LexRegPulse: Banking Regulation Brief

io.github.RRGU26Published by GitHub account RRGU26v1.3.0Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableFinanceKnowledge & Memory

Overview

AI-generated overview

A hosted, keyless MCP server that gives an assistant LexRegPulse's daily US banking regulation brief, weekly digest, archive, deep-dive posts and deadline list.

What you can do
Read the daily briefing and weekly digest, including lead story, agency developments and industry signals, as markdown with canonical URLs, optionally for a specific date via the archive index of dates, titles and links. Fetch deep-dive analysis posts: a list of recent posts with titles, dates, summaries and slugs, or the full text of one post by slug. List upcoming regulatory deadlines such as comment windows closing and rules taking effect, with date, kind, title and agency. Retrieve the daily podcast audio URL and RSS feed, and get a LinkedIn-ready post drafted from the day's brief. Subscribe an email address to the free Daily Brief and Sunday digest.
When to use it
Useful for banking compliance, regulatory affairs and fintech policy work where an assistant should answer from current US federal and state banking regulatory coverage rather than general knowledge, including tracking comment deadlines and drafting shareable summaries.
Requirements
Remote endpoint at lexregpulse.com over Streamable HTTP, or a local process via npx bankregpulse-mcp-server with Node.js 18 or higher. No API key or account for basic use; the optional BANKREGPULSE_API_URL variable points at a custom API endpoint. Network access to the LexRegPulse API is required.
Before you install
Read-only and free, with rate limits of 100 requests per hour per IP and a fair-use policy. subscribe_to_daily_brief sends a user-supplied email address to LexRegPulse and should only be called when the user asks and provides the address. Setting BANKREGPULSE_API_URL redirects requests to a different endpoint of your choosing.

Installation

In SourceWeft

  1. Open LexRegPulse: Banking Regulation Brief in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.RRGU26%2Fbankregpulse-mcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "lexregpulse-banking-regulation-brief": {
      "type": "http",
      "url": "https://lexregpulse.com/mcp"
    }
  }
}

README

BankRegPulse MCP Server

Real-time banking regulatory intelligence for AI assistants

[npm version] [License: MIT] [Node Version] [MCP]

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

ToolDescriptionExample Use
get_daily_briefingThe morning brief (lead, regulatory developments, industry signals, political, what's coming, what it means), as markdown with its canonical URL"What's in today's banking regulatory brief?"
get_weekly_digestThe Sunday print digest"Summarize last week's regulatory developments"
list_briefingsArchive index: dates, titles, URLs"Which edition covered the OCC charter decisions?"
get_blog_postsRecent deep-dive analysis by Lex"What has Lex written on the unsafe-or-unsound rule?"
get_blog_postFull text of one deep dive, by slug"Give me the full OCC-FDIC rule analysis"
get_upcoming_deadlinesComment windows and effective dates from the deadline tracker"What comment periods close in the next two weeks?"
get_daily_podcastAudio URL and feed for the daily episode"Get today's regulatory podcast"
get_linkedin_postLinkedIn-ready post drafted from the brief"Draft a LinkedIn post about today's news"
subscribe_to_daily_briefSubscribe an email address to the free Daily Brief (6:45 AM ET) and Sunday digest; welcome email with one-click unsubscribe"Subscribe me to LexRegPulse at [email protected]"

📊 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)

bash
npx bankregpulse-mcp-server

Option 2: From Source

bash
git clone https://github.com/RRGU26/bankregpulse-mcp-server.gitcd bankregpulse-mcp-servernpm installnpm run build

Setup for Claude Desktop

  1. Locate Claude Desktop config:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%\Claude\claude_desktop_config.json

  2. Add BankRegPulse MCP server:

json
{  "mcpServers": {    "bankregpulse": {      "command": "npx",      "args": ["bankregpulse-mcp-server"]    }  }}

  1. Restart Claude Desktop

  2. Test it:

    • Open Claude Desktop
    • Ask: "What's in today's banking regulatory briefing?"
    • Claude will query the MCP server and return live data

Setup for Other AI Assistants

Continue.dev (VS Code)

Add to ~/.continue/config.json:

json
{  "experimental": {    "modelContextProtocolServers": [      {        "transport": {          "type": "stdio",          "command": "npx",          "args": ["bankregpulse-mcp-server"]        }      }    ]  }}

Custom Integration

Any MCP-compatible client can connect via stdio:

typescript
import { Client } from '@modelcontextprotocol/sdk/client/index.js';import { StdioClientTransport } from '@modelcontextprotocol/sdk/client/stdio.js';
const transport = new StdioClientTransport({  command: 'npx',  args: ['bankregpulse-mcp-server']});
const client = new Client({  name: 'my-client',  version: '1.0.0'}, {  capabilities: {}});
await client.connect(transport);

HTTP/SSE Mode

Run the MCP server as an HTTP endpoint instead of stdio:

bash
# Set environment variableexport MCP_TRANSPORT=httpexport PORT=3000  # optional, defaults to 3000
# Run servernpx bankregpulse-mcp-server

