LexRegPulse: Banking Regulation Brief
REMOTE · LEXREGPULSE.COM · 2 COMPONENTS
Daily US banking regulation brief, weekly digest, archive and comment-deadline tracker. No key.
Available components
Last scanned (21 hours ago)
Scores higher than 83% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1974 tokens (~58/item across 34 items; 9 tools + 25 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
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
- Resource “brief-2026-10-21” was removed ▼ functional
- Stability: pass → 0.97 functional
- New resource “brief-2026-11-04” functional
- 4 Nov 26 0
- Resource “brief-2026-10-20” was removed ▼ functional
- New resource “brief-2026-11-03” functional
- 3 Nov 26 0
- Resource “brief-2026-10-19” was removed ▼ functional
- New resource “brief-2026-11-02” functional
- 2 Nov 26 0
- Resource “digest-2026-10-18” was removed ▼ functional
- New resource “digest-2026-11-01” functional
- 1 Nov 26 0
- Resource “brief-2026-10-17” was removed ▼ functional
- New resource “brief-2026-10-31” functional
- 31 Oct 26 0
- Resource “brief-2026-10-16” was removed ▼ functional
- New resource “brief-2026-10-30” functional
- 30 Oct 26 0
- Resource “deep-dive-occ-fdic-unsafe-unsound-rule-changed” was removed ▼ functional
- Resource “brief-2026-10-15” was removed ▼ functional
- New resource “deep-dive-occ-stablecoin-rule-tokenized-deposit-yield-carve” functional
- New resource “brief-2026-10-29” functional
- 29 Oct 26 0
- Resource “brief-2026-10-14” was removed ▼ functional
- New resource “brief-2026-10-28” 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 · Probed https://lexregpulse.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lexregpulse.com | CN=YE1,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 69cae7bc183c85dd603ddc1036c20765626 |
| SANs: *.lexregpulse.com, lexregpulse.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of lexregpulse.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| lexregpulse.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self';style-src 'self' 'nonce-D0ZynUroQzm3Y61pADhA6w==';script-src 'self' 'nonce-D0ZynUroQzm3Y61pADhA6w==';img-src 'self' data: https:;connect-src 'self' https: wss:;font-src 'self' https: data:;object-src 'none';media-src 'self';frame-src 'none';base-uri 'self';form-action 'self';frame-ancestors 'self';script-src-attr 'none';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lexregpulse.com/mcp | Verified | 200 | |
| http (plaintext) | http://lexregpulse.com/mcp | HTTPS enforced | 301 | https://lexregpulse.com/mcp |
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 ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many posts, newest first (default 10, max 50). |
No output schema declared.
No examples provided.
get_daily_briefing ~182
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, …
| 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 ~63
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.
| 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 ~58
A LinkedIn-ready post drafted from the day's sent brief: the lead in one paragraph, three headlines, a link to the edition.
| 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 ~71
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.
| 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 ~74
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.
| 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 ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many editions, newest first (default 14, max 60). |
No output schema declared.
No examples provided.
subscribe_to_daily_brief ~100
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.
| 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 is a hosted endpoint at https://lexregpulse.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · lexregpulse.com
claude mcp add --transport http rrgu26-bankregpulse-mcp-server 'https://lexregpulse.com/mcp'
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 hosted endpoint (https://lexregpulse.com/mcp).
Is the LexRegPulse: Banking Regulation Brief MCP server safe to use?
LexRegPulse: Banking Regulation Brief scores 81 out of 100 on VerifyMCP. 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 791 tokens of context every time the server is loaded.
Does the LexRegPulse: Banking Regulation Brief MCP server require authentication?
No. We connected to LexRegPulse: Banking Regulation Brief without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 did VerifyMCP test on the LexRegPulse: Banking Regulation Brief MCP server?
VerifyMCP ran 12 checks on LexRegPulse: Banking Regulation Brief, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about LexRegPulse: Banking Regulation Brief: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.