LexRegPulse: Banking Regulation Brief is answering right now. Last checked 6 min ago. 63 installs a week from npm. It exposes 9 tools. Last commit 20 Sep 2026.
Daily US banking regulation brief, weekly digest, archive and comment-deadline tracker. No key.
Installs per day
peak 292 · avg 19 · -16% w/w
a month agotoday
Uptime history
49 days of history · worst day 92%
49 days agonow
96.7%
Uptime 24h
88 of 91 checks
9
Tools
read from the server
875 ms
Response time
average over 24h
63
Installs / week
npm and PyPI
What changed 1
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 October 2026. No other catalogue keeps this.
9 Oct
a tool description was rewritten
get_weekly_digest
LexRegPulse: Banking Regulation Brief does not always answer
Over the last week it answered 99.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.
run in your terminal
claude mcp add bankregpulse-mcp-server --transport http https://lexregpulse.com/mcpSettings → Connectors → Add custom connector, then paste this address
https://lexregpulse.com/mcp~/.codex/config.toml
[mcp_servers.bankregpulse-mcp-server]
url = "https://lexregpulse.com/mcp".cursor/mcp.json
{
"mcpServers": {
"bankregpulse-mcp-server": {
"url": "https://lexregpulse.com/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"bankregpulse-mcp-server": {
"type": "http",
"url": "https://lexregpulse.com/mcp"
}
}
}Available tools 9
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
blog
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").
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.
daily
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, …
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.
briefings
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.
linkedin
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.
subscribe
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.
upcoming
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.
weekly
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://lexregpulse.com/mcp | streamable-http | answering | 694 ms | 6 min ago |
Alternatives to LexRegPulse: Banking Regulation Brief
same job, measured the same wayHorizon: AI News & AI Regulation Tracker
by alchemylab-horizon
Free, no-key AI news + AI regulation tracker MCP: EU AI Act, US federal & state, UK. Daily briefing.
E
Eclipse Codex MCP
by cyan-eclipse-technologies-llc
Banking regulation as data: a citation-exact library, a deadline engine, sanctions screening, and
AppealGo UK parking guides
by appealgo
Free, no key: UK parking ticket appeal guides, PCN contravention codes and deadline calculator.
eCFR.io Federal Regulations
by ecfr
Search and read US federal regulations with legal and inline citations linking to ecfr.io.
e/acc
by e-acc
AI news for agents: daily, weekly and monthly briefings, trending events and model prices. No key.
AIHOT
by kkkkhazix
Chinese AI news: search topics, explore hot events, and read daily, weekly and monthly briefs.
Regulations.ai — Global AI Law Tracker
by regulations
AI laws from 110+ countries, enforcement actions and a 3,900-term glossary. Free, no API key.
Regulations.gov
by 1102tools
Regulations.gov readiness, rulemaking dockets, documents, comments, and comment periods. 9 tools.
LexRegPulse: Banking Regulation Brief — questions
Answers built from our own checks of this server.
What can LexRegPulse: Banking Regulation Brief do?
It exposes 9 tools, read directly from the server on our last check. Among them: get_blog_post, get_blog_posts, get_daily_briefing, get_daily_podcast, get_linkedin_post, get_upcoming_deadlines and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is LexRegPulse: Banking Regulation Brief mostly used for?
Its tools cluster around blog and daily. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is LexRegPulse: Banking Regulation Brief working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 88 of 91 checks got a reply (96.7%), average response time 875 ms. The bar chart above shows every period we have measured.
How do I connect LexRegPulse: Banking Regulation Brief?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does LexRegPulse: Banking Regulation Brief need an API key?
No. LexRegPulse: Banking Regulation Brief completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is LexRegPulse: Banking Regulation Brief?
It answers our handshake in 875 ms on average, which is faster than 7% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use LexRegPulse: Banking Regulation Brief?
The npm package bankregpulse-mcp-server was installed 63 times in the last week. Week over week that is -16%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is LexRegPulse: Banking Regulation Brief open source?
The code is open source: it is published under the MIT licence, written in TypeScript and 1 stars on GitHub. The licence covers the code in the repository, not the hosted service at lexregpulse.com, which runs on its operator's own terms.