mcp-registry/io.github.rrgu26/bankregpulse-mcp-server · v1.3.0
As of 2026-10-19 01:29 UTC, the Rrgu26 Bankregpulse MCP server is up with a Glimind reliability score of 71/100 (grade C). Over the last 30 days it answered 98.8% of Glimind's liveness checks. It had 40 outages in 90 days, with a median recovery of 8 minutes.
Daily US banking regulation brief, weekly digest, archive and comment-deadline tracker. No key.
Claude Code
claude mcp add --transport http rrgu26-bankregpulse-mcp-server https://lexregpulse.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"rrgu26-bankregpulse-mcp-server": {
"type": "http",
"url": "https://lexregpulse.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
9 of 9 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Reachable 98.8% of the time over the last 30 days; median recovery 8 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
Handshake + tools/list takes ~1,929 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.rrgu26%2Fbankregpulse-mcp-server/fixes
{
"name": "get_blog_post",
"description": "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\").",
"inputSchema": {
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"description": "Post slug from get_blog_posts or the URL."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_blog_posts",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"limit": {
"type": "integer",
"description": "How many posts, newest first (default 10, max 50)."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_daily_briefing",
"description": "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 befo",
"inputSchema": {
"type": "object",
"properties": {
"date": {
"type": "string",
"description": "Optional edition date, YYYY-MM-DD. Defaults to the most recent edition."
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.rrgu26/bankregpulse-mcp-server"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.rrgu26/bankregpulse-mcp-server"}) over MCP.
get_daily_briefing ~197 tokenssubscribe_to_daily_brief ~163 tokensget_blog_posts ~135 tokensget_weekly_digest ~118 tokensget_upcoming_deadlines ~116 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.rrgu26%2Fbankregpulse-mcp-server?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.rrgu26%2Fbankregpulse-mcp-server?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.rrgu26%2Fbankregpulse-mcp-server.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.rrgu26%2Fbankregpulse-mcp-server.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.rrgu26%2Fbankregpulse-mcp-server?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:08d119c5e1542180…, first seen 2026-10-17, included at leaf 5985 of 24,211. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable media servers · most reliable communication servers · most reliable email servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 01:29 UTC, the Rrgu26 Bankregpulse MCP server is up with a Glimind reliability score of 71/100 (grade C). Over the last 30 days it answered 98.8% of Glimind's liveness checks. It had 40 outages in 90 days, with a median recovery of 8 minutes.
Rrgu26 Bankregpulse MCP server advertises 9 tools, including get_blog_post, get_blog_posts, get_daily_briefing, get_daily_podcast, get_linkedin_post.
Point your MCP client at this streamable-http endpoint: https://lexregpulse.com/mcp
Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.