# LexRegPulse: Banking Regulation Brief (remote · lexregpulse.com)

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

- Trust score: 81/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `lexregpulse.com`: 81/100 (this document), [markdown](https://verifymcp.io/servers/rrgu26-bankregpulse-mcp-server/lexregpulse.md), [page](https://verifymcp.io/servers/rrgu26-bankregpulse-mcp-server/lexregpulse)
- npm · `bankregpulse-mcp-server`: 85/100, [markdown](https://verifymcp.io/servers/rrgu26-bankregpulse-mcp-server/bankregpulse-mcp-server.md), [page](https://verifymcp.io/servers/rrgu26-bankregpulse-mcp-server/bankregpulse-mcp-server)

## Channel facts

- Endpoint: `https://lexregpulse.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1974 tokens (~58/item across 34 items; 9 tools + 25 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http rrgu26-bankregpulse-mcp-server 'https://lexregpulse.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "rrgu26-bankregpulse-mcp-server": {
      "url": "https://lexregpulse.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "rrgu26-bankregpulse-mcp-server": {
      "type": "http",
      "url": "https://lexregpulse.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.rrgu26-bankregpulse-mcp-server]
url = "https://lexregpulse.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rrgu26-bankregpulse-mcp-server": {
      "type": "remote",
      "url": "https://lexregpulse.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add rrgu26-bankregpulse-mcp-server --url 'https://lexregpulse.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  rrgu26-bankregpulse-mcp-server:
    url: "https://lexregpulse.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "rrgu26-bankregpulse-mcp-server": {
      "Transport": "http",
      "Url": "https://lexregpulse.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add rrgu26-bankregpulse-mcp-server -t streamable-http -u 'https://lexregpulse.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "rrgu26-bankregpulse-mcp-server": {
      "type": "http",
      "url": "https://lexregpulse.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 81, 0)

- [functional regression] Resource “brief-2026-10-21” was removed
- [functional] Stability: pass → 0.97
- [functional] New resource “brief-2026-11-04”

### 2026-11-04 (score 81, 0)

- [functional regression] Resource “brief-2026-10-20” was removed
- [functional] New resource “brief-2026-11-03”

### 2026-11-03 (score 81, 0)

- [functional regression] Resource “brief-2026-10-19” was removed
- [functional] New resource “brief-2026-11-02”

### 2026-11-02 (score 81, 0)

- [functional regression] Resource “digest-2026-10-18” was removed
- [functional] New resource “digest-2026-11-01”

### 2026-11-01 (score 81, 0)

- [functional regression] Resource “brief-2026-10-17” was removed
- [functional] New resource “brief-2026-10-31”

### 2026-10-31 (score 81, 0)

- [functional regression] Resource “brief-2026-10-16” was removed
- [functional] New resource “brief-2026-10-30”

### 2026-10-30 (score 81, 0)

- [functional regression] Resource “deep-dive-occ-fdic-unsafe-unsound-rule-changed” was removed
- [functional regression] 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”

### 2026-10-29 (score 81, 0)

- [functional regression] Resource “brief-2026-10-14” was removed
- [functional] New resource “brief-2026-10-28”

## MCP tools (9)

### `get_daily_briefing` (~182 tokens)

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, …

Input parameters:

- `date` (string): Optional edition date, YYYY-MM-DD. Defaults to the most recent edition.

### `get_weekly_digest` (~74 tokens)

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.

Input parameters:

- `date` (string): Optional Sunday date, YYYY-MM-DD. Defaults to the latest digest.

### `list_briefings` (~80 tokens)

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.

Input parameters:

- `limit` (integer): How many editions, newest first (default 14, max 60).

### `get_blog_posts` (~98 tokens)

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.

Input parameters:

- `limit` (integer): How many posts, newest first (default 10, max 50).

### `get_blog_post` (~65 tokens)

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").

Input parameters:

- `slug` (string, required): Post slug from get_blog_posts or the URL.

### `get_upcoming_deadlines` (~71 tokens)

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.

Input parameters:

- `days` (integer): Window in days from today (default 21, max 90).

### `get_daily_podcast` (~63 tokens)

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.

Input parameters:

- `date` (string): Optional edition date, YYYY-MM-DD. Defaults to the most recent edition.

### `get_linkedin_post` (~58 tokens)

A LinkedIn-ready post drafted from the day's sent brief: the lead in one paragraph, three headlines, a link to the edition.

Input parameters:

- `date` (string): Optional edition date, YYYY-MM-DD. Defaults to the most recent edition.

### `subscribe_to_daily_brief` (~100 tokens)

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.

Input parameters:

- `email` (string, required): The user's email address.
- `first_name` (string): Optional first name for the greeting.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/rrgu26-bankregpulse-mcp-server/lexregpulse#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 81
- 2026-10-28: 81
- 2026-10-27: 81
- 2026-10-26: 81
- 2026-10-25: 81
- 2026-10-24: 81
- 2026-10-23: 81
- 2026-10-22: 81
- 2026-10-21: 81
- 2026-10-20: 81
- 2026-10-19: 81
- 2026-10-18: 80
- 2026-10-17: 80
- 2026-10-16: 80
- 2026-10-15: 79
- 2026-10-14: 79
- 2026-10-13: 78
- 2026-10-12: 78
- 2026-10-10: 77
- 2026-10-09: 76
- 2026-10-05: 74
- 2026-10-04: 74
- 2026-10-03: 73

## Common questions

### 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.

## Links

- Remote endpoint: https://lexregpulse.com/mcp
- Repository: https://github.com/RRGU26/bankregpulse-mcp-server
- Website: https://lexregpulse.com/
- Changelog RSS feed: https://verifymcp.io/servers/rrgu26-bankregpulse-mcp-server/lexregpulse.xml
- Changelog JSON feed: https://verifymcp.io/servers/rrgu26-bankregpulse-mcp-server/lexregpulse/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/rrgu26-bankregpulse-mcp-server/lexregpulse.json
- HTML version of this page: https://verifymcp.io/servers/rrgu26-bankregpulse-mcp-server/lexregpulse