Skip to content

LexRegPulse: Banking Regulation Brief

by RRGU26 · remote · local (npm) · no sign-in to list tools · v1.3.0 · published by GitHub user RRGU26

Daily US banking regulation brief, weekly digest, archive and comment-deadline tracker. No key.

Deletes · 1Changes · 1
CompareRegistry entry

9 tools: 1 can delete or cancel things, 1 change things and 7 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http bankregpulse https://lexregpulse.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

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 7Claude Code: allow
  • get_blog_postFull text of one LexRegPulse deep-dive post as markdown, by slug (the last path segment of its URL, e.g.No findings

    Why it is in this group

    • The name "get_blog_post" says "get": a word for reading.
    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…No findings

    Why it is in this group

    • The name "get_blog_posts" says "get": a word for reading.
    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.No findings

    Why it is in this group

    • The name "get_linkedin_post" says "get": a word for reading.
    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…No findings

    Why it is in this group

    • The name "get_upcoming_deadlines" says "get": a word for reading.
    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.

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/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.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. It assumes the server is installed as bankregpulse. Review it before you use it.