LexRegPulse: Banking Regulation Brief MCP server
io.github.RRGU26/bankregpulse-mcp-serverRRGU26streamable-httpv1.3.0Scanned
Daily US banking regulation brief, weekly digest, archive and comment-deadline tracker. No key.
9 tools: 1 can delete or cancel things, 1 change things and 7 only read.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the LexRegPulse: Banking Regulation Brief MCP server can do
The LexRegPulse: Banking Regulation Brief MCP server is published by the GitHub account RRGU26. It has 9 tools. It can delete or cancel things (1 tool: list_briefings) and create or change data (1 tool: subscribe_to_daily_brief). 7 tools only read.
4 tools bring in text other people can write (get_blog_posts, get_blog_post, get_upcoming_deadlines and 1 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 1.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Deletes or cancels 1Claude Code: deny
list_briefingsThe archive index: recent daily briefs and weekly digests with dates, titles and canonical URLs.No findings
Why it is in this group
- The name "list_briefings" says "list": a word for reading.
- The description's first verb is "archive": a word for removing or ending something.
Description, as the server wrote it 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.
Changes things 1Claude Code: ask
subscribe_to_daily_briefSubscribe an email address to the LexRegPulse Daily Brief (free; every morning at 6:45 AM ET, plus the Sunday digest).No findings
Why it is in this group
- The name "subscribe_to_daily_brief" says "subscribe": a word for a change.
Description, as the server wrote it 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.
Only reads 7Show 7 read-only tools
get_blog_postFull text of one LexRegPulse deep-dive post as markdown, by slug (the last path segment of its URL, e.g.Reads text others writeNo findings
Why it is in this group
- The name "get_blog_post" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "get_blog_post" says "get" and "post": it reads posts, which other people can write.
- untrusted-inputThe description's first sentence says "post": it reads posts, which other people can write.
Description, as the server wrote it 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_postsLexRegPulse'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…Reads text others writeNo findings
Why it is in this group
- The name "get_blog_posts" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "get_blog_posts" says "get" and "post": it reads posts, which other people can write.
Description, as the server wrote it 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.
get_daily_briefingLexRegPulse's daily banking regulatory brief, published every morning at 6:45 AM ET.No findings
Why it is in this group
- The name "get_daily_briefing" says "get": a word for reading.
Description, as the server wrote it 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_podcastThe day's LexRegPulse Daily podcast: the four-minute audio edition of the morning brief.No findings
Why it is in this group
- The name "get_daily_podcast" says "get": a word for reading.
Description, as the server wrote it 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.
get_linkedin_postA LinkedIn-ready post drafted from the day's sent brief: the lead in one paragraph, three headlines, a link to the edition.Reads text others writeNo findings
Why it is in this group
- The name "get_linkedin_post" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "get_linkedin_post" says "get" and "post": it reads posts, which other people can write.
- untrusted-inputThe description's first sentence says "post": it reads posts, which other people can write.
Description, as the server wrote it A LinkedIn-ready post drafted from the day's sent brief: the lead in one paragraph, three headlines, a link to the edition.
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 rather…Reads text others writeNo findings
Why it is in this group
- The name "get_upcoming_deadlines" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "comment": it reads comments, which other people can write.
Description, as the server wrote it 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.
get_weekly_digestThe 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 edi…No findings
Why it is in this group
- The name "get_weekly_digest" says "get": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:00 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://lexregpulse.com/.well-known/oauth-protected-resource
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://lexregpulse.com/mcp: tools/list returned 9 tools to an anonymous client, including list_briefings (destructive), subscribe_to_daily_brief (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http bankregpulse https://lexregpulse.com/mcpclaude mcp add --transport http bankregpulse https://lexregpulse.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__bankregpulse__get_daily_briefing",
"mcp__bankregpulse__get_weekly_digest",
"mcp__bankregpulse__get_blog_posts",
"mcp__bankregpulse__get_blog_post",
"mcp__bankregpulse__get_upcoming_deadlines",
"mcp__bankregpulse__get_daily_podcast",
"mcp__bankregpulse__get_linkedin_post"
],
"ask": [
"mcp__bankregpulse__subscribe_to_daily_brief"
],
"deny": [
"mcp__bankregpulse__list_briefings"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as bankregpulse. Review it before you use it.
Capability tags behind 4 rules
- mcp__bankregpulse__get_blog_posts untrusted-input
- mcp__bankregpulse__get_blog_post untrusted-input
- mcp__bankregpulse__get_upcoming_deadlines untrusted-input
- mcp__bankregpulse__get_linkedin_post untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.RRGU26/bankregpulse-mcp-server/verify?hash=2cba3704b67c29c49de6539c8fa012205242559a88e55f694a421b30b94bde8e" | jq -e '.changed == false'Pinned hash 2cba3704b67c, from Nov 16, 2026, 04:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.RRGU26/bankregpulse-mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.RRGU26/bankregpulse-mcp-server)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:18 UTC.
LexRegPulse: Banking Regulation Brief MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the LexRegPulse: Banking Regulation Brief MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the LexRegPulse: Banking Regulation Brief MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: list_briefings.
Can the LexRegPulse: Banking Regulation Brief MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the LexRegPulse: Banking Regulation Brief MCP server have?
- 9 tools: 1 destructive, 1 write, 7 read. list_briefings, subscribe_to_daily_brief, get_daily_briefing, get_weekly_digest, get_blog_posts, get_blog_post, get_upcoming_deadlines, get_daily_podcast and 1 more.
Does the LexRegPulse: Banking Regulation Brief MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the LexRegPulse: Banking Regulation Brief MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the LexRegPulse: Banking Regulation Brief MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.