Reg Monitoring

com.regmonitoring由 regmonitoring.com 发布官方发布者v0.2.0更新于 Nov 2, 2026

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

已验证Streamable HTTP可网页运行金融知识与记忆

概览

AI 生成的概览

检索20个司法辖区金融监管机构的监管动态、截止期限与执法处罚,并提供AI分析与月度简报。

可以做什么
  • 按监管机构、辖区、主题、行业、内容类型、紧急程度和日期检索监管动态
  • 读取单条动态的完整AI分析、截止日期、罚款数据与相关记录
  • 列出有日期的义务,如征求意见截止、合规期限和规则生效日期
  • 检索执法行动,含结构化的罚款金额与违规类别
  • 查询有效的筛选值和语料覆盖统计
  • 获取按地区编排的编辑撰写月度简报
适用场景
适合合规、法务与风险相关问题:某金融监管机构发布了什么、处罚了什么、排定了哪些期限;也适合编制合规日历或回顾一个月的监管变化。
运行要求
远程 streamable HTTP 端点;未声明软件包、环境变量或请求头。服务器说明筛选值精确且区分大小写,建议先查询分类法工具。
安装前请注意
内容属于监管信息,不构成法律意见。覆盖范围本身并不均衡,空结果可能表示数据缺失而非确无此事,下结论前应先查看覆盖统计。月度简报工具会返回免费邮件订阅链接。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Reg Monitoring,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.regmonitoring%2Fregulatory-updates/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "reg-monitoring": {
      "type": "http",
      "url": "https://mcp.regmonitoring.com/mcp"
    }
  }
}

工具

7

regmonitoring_search_updates

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.

输入参数sortlimitqueryoffsettopicssectorsurgencyfirm_typesregulatorshas_analysiscontent_typesjurisdictions另有 3 个

regmonitoring_get_update

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.

输入参数idsluginclude_source_text

regmonitoring_list_deadlines

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.

输入参数tofromlimitoffsetstatusfirm_typesregulatorscontent_typesjurisdictionsdeadline_typeshigh_confidence_only

regmonitoring_search_enforcement

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.

输入参数sortlimitentityoffsetcurrencyfinal_onlyregulatorsmin_penaltyjurisdictionspublished_afterpublished_beforewith_penalty_amount_only

regmonitoring_get_taxonomy

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

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

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.

输入参数month

版本历史

1
  1. v0.2.0最新Nov 2, 2026

评分

已满足适用检查项的 83%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分

    请声明包含 README 的 GitHub 仓库,或在 OAuth 受保护资源元数据中提供 resource_documentation。

  • 许可证不适用

    托管服务按其提供方的条款使用,因此这里不要求许可证。此检查项不计入百分比。