LexRegPulse reads thousands of regulatory documents, market moves and industry signals every morning and publishes the ones that change a decision. This server gives your agent that output directly: the daily brief (6:45 AM ET, every day), the Sunday print digest, the searchable archive, Lex's deep-dive analysis pieces, and a deterministic deadline tracker built from the Federal Register's structured fields. Built for people who make decisions inside banks, fintechs, law firms and consultancies: treasurers, CROs, general counsel, compliance officers, deal lawyers and the founders dealing with their first MRA. Coverage spans the OCC, FDIC, Federal Reserve, CFPB, FinCEN, OFAC, SEC, CFTC, NCUA and all fifty state regulators, with the market and industry context that makes a rule matter now: rates, funding, deal flow, competitors. Every figure in the brief is traced to a primary source and every edition is scored by an independent QA pass before it sends. Responses come back as markdown with the canonical lexregpulse.com URL and a cite line, so your agent can quote a bullet and link straight to it. Tools get_daily_briefing today's brief, or any date · get_weekly_digest the Sunday edition · list_briefings the archive index · get_blog_posts and get_blog_post deep-dive analysis by Lex · get_upcoming_deadlines comment windows closing and rules taking effect · get_daily_podcast the four-minute audio edition · get_linkedin_post a post drafted from the day's brief. Try asking What's in this morning's banking regulatory brief?" · "Which comment periods close in the next two weeks?" · "What did LexRegPulse say about the OCC-FDIC unsafe-or-unsound rule?" · "Summarize last week's regulatory developments for a bank treasurer." Read-only over published content. Site guide for agents: https://lexregpulse.com/llms.txt

MCP readiness

B · 84/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	24/25	Endpoint answers the MCP initialize handshake (4218 ms); slow response -1.
Protocol revision	6/10	Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 9 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Slow (4218 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 75% of peers; This listing 84 · peer median 81
Latency: Faster than 46% of peers; This listing 362 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Protocol revision −4 — Support the current protocol revision.
Now: Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-06-25 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/bankregpulse/lexreg/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/bankregpulse/lexreg/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://lexregpulse.com/

Listed at (smithery)

https://lexregpulse.com/