LexRegPulse: Banking Regulation Brief
NPM · BANKREGPULSE-MCP-SERVER · 2 COMPONENTS
Daily US banking regulation brief, weekly digest, archive and comment-deadline tracker. No key.
Available components
Last scanned (19 hours ago)
Scores higher than 86% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 60 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 776 tokens (~86/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Package version: 1.0.3 → 1.3.0 functional
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 −1
- Stability: pass → 0.93 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/bankregpulse-mcp-server@1.3.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_blog_post ~65
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").
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Post slug from get_blog_posts or the URL. |
No output schema declared.
No examples provided.
get_blog_posts ~99
LexRegPulse's deep-dive analysis pieces by Lex — long-form reads on a rule, an enforcement pattern or a supervisory shift, each ending on the decision it changes for a bank, fintech or firm. Returns the newest posts with title, date, one-line summary and canonical URL; use get_blog_post for the full text.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many posts to list, newest first (default 10, max 50). |
No output schema declared.
No examples provided.
get_daily_briefing ~181
LexRegPulse's daily banking regulatory brief, published every weekday and weekend 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 markdown with the canonical URL; each bullet is addressable on the web page as #b-1, #b-2, …
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Optional edition date, YYYY-MM-DD. Defaults to the most recent edition. |
No output schema declared.
No examples provided.
get_daily_podcast ~58
Today's LexRegPulse Daily podcast: the four-minute audio edition of the morning brief. Returns the audio URL and the podcast RSS feed.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Optional edition date, YYYY-MM-DD. Defaults to the most recent edition. |
No output schema declared.
No examples provided.
get_linkedin_post ~47
A LinkedIn-ready post drafted from the day's sent brief, ready to copy.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Optional edition date, YYYY-MM-DD. Defaults to the most recent edition. |
No output schema declared.
No examples provided.
get_upcoming_deadlines ~72
Upcoming regulatory deadlines from LexRegPulse's deterministic tracker — comment windows closing and rules taking effect — pulled from the Federal Register's structured fields, not from prose. Returns date, kind, title and agency.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Window in days from today (default 21, max 90). |
No output schema declared.
No examples provided.
get_weekly_digest ~76
The LexRegPulse Weekly Print Digest (Sundays): the week's lead stories, regulatory developments, market and macro, industry watch and the week ahead, written as a long-form print edition. Returns markdown with the canonical URL.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Optional Sunday date, YYYY-MM-DD. Defaults to the latest digest. |
No output schema declared.
No examples provided.
list_briefings ~83
The archive index: recent daily briefs and weekly digests with their 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many editions to list, newest first (default 14, max 60). |
No output schema declared.
No examples provided.
subscribe_to_daily_brief ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The user's email address. | |
| first_name | string | – | Optional first name for the greeting. |
No output schema declared.
No examples provided.
How do I install the LexRegPulse: Banking Regulation Brief MCP server?
LexRegPulse: Banking Regulation Brief runs locally as an npm package, launched with npx -y bankregpulse-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · bankregpulse-mcp-server
claude mcp add rrgu26-bankregpulse-mcp-server -- npx -y bankregpulse-mcp-server
What is the LexRegPulse: Banking Regulation Brief MCP server?
LexRegPulse: Banking Regulation Brief is an MCP server listed in the public MCP registry as io.github.RRGU26/bankregpulse-mcp-server. Daily US banking regulation brief, weekly digest, archive and comment-deadline tracker. No key. This page covers its npm package (bankregpulse-mcp-server).
Is the LexRegPulse: Banking Regulation Brief MCP server safe to use?
LexRegPulse: Banking Regulation Brief scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the LexRegPulse: Banking Regulation Brief MCP server expose?
LexRegPulse: Banking Regulation Brief exposes 9 tools: get_daily_briefing, get_weekly_digest, list_briefings, get_blog_posts, get_blog_post, and 4 more. Their descriptions and schemas cost roughly 776 tokens of context every time the server is loaded.
Is the LexRegPulse: Banking Regulation Brief MCP server still maintained?
LexRegPulse: Banking Regulation Brief is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the LexRegPulse: Banking Regulation Brief MCP server under?
LexRegPulse: Banking Regulation Brief declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the LexRegPulse: Banking Regulation Brief MCP server?
VerifyMCP ran 16 checks on LexRegPulse: Banking Regulation Brief, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.