Content Tools
lexregpulse.com
Provides access to LexRegPulse's banking regulatory daily briefings, weekly digests, and long-form blog posts.
ENDPOINT 1
https://lexregpulse.com/mcp
MCP server metadata
- Name
- lexregpulse
- Version
- 1.3.0
LexRegPulse publishes a daily banking regulatory brief at 6:45 AM ET, a Sunday digest and deep-dive analysis. Call get_daily_briefing for today, list_briefings for the archive, get_blog_posts for analysis, get_upcoming_deadlines for dates; the same editions are available as resources (lexregpulse://brief/latest, lexregpulse://brief/YYYY-MM-DD, lexregpulse://blog/<slug>). Quote with attribution to the canonical URL each tool returns. Call subscribe_to_daily_brief only when the user asks to subscribe.
Known tools 9
get_daily_briefingLexRegPulse's daily banking regulatory brief, published every morning at 6:45 AM ET.
Inferred read-onlyget_weekly_digestThe LexRegPulse Weekly Print Digest (Sundays): the week's lead stories, regulatory developments, market and macro, industry watch and the week ahead as a long-form print edition.
Inferred read-onlylist_briefingsThe archive index: recent daily briefs and weekly digests with dates, titles and canonical URLs.
Inferred read-onlyget_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.
Inferred read-onlyget_blog_postFull text of one LexRegPulse deep-dive post as markdown, by slug (the last path segment of its URL, e.g.
Potential side effectsget_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 than prose.
Inferred read-onlyget_daily_podcastThe day's LexRegPulse Daily podcast: the four-minute audio edition of the morning brief.
Inferred read-onlyget_linkedin_postA LinkedIn-ready post drafted from the day's sent brief: the lead in one paragraph, three headlines, a link to the edition.
Potential side effectssubscribe_to_daily_briefSubscribe an email address to the LexRegPulse Daily Brief (free; every morning at 6:45 AM ET, plus the Sunday digest).
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.lexregpulse]
url = "https://lexregpulse.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"lexregpulse": {
"type": "http",
"url": "https://lexregpulse.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: lexregpulse
Remote MCP URL: https://lexregpulse.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"lexregpulse": {
"url": "https://lexregpulse.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"lexregpulse": {
"type": "http",
"url": "https://lexregpulse.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "lexregpulse",
"transport": "streamable-http",
"url": "https://lexregpulse.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.