# Reg Monitoring (remote · mcp.regmonitoring.com)

Financial regulatory updates, deadlines and enforcement actions from regulators worldwide.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.regmonitoring.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-regmonitoring-regulatory-updates/mcp.md), [page](https://verifymcp.io/servers/com-regmonitoring-regulatory-updates/mcp)

## Channel facts

- Endpoint: `https://mcp.regmonitoring.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2377 tokens (~339/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 95% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 Reg Monitoring MCP server?

Reg Monitoring is a hosted endpoint at https://mcp.regmonitoring.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 com-regmonitoring-regulatory-updates 'https://mcp.regmonitoring.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-regmonitoring-regulatory-updates": {
      "url": "https://mcp.regmonitoring.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-regmonitoring-regulatory-updates": {
      "type": "http",
      "url": "https://mcp.regmonitoring.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-regmonitoring-regulatory-updates]
url = "https://mcp.regmonitoring.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-regmonitoring-regulatory-updates": {
      "type": "remote",
      "url": "https://mcp.regmonitoring.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-regmonitoring-regulatory-updates --url 'https://mcp.regmonitoring.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-regmonitoring-regulatory-updates:
    url: "https://mcp.regmonitoring.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-regmonitoring-regulatory-updates": {
      "Transport": "http",
      "Url": "https://mcp.regmonitoring.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-regmonitoring-regulatory-updates -t streamable-http -u 'https://mcp.regmonitoring.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-regmonitoring-regulatory-updates": {
      "type": "http",
      "url": "https://mcp.regmonitoring.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-04 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 68, +8)

- [security improvement] Authorization: unverified → partial
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] Tool “regmonitoring_get_monthly_briefing” changed its title: Get monthly briefing
- [cosmetic] Tool “regmonitoring_get_stats” changed its title: Get coverage statistics
- [cosmetic] Tool “regmonitoring_get_taxonomy” changed its title: Get filter values
- [cosmetic] Tool “regmonitoring_get_update” changed its title: Get update detail
- [cosmetic] Tool “regmonitoring_list_deadlines” changed its title: List regulatory deadlines
- [cosmetic] Tool “regmonitoring_search_enforcement” changed its title: Search enforcement actions
- [cosmetic] Tool “regmonitoring_search_updates” changed its title: Search regulatory updates

### 2026-11-01 (score 60)

First indexed and scored.

## MCP tools (7)

### `regmonitoring_search_updates` (~542 tokens)

Search regulatory updates

Search regulatory updates from financial regulators across 20 jurisdictions — news, enforcement actions, consultations, policy statements, guidance, final rules, speeches and warnings, from 2011 to today. Filter by regulator, jurisdiction, topic, sector, firm type, content type, urgency, importance and date. Use published_after to answer "what changed recently"; use significance_min (4+) to cut routine noise. Returns compact records with a canonical regmonitoring.com URL for each — cite it. Call regmonitoring_get_update for the full text and analysis of any single result.

Input parameters:

- `content_types` (array): Kind of document.
- `firm_types` (array): Types of firm affected. Records tagged "All Firms" are cross-cutting and match every firm-type filter, so filtering by "Asset Manager" also returns updates that apply to everyone.
- `has_analysis` (boolean): Only records carrying AI analysis (about 89% of the corpus).
- `jurisdictions` (array): Lowercase jurisdiction codes, e.g. ["uk","us","eu"]. Call regmonitoring_get_taxonomy for the valid list — guessing "UK" or "United Kingdom" returns nothing.
- `limit` (integer): Results to return, default 20, max 100.
- `offset` (integer): Skip this many results, for paging.
- `published_after` (string): ISO date (YYYY-MM-DD), inclusive. This is how you answer "what changed this week" — no separate tool is needed.
- `published_before` (string): ISO date (YYYY-MM-DD), inclusive.
- `query` (string): Free-text search over title and summary. All words must appear (case-insensitive). Omit to browse by filters alone.
- `regulators` (array): Lowercase regulator codes, e.g. ["fca","sec","esma"]. See regmonitoring_get_taxonomy.
- `sectors` (array): Industry segments.
- `significance_min` (integer): Minimum importance, 1 (routine) to 5 (major). Every record is scored, so this is the most reliable way to cut noise. 4+ is "worth a compliance officer's attention".
- `sort` (string): Default "newest". "relevance" ranks by query match and falls back to newest when no query is given.
- `topics` (array): Regulatory themes. Values are exact, e.g. "AML / Financial Crime".
- `urgency` (array): Urgency. NOTE: about 35% of records have no urgency set, and filtering on this excludes all of them. Prefer significance_min unless urgency is specifically what you want.

### `regmonitoring_get_update` (~222 tokens)

Get update detail

Full detail for one regulatory update, by id or slug: the AI analysis (executive summary, what changed, who is affected, actions required, key dates, compliance impact, citations), any deadline, any enforcement penalty data, and related records. Call this after regmonitoring_search_updates when you need to judge what an update actually requires. Check the analysis `depth` field: "deep" means real structured analysis, "rationale" means only a short classification note. Set include_source_text to read the original document text.

Input parameters:

- `id` (string): Record id, as returned by regmonitoring_search_updates.
- `include_source_text` (boolean): Include the full scraped text of the source document. Off by default because it can run to tens of thousands of characters. Present on ~72% of records; ask for it when the analysis is not enough to j…
- `slug` (string): URL slug, the last path segment of a regmonitoring.com/updates/... link. Use this or id; id is faster.

### `regmonitoring_list_deadlines` (~357 tokens)

List regulatory deadlines

Regulatory deadlines with dates: consultation response dates, compliance deadlines, and rule effective dates, filterable by date range, status, firm type, jurisdiction and regulator. This is the tool for "what is coming up for my firm" and for building a compliance calendar. Status is derived at query time, never stored, so it is always current; buckets do not overlap (within_90 excludes anything already within 30 days). Set high_confidence_only when the answer will be planned against.

Input parameters:

- `content_types` (array): Kind of document the deadline came from.
- `deadline_types` (array): response_due = consultation closes; compliance_deadline = firms must have complied; effective_date = rule takes effect.
- `firm_types` (array): Records tagged "All Firms" are cross-cutting and match every firm-type filter.
- `from` (string): Earliest deadline date, YYYY-MM-DD, inclusive.
- `high_confidence_only` (boolean): Only deadlines extracted with high confidence. Worth setting when the answer will be planned against — a wrong date is worse than no date.
- `jurisdictions` (array): Lowercase jurisdiction codes. See regmonitoring_get_taxonomy.
- `limit` (integer): Default 50, max 100.
- `offset` (integer)
- `regulators` (array): Lowercase regulator codes. See regmonitoring_get_taxonomy.
- `status` (array): Derived from the date at query time, never stored. "within_90" means within 90 days but not within 30 — the buckets do not overlap. Omit this and pass from/to for a plain date range.
- `to` (string): Latest deadline date, YYYY-MM-DD, inclusive.

### `regmonitoring_search_enforcement` (~394 tokens)

Search enforcement actions

Enforcement actions across regulators and jurisdictions, with structured penalty data where it has been parsed: entity penalised, amount, currency, breach categories, and whether the penalty is final. Use for "what has this regulator fined firms for", "has this firm been penalised", or precedent research on a breach type. IMPORTANT: only about a quarter of enforcement records have a parsed penalty amount — extraction requires full source text, which many records lack. Do NOT answer "what are the largest fines" from sort=largest_penalty alone: it ranks only the parsed subset. Check the `note` field, which reports how many actions were excluded. Amounts are never converted between currencies.

Input parameters:

- `currency` (string): ISO code, e.g. "GBP", "USD", "EUR".
- `entity` (string): Case-insensitive substring of the penalised firm or individual name.
- `final_only` (boolean): Only penalties recorded as final, excluding proposed or under appeal.
- `jurisdictions` (array): Lowercase jurisdiction codes.
- `limit` (integer): Default 20, max 100.
- `min_penalty` (number): Minimum penalty amount, in the currency of the record — amounts are NOT converted between currencies, so combine this with `currency` if you need comparable figures.
- `offset` (integer)
- `published_after` (string): YYYY-MM-DD, inclusive.
- `published_before` (string): YYYY-MM-DD, inclusive.
- `regulators` (array): Lowercase regulator codes.
- `sort` (string): Default "newest". "largest_penalty" excludes records with no amount.
- `with_penalty_amount_only` (boolean): Only records carrying a structured penalty amount. IMPORTANT: this is a small minority of enforcement records — most enforcement actions are indexed without a parsed figure. Leaving this false return…

### `regmonitoring_get_taxonomy` (~110 tokens)

Get filter values

Every valid filter value with the number of records carrying it: jurisdiction and regulator codes with their full names, content types, topics, sectors, firm types, urgency levels and deadline types. CALL THIS FIRST if you are unsure of any filter value. Values are exact and case-sensitive — "uk" not "UK", "AML / Financial Crime" not "AML" — and a wrong value returns zero results rather than an error, which is indistinguishable from the data genuinely being empty.

### `regmonitoring_get_stats` (~101 tokens)

Get coverage statistics

Coverage statistics for the regmonitoring.com regulatory corpus: how many updates are indexed, the date range they span, how many regulators and jurisdictions are represented, and how many records carry AI analysis, a deadline, a penalty amount or an urgency rating. Call this before making claims about what the corpus does or does not contain — most records have no penalty amount, so an empty enforcement result usually means the data is absent rather than that no enforcement occurred.

### `regmonitoring_get_monthly_briefing` (~165 tokens)

Get monthly briefing

The Reg Monitoring monthly briefing: an editor-written round-up of the most important financial services regulatory updates of one month, grouped by region (North America; UK and Europe; Asia-Pacific, Middle East and Africa), with a one-line overview per region and the deadlines in the 60 days after it was sent. Use for "what happened in regulation last month" or "catch me up", where a curated summary beats a raw search. Omit `month` for the latest issue. The response includes how to receive the briefing by email each month.

Input parameters:

- `month` (string): The month the issue covers, as YYYY-MM (e.g. "2026-10"). Omit for the latest issue. Each issue covers the previous calendar month.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-regmonitoring-regulatory-updates/mcp#diagnostics

## Score history

- 2026-11-05: 69
- 2026-11-04: 69
- 2026-11-03: 68
- 2026-11-02: 68
- 2026-11-01: 60

## Common questions

### What is the Reg Monitoring MCP server?

Reg Monitoring is an MCP server listed in the public MCP registry as com.regmonitoring/regulatory-updates. Financial regulatory updates, deadlines and enforcement actions from regulators worldwide. This page covers its hosted endpoint (https://mcp.regmonitoring.com/mcp).

### Is the Reg Monitoring MCP server safe to use?

Reg Monitoring scores 69 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 Reg Monitoring MCP server expose?

Reg Monitoring exposes 7 tools: regmonitoring_search_updates, regmonitoring_get_update, regmonitoring_list_deadlines, regmonitoring_search_enforcement, regmonitoring_get_taxonomy, and 2 more. Their descriptions and schemas cost roughly 1,891 tokens of context every time the server is loaded.

### Does the Reg Monitoring MCP server require authentication?

No. We connected to Reg Monitoring without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Reg Monitoring MCP server still maintained?

Reg Monitoring 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 Reg Monitoring MCP server?

VerifyMCP ran 13 checks on Reg Monitoring, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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://mcp.regmonitoring.com/mcp
- Website: https://regmonitoring.com/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/com-regmonitoring-regulatory-updates/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-regmonitoring-regulatory-updates/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-regmonitoring-regulatory-updates/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-regmonitoring-regulatory-updates/mcp