Endpoints:

  • GET /health - Health check
  • GET /sse - SSE endpoint for MCP connections

Connect via HTTP:

typescript
import { Client } from '@modelcontextprotocol/sdk/client/index.js';import { SSEClientTransport } from '@modelcontextprotocol/sdk/client/sse.js';
const transport = new SSEClientTransport(  new URL('http://localhost:3000/sse'));
const client = new Client({  name: 'my-client',  version: '1.0.0'}, {  capabilities: {}});
await client.connect(transport);

Test with curl:

bash
# Health checkcurl http://localhost:3000/health
# SSE connection (requires MCP client)curl -N http://localhost:3000/sse

Usage Examples

Daily Briefing

Ask Claude:

"What's in today's banking regulatory briefing?"

Claude queries:

Tool: get_daily_briefingDate: today

You receive:

  • Executive summary of key developments
  • Document count and high-priority items
  • Agency-by-agency breakdown

Podcast

Ask Claude:

"Get me today's regulatory podcast"

Claude queries:

Tool: get_daily_podcastDate: today

You receive:

  • Audio URL for the daily briefing podcast
  • Generated by AI from the day's regulatory developments

LinkedIn Post

Ask Claude:

"Draft a LinkedIn post about today's CFPB enforcement actions"

Claude queries:

Tool: get_linkedin_postDate: today

You receive:

  • Pre-formatted LinkedIn post with hashtags
  • Key stats and highlights
  • Ready to copy and share

Advanced Usage

Query Specific Dates

"What was in the regulatory briefing on February 20, 2024?"

Claude will pass date: "2024-02-20" to the tool.

Custom API Endpoint

Set environment variable to use a different API:

bash
export BANKREGPULSE_API_URL=https://your-custom-api.com

Troubleshooting

"No briefing found"

Cause: Briefing hasn't been generated yet (runs at 6 AM EST daily)

Solution: Query yesterday's briefing or wait until morning

"API request failed"

Cause: Network issue or API is down

Solution:

  1. Check https://bankregpulse-enterprise-api.onrender.com/health
  2. Verify internet connection
  3. Check Render status: https://status.render.com

"Unknown tool"

Cause: MCP server not properly installed or outdated

Solution:

bash
npm cache clean --forcenpx bankregpulse-mcp-server@latest

Development

Local Development

bash
# Clone repogit clone https://github.com/RRGU26/bankregpulse-mcp-server.gitcd bankregpulse-mcp-server
# Install dependenciesnpm install
# Buildnpm run build
# Run locallynpm start

Testing with MCP Inspector

bash
npx @modelcontextprotocol/inspector npx bankregpulse-mcp-server

Opens a web UI to test tool calls.

Architecture

┌─────────────────┐│  AI Assistant   │ (Claude, ChatGPT, etc.)│  (MCP Client)   │└────────┬────────┘         │ stdio         │┌────────▼────────┐│  BankRegPulse   ││   MCP Server    │ (this package)└────────┬────────┘         │ HTTPS         │┌────────▼────────┐│  BankRegPulse   ││      API        │ (bankregpulse-enterprise-api.onrender.com)└────────┬────────┘         │┌────────▼────────┐│   PostgreSQL    ││   Database      │ (100+ regulatory sources)└─────────────────┘

API Endpoints (Backend)

The MCP server calls these public API endpoints:

  • GET /api/mcp/briefing?date=YYYY-MM-DD - Daily briefing
  • GET /api/mcp/podcast?date=YYYY-MM-DD - Podcast URL
  • GET /api/mcp/linkedin-post?date=YYYY-MM-DD - LinkedIn post

No authentication required for basic usage.

Pricing

Free for community use.

No API key required. Rate limits apply:

  • 100 requests per hour per IP
  • Fair use policy

For enterprise usage (higher limits, SLA), contact: [email protected]

Support

Contributing

Contributions welcome! Please:

  1. Fork the repo
  2. Create a feature branch
  3. Submit a pull request

License

MIT License - see LICENSE for details.

Acknowledgments

  • Built on Model Context Protocol by Anthropic
  • Powered by BankRegPulse regulatory intelligence platform
  • Regulatory data from OCC, FDIC, CFPB, Federal Reserve, and state banking departments

Related Projects

Made with ❤️ for the banking compliance community

Source: README.md at commit f762dd4

Tools

9

get_daily_briefing

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, …

Parametersdate

get_weekly_digest

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.

Parametersdate

list_briefings

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.

Parameterslimit

get_blog_posts

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.

Parameterslimit

get_blog_post

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").

Parametersslugrequired

get_upcoming_deadlines

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.

Parametersdays

get_daily_podcast

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.

Parametersdate

get_linkedin_post

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

Parametersdate

subscribe_to_daily_brief

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.

Parametersemailrequiredfirst_name

Version history

2
  1. v1.3.0LatestSep 21, 2026
  2. v1.0.3Sep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts