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。

  • 授權條款不適用

    託管服務按其提供方的條款使用,因此這裡不要求授權條款。此檢查項不計入百分比。