MCP.Market

LexRegPulse: Banking Regulation Brief MCP server

online · 100% uptime
by RRGU26·io.github.RRGU26/bankregpulse-mcp-server·v1.3.0·1 stars
No reviews yet

Daily US banking regulation brief, weekly digest, archive and comment-deadline tracker. No key.

A86/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A86/100

full report

Adoption
Growing

1 stars49 downloads/wk

Reviews

Write one

Nobody has reviewed LexRegPulse: Banking Regulation Brief yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

LexRegPulse: Banking Regulation Brief tools (9, 2 write)

write = sends, deletes, buys or posts
  • get_blog_postwrite actionFree

    Full text of one LexRegPulse deep-dive post as markdown, by slug (the last path segment of its URL, e.g. "occ-fdic-unsafe-unsound-rule-changed").

  • get_blog_postsFree

    LexRegPulse's deep-dive analysis pieces by Lex: long-form reads on a rule, an enforcement pattern or a supervisory shift, each ending on what it changes for a bank, fintech or firm. Returns the newest posts with title, date, one-line summary, slug and canonical URL; use get_blog_post for the full text.

  • get_daily_briefingFree

    LexRegPulse's daily banking regulatory brief, published every morning at 6:45 AM ET. Sections: the lead story with its bank-side transmission, regulatory developments (OCC, FDIC, Federal Reserve, CFPB, FinCEN, OFAC, SEC, CFTC, NCUA and the states), industry signals (market and industry context: rates, deals, funding, fintech), political and legislative items, what's coming (comment windows, effective dates) and what it means. Every figure is traced to a source and every edition is QA-scored before it sends. Returns the full edition as markdown with its canonical URL; each bullet is addressable on the web page as #b-1, #b-2, …

  • get_daily_podcastFree

    The day's LexRegPulse Daily podcast: the four-minute audio edition of the morning brief. Returns the audio URL, the RSS feed and the matching written edition.

  • get_linkedin_postwrite actionFree

    A LinkedIn-ready post drafted from the day's sent brief: the lead in one paragraph, three headlines, a link to the edition.

  • get_upcoming_deadlinesFree

    Upcoming regulatory deadlines from LexRegPulse's deterministic tracker: comment windows closing and rules taking effect, pulled from the Federal Register's structured fields rather than prose. Returns date, kind, title and agency.

  • get_weekly_digestFree

    The LexRegPulse Weekly Intelligence Digest (Sundays): the week's lead stories, regulatory developments, market and macro, industry watch and the week ahead as a long-form print edition. Returns markdown with the canonical URL.

  • list_briefingsFree

    The archive index: recent daily briefs and weekly digests with dates, titles and canonical URLs. Use it to find the edition that covered a date or a story, then call get_daily_briefing or get_weekly_digest with that date.

  • subscribe_to_daily_briefFree

    Subscribe an email address to the LexRegPulse Daily Brief (free; every morning at 6:45 AM ET, plus the Sunday digest). Call this only when the user has asked to subscribe and has given the address. A welcome email confirms the subscription and carries a one-click unsubscribe link. Returns a plain confirmation.

Public scan report

scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it

1 high
  • Code scan3 source files scanned25/25
  • Live reliabilityremote reachable in 1269ms20/20
  • Tool poisoning9 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 2 write-action tools with no auth3/15
  • Maintenancelast push 26 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • highWrite-action tools reachable without authenticationauth.open-write
Overall 86/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How LexRegPulse: Banking Regulation Brief compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
86/100
higher than 72% of 48,243 servers
Tools
9
the typical server has 7
Tools that change things
22%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
1,047 ms
faster than 12% of 30,027 servers
GitHub stars
1
more than 65% of 28,706 servers
Downloads a week
49
more than 39% of 12,306 servers with a package

What its tools let an agent do: 7 read · 2 change

Release history: 2 versions in the registry since 2026-02-25, latest 2026-09-20, typically one every 208 days.

Install LexRegPulse: Banking Regulation Brief in Claude Code, Cursor or VS Code

claude mcp add --transport http bankregpulse-mcp-server https://lexregpulse.com/mcp
Add to Cursor

What the publisher says

From the LexRegPulse: Banking Regulation Brief repository's README, as published. We do not edit it. Read it on GitHub

BankRegPulse MCP Server

Real-time banking regulatory intelligence for AI assistants

Connect your AI assistant (Claude, ChatGPT, etc.) to live banking regulatory data from 100+ sources including OCC, FDIC, CFPB, Federal Reserve, and all 50 state banking departments.

Fastest way in: no install, no key

The server is hosted. Point any MCP client at the URL:

https://lexregpulse.com/mcp
  • Claude (web, desktop, mobile): Settings, Connectors, Add custom connector, paste the URL.
  • Claude Code: claude mcp add --transport http lexregpulse https://lexregpulse.com/mcp
  • ChatGPT (developer mode), Cursor, VS Code, any Streamable HTTP client: add the same URL as a remote MCP server.
  • Smithery: https://smithery.ai/servers/bankregpulse/lexreg
  • Local over stdio: npx bankregpulse-mcp-server (see Installation below).

Read-only and free. The content is the LexRegPulse daily brief (6:45 AM ET), the Sunday digest, the archive, deep-dive analysis and a comment-deadline tracker built from Federal Register fields.

What is This?

BankRegPulse MCP Server is a Model Context Protocol server that lets AI assistants query our regulatory intelligence database in real-time.

Instead of manually searching for regulatory updates, just ask your AI:

  • "What's in today's banking regulatory briefing?"
  • "Play today's regulatory podcast"
  • "Draft a LinkedIn post about today's CFPB updates"

Your AI will pull fresh data from BankRegPulse and answer with context.

Features

🎯 Eight Tools

📊 Data Coverage

  • Federal Agencies: OCC, FDIC, CFPB, Federal Reserve, Treasury
  • State Banking Departments: All 50 states
  • Congress: House Financial Services, Senate Banking
  • Federal Register: Final rules, proposed rules, notices
  • News: Reuters, American Banker, PYMNTS, Banking Dive
  • Update Frequency: Real-time (monitored 24/7)

Installation

Prerequisites

  • Node.js 18 or higher
  • An MCP-compatible AI assistant (Claude Desktop, Continue.dev, etc.)

Option 1: NPM (Recommended)

npx bankregpulse-mcp-server

Option 2: From Source

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

LexRegPulse: Banking Regulation Brief: common questions

Is LexRegPulse: Banking Regulation Brief MCP server safe?
Yes, by our scan: it is graded A (86/100). Read the LexRegPulse: Banking Regulation Brief safety report
How do I install LexRegPulse: Banking Regulation Brief?
It runs remotely at lexregpulse.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does LexRegPulse: Banking Regulation Brief need an API key?
No secret keys are declared. It reads 1 setting from the environment.
Is LexRegPulse: Banking Regulation Brief maintained?
The last commit was 46 days ago (2026-09-20). The latest release is v1.3.0.
Is LexRegPulse: Banking Regulation Brief up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does LexRegPulse: Banking Regulation Brief compare with other MCP servers?
safety score 86/100 (higher than 72% of 48,243 servers); tools 9 (the typical server has 7); tools that change things 22% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.