bankregpulse-mcp-server

MCPcommunitylive
v1.3.0BankRegPulseMITUpdated 2d agonpmGitHub

Daily banking regulatory intelligence for AI agents: the LexRegPulse morning brief, weekly digest, archive, deep dives and deadline tracker.

Endpoint healthlive
checked 1 day ago · 757ms
100% of the last 1 check reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
46Downloads/wk
2d agoLast update
Package
AuthorBankRegPulse
LicenseMIT
Version1.3.0
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface9 tools · none privileged
Security scan✓ Cleanv1.3.0 · todayHow well does this scan work?
EvalsNone
IndexedSep 21, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

9 tools · none privileged
Statically extracted from the published packagev1.3.0 · 11h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

get_daily_briefingNo description published

This tool published no description. Forge does not invent one.

get_weekly_digestThe 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.

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.

No input schema was published for this tool.

list_briefingsThe 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.

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.

No input schema was published for this tool.

get_blog_postsLexRegPulse'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 ful…

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

No input schema was published for this tool.

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

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

No input schema was published for this tool.

get_upcoming_deadlinesUpcoming 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.

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.

No input schema was published for this tool.

get_daily_podcastToday's LexRegPulse Daily podcast: the four-minute audio edition of the morning brief. Returns the audio URL and the podcast RSS feed.

Today's LexRegPulse Daily podcast: the four-minute audio edition of the morning brief. Returns the audio URL and the podcast RSS feed.

No input schema was published for this tool.

get_linkedin_postA LinkedIn-ready post drafted from the day's sent brief, ready to copy.

A LinkedIn-ready post drafted from the day's sent brief, ready to copy.

No input schema was published for this tool.

subscribe_to_daily_briefSubscribe 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.

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.

No input schema was published for this tool.

8 of 9 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Daily banking regulatory intelligence for AI agents: the LexRegPulse morning brief, weekly digest, archive, deep dives and deadline tracker.

Keywords
aibankingbankregpulsecfpbclaudecompliancefdicfederal-reservefincenfintechlexregpulsemcpmodel-context-protocoloccregulationregulatoryregulatory-intelligence
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-22 — observed resolution, not a publisher declaration.

60 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.