loading…
Search for a command to run...
loading…
BankRegPulse MCP Server connects AI assistants to live banking regulatory data from 100+ sources including OCC, FDIC, CFPB, Federal Reserve, and all 50 state ba
BankRegPulse MCP Server connects AI assistants to live banking regulatory data from 100+ sources including OCC, FDIC, CFPB, Federal Reserve, and all 50 state banking departments. Three tools: daily intelligence briefings, regulatory podcast audio, and pre-formatted LinkedIn posts — all updated daily at 6 AM EST.
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.
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:
Your AI will pull fresh data from BankRegPulse and answer with context.
| Tool | Description | Example Use |
|---|---|---|
get_daily_briefing |
Daily regulatory intelligence summary | "What did the OCC publish today?" |
get_daily_podcast |
Audio briefing URL | "Get today's regulatory podcast" |
get_linkedin_post |
Pre-formatted social content | "Draft a LinkedIn post about today's news" |
npx bankregpulse-mcp-server
git clone https://github.com/RRGU26/bankregpulse-mcp-server.git
cd bankregpulse-mcp-server
npm install
npm run build
Locate Claude Desktop config:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonAdd BankRegPulse MCP server:
{
"mcpServers": {
"bankregpulse": {
"command": "npx",
"args": ["bankregpulse-mcp-server"]
}
}
}
Restart Claude Desktop
Test it:
Add to ~/.continue/config.json:
{
"experimental": {
"modelContextProtocolServers": [
{
"transport": {
"type": "stdio",
"command": "npx",
"args": ["bankregpulse-mcp-server"]
}
}
]
}
}
Any MCP-compatible client can connect via stdio:
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);
Run the MCP server as an HTTP endpoint instead of stdio:
# Set environment variable
export MCP_TRANSPORT=http
export PORT=3000 # optional, defaults to 3000
# Run server
npx bankregpulse-mcp-server
Endpoints:
GET /health - Health checkGET /sse - SSE endpoint for MCP connectionsConnect via HTTP:
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:
# Health check
curl http://localhost:3000/health
# SSE connection (requires MCP client)
curl -N http://localhost:3000/sse
Ask Claude:
"What's in today's banking regulatory briefing?"
Claude queries:
Tool: get_daily_briefing
Date: today
You receive:
Ask Claude:
"Get me today's regulatory podcast"
Claude queries:
Tool: get_daily_podcast
Date: today
You receive:
Ask Claude:
"Draft a LinkedIn post about today's CFPB enforcement actions"
Claude queries:
Tool: get_linkedin_post
Date: today
You receive:
"What was in the regulatory briefing on February 20, 2024?"
Claude will pass date: "2024-02-20" to the tool.
Set environment variable to use a different API:
export BANKREGPULSE_API_URL=https://your-custom-api.com
Cause: Briefing hasn't been generated yet (runs at 6 AM EST daily)
Solution: Query yesterday's briefing or wait until morning
Cause: Network issue or API is down
Solution:
Cause: MCP server not properly installed or outdated
Solution:
npm cache clean --force
npx bankregpulse-mcp-server@latest
# Clone repo
git clone https://github.com/RRGU26/bankregpulse-mcp-server.git
cd bankregpulse-mcp-server
# Install dependencies
npm install
# Build
npm run build
# Run locally
npm start
npx @modelcontextprotocol/inspector npx bankregpulse-mcp-server
Opens a web UI to test tool calls.
┌─────────────────┐
│ 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)
└─────────────────┘
The MCP server calls these public API endpoints:
GET /api/mcp/briefing?date=YYYY-MM-DD - Daily briefingGET /api/mcp/podcast?date=YYYY-MM-DD - Podcast URLGET /api/mcp/linkedin-post?date=YYYY-MM-DD - LinkedIn postNo authentication required for basic usage.
Free for community use.
No API key required. Rate limits apply:
For enterprise usage (higher limits, SLA), contact: [email protected]
Contributions welcome! Please:
MIT License - see LICENSE for details.
Made with ❤️ for the banking compliance community
Добавь это в claude_desktop_config.json и перезапусти Claude Desktop.
{
"mcpServers": {
"bankregpulse": {
"command": "npx",
"args": []
}
}
}