Global law
The law of nearly every country on earth, any date: read it, see what changed it, check citations.
MCP server for FCA Handbook compliance analysis with verbatim citations.
作者提供的原文
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 20/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 The Metis Fca Handbook AI Harness MCP。按照 https://mcp.popnx.com/i/99blaked99-the-metis-fca-handbook-ai-harness-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(fcahandbookharnessimplementation.onrender.com) · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 5 分钟
需要 The Metis Fca Handbook AI Harness MCP 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
The Metis Fca Handbook AI Harness MCPhttps://fcahandbookharnessimplementation.onrender.com/mcp在 Request headers 下添加这个名称和值
AuthorizationBearer <在这里粘贴你的密钥>只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsThe Metis Fca Handbook AI Harness MCP
用 The Metis Fca Handbook AI Harness MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 The Metis Fca Handbook AI Harness MCP,或回答中出现 The Metis Fca Handbook AI Harness MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 The Metis Fca Handbook AI Harness MCP
The Metis Fca Handbook AI Harness MCP 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式
A · 使用能连接 The Metis Fca Handbook AI Harness MCP 的应用
B · 法律与政府数据 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code · 约 5 分钟
需要 The Metis Fca Handbook AI Harness MCP 的密钥(在开发者网站创建)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user the-metis-fca-handbook-ai-harness https://fcahandbookharnessimplementation.onrender.com/mcp --header 'Authorization: Bearer {metis_api_key}'按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 The Metis Fca Handbook AI Harness MCP 在列表中并显示已连接
用 The Metis Fca Handbook AI Harness MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 The Metis Fca Handbook AI Harness MCP,或回答中出现 The Metis Fca Handbook AI Harness MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 5 分钟
需要 The Metis Fca Handbook AI Harness MCP 的密钥(在开发者网站创建)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
在 The Metis Fca Handbook AI Harness MCP 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 The Metis Fca Handbook AI Harness MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 The Metis Fca Handbook AI Harness MCP,或回答中出现 The Metis Fca Handbook AI Harness MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 5 分钟
需要 The Metis Fca Handbook AI Harness MCP 的密钥(在开发者网站创建)
打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。
获取密钥的方法见下方开发者的 README
在 The Metis Fca Handbook AI Harness MCP 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 The Metis Fca Handbook AI Harness MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 The Metis Fca Handbook AI Harness MCP,或回答中出现 The Metis Fca Handbook AI Harness MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://fcahandbookharnessimplementation.onrender.com/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user the-metis-fca-handbook-ai-harness https://fcahandbookharnessimplementation.onrender.com/mcp --header 'Authorization: Bearer {metis_api_key}'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"the-metis-fca-handbook-ai-harness": {
"url": "https://fcahandbookharnessimplementation.onrender.com/mcp",
"headers": {
"Authorization": "Bearer {metis_api_key}"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"the-metis-fca-handbook-ai-harness": {
"type": "http",
"url": "https://fcahandbookharnessimplementation.onrender.com/mcp",
"headers": {
"Authorization": "Bearer {metis_api_key}"
}
}
}
}Claude Code
claude mcp add --scope user the-metis-fca-handbook-ai-harness --env METIS_API_KEY=your-value -- uvx fca-handbook-harness-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"the-metis-fca-handbook-ai-harness": {
"command": "uvx",
"args": [
"fca-handbook-harness-mcp"
],
"env": {
"METIS_API_KEY": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"the-metis-fca-handbook-ai-harness": {
"command": "uvx",
"args": [
"fca-handbook-harness-mcp"
],
"env": {
"METIS_API_KEY": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"the-metis-fca-handbook-ai-harness": {
"type": "stdio",
"command": "uvx",
"args": [
"fca-handbook-harness-mcp"
],
"env": {
"METIS_API_KEY": "your-value"
}
}
}
}METIS_API_KEY 机密 必填 envMETIS_BASE_URL env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
工具名称和描述与服务器在 2026年11月17日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
evaluate_fca_handbook_applicabilityEvaluate which FCA Handbook entries apply to a situation as input by the user, using the Metis FCA Handbook AI Harness. Calls a live compliance reasoning run, billed to the configured account. Use for questions involving the FCA Handbook, including authorisation, permissions, or
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月21日
注册名称已通过 GitHub 账户 99blakeD99 验证,该账户拥有此仓库
代码最后更新于23天前
使用 MIT
在 149 毫秒内响应(HTTP 200)
无需登录
已读取 1 个工具描述,未发现针对 AI 的隐藏指令
OSV.dev 中没有 fca-handbook-harness-mcp@0.1.13 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/99blaked99-the-metis-fca-handbook-ai-harness-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization, METIS_API_KEY
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于23天前,最新版本(0.1.13)于23天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:Global law, Open Legal Data (Germany), LibreJustice, InfraNode, Fedlex Connector
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
The law of nearly every country on earth, any date: read it, see what changed it, check citations.
German court decisions (Rechtsprechung) and laws (Gesetze) with citation graph and citation checks.
Search French-language and European case law and French legal texts (codes, statutes, treaties).
Keyless open data for 84 German cities: 12 lean read-only MCP tools covering 67 data types.
Search Swiss federal legislation: laws, articles, amendments via the Fedlex SPARQL endpoint.
| 本项 The Metis Fca Handbook AI Harness MCP | Global law | Open Legal Data (Germany) | LibreJustice | InfraNode | Fedlex Connector | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | NOASSERTION | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
An MCP (Model Context Protocol) server that integrates the Metis FCA Handbook AI Harness into your AI workflow. MCP is supported by Claude, OpenAI, Gemini, and most desktop/IDE MCP clients (Cursor, Windsurf, Cline, and others) — this README uses Claude Code as the tested, worked example for the recommended remote server, and Claude Code and Claude Desktop for the local fallback; adjust the configuration steps to fit your own client.
Source & full documentation: github.com/99blakeD99/the-metis-fca-handbook-ai-harness-mcp-files
evaluate_fca_handbook_applicabilityEvaluate which FCA Handbook entries apply to an entity, via the Metis FCA Handbook AI Harness. One-shot: no session, no conversation state. Supports quick mode (60-120 seconds, default) and full mode (90-120 seconds, more detailed). Returns a compliance report with verbatim citations and refinement suggestions, which identify gaps in the information you provided and how to fill them.
Experience the Harness interactively before integrating:
https://fcahandbookharnessimplementation.onrender.com
Email the-metis-fca-handbook-ai-harness@jbmd.co.uk and request a free temporary Access Code.
Ask compliance questions in natural language and watch each reasoning step unfold in real-time.
The Harness is built on proven principles:
Embed FCA reasoning as a service within your compliance platform. Users ask natural-language questions; your platform calls the Harness and presents structured reasoning.
Agents building compliance workflows can include FCA Handbook reasoning as a composed tool—no external API calls, just MCP configuration.
Integrate into document review or due-diligence pipelines. Automatically screen new rules against FCA applicability.
FS firms screening MCP servers will find:
Setup is a one-off task for whoever manages your AI tools. Once it is connected, your compliance staff simply ask their AI assistant.
Which setup to use:
Authorization header. Nothing is installed; you need only a URL and your API key. This is the recommended setup.Both give the same tool and the same results, billed at the same rate. For Claude Desktop, use the local server.
Follow these rules in addition to the steps below:
--scope user unless the user asks for a project-only setup. For Claude Desktop, use the local setup. For other clients, use the settings in step 2b.METIS_API_KEY. Never ask the user to paste the key into this conversation, never write it to a file in a project or repository, and never put it as a literal value in a configuration file. Configuration files use the ${METIS_API_KEY} reference shown below. To check that it is set without printing it, run [ -n "$METIS_API_KEY" ] && echo set || echo unset. If it is not set, tell the user how to set it (step 2), wait until they confirm it is set, and change no configuration and use no placeholder in the meantime. If the user pastes their key into the conversation anyway, do not use it, repeat it or write it anywhere, and suggest they regenerate it on the dashboard.claude mcp add, or in .mcp.json (one project) or ~/.claude.json (all projects, which is where claude mcp add --scope user writes). Use the CLI where you can: ~/.claude.json is the route we tested, and we have not tested a hand-made ~/.mcp.json. Never put an mcpServers entry in .claude/settings.json.evaluate_fca_handbook_applicability is listed. In Claude Code, run claude mcp list to see whether the server is connected. /mcp lists its tools, but it is a slash command that only the user can run, so ask them to run it. In other clients, check the client's MCP settings screen. Do not call the tool to test it. Every call is a real analysis run, billed to the user's account, and takes one to two minutes or more. Call it only when the user asks a real FCA Handbook question.⏸ Pending approval (the user must approve the server; see "Verify the connection" below) and a 401 error on first use (see Troubleshooting).If you already have an API key, skip to step 2.
Visit the Metis account dashboard:
https://fcahandbookharnessimplementation.onrender.com
The remote server is at:
https://fcahandbookharnessimplementation.onrender.com/mcp
It uses the Streamable HTTP transport and expects your API key as a bearer token in the Authorization header of each request.
Important: Supply the key from an environment variable or secrets manager, never as a literal value in a configuration file that may be committed to a shared repository. Add this line to your shell startup file (~/.bashrc, ~/.zshrc, etc.), before launching your client, so the variable is present in the client's own process environment:
export METIS_API_KEY="sk_live_..."
Replace sk_live_... with your actual API key from your Metis account.
On Windows, run setx METIS_API_KEY "sk_live_..." in Command Prompt instead, then restart your client. In every case, start your client after the variable is set, from a terminal if you can: an app launched from the Dock, Spotlight or the Start menu may not see a variable set in a shell startup file.
The easiest route is the CLI, which writes the correct file for you. Quote the header exactly as shown (single quotes) so your shell does not expand ${METIS_API_KEY} before claude mcp add sees it. Otherwise your actual key is written into the config file as a literal, which is the hardcoding the note above warns against.
claude mcp add --transport http --scope user fca-handbook-harness-mcp https://fcahandbookharnessimplementation.onrender.com/mcp --header 'Authorization: Bearer ${METIS_API_KEY}'
A --scope user entry applies to every Claude Code project on the machine and stays until you run claude mcp remove. Use --scope project instead for a project-only setup. If you would rather edit the file directly, add it under the top-level mcpServers key of ~/.claude.json (all projects; this file also holds your other Claude Code settings, so edit it with care) or put it in .mcp.json in your project root (that project only). .mcp.json is a standalone file, not inside .claude/; Claude Code rejects an mcpServers key in .claude/settings.json.
{
"mcpServers": { "fca-handbook-harness-mcp": { "type": "http", "url": "https://fcahandbookharnessimplementation.onrender.com/mcp", "headers": { "Authorization": "Bearer ${METIS_API_KEY}" } } } }
Claude Code substitutes ${METIS_API_KEY} from your environment when it starts. If the variable is not set at that point, Claude Code sends the literal text ${METIS_API_KEY} as your key (and warns about it), which produces a 401 error that is easy to mistake for a bad key. Start Claude Code from a shell where [ -n "$METIS_API_KEY" ] && echo set prints set. If the tool does not appear after you add the server, restart Claude Code.
Cursor, VS Code (Copilot), Gemini CLI, Cline, and other developer tools and agent frameworks can connect to a remote MCP server when given a URL and a custom header. They should work with the settings below, but they have not been tested by us. Field names and file locations differ between clients and are still changing, so follow your client's own documentation for adding a remote MCP server.
https://fcahandbookharnessimplementation.onrender.com/mcpAuthorization: Bearer . Read the key from an environment variable if your client supports that.The syntax for referring to an environment variable differs between clients. For example, Cursor documents ${env:METIS_API_KEY} where Claude Code uses ${METIS_API_KEY}. Use your client's own syntax, and never a literal key.
A client that accepts only no authentication or OAuth for remote servers cannot send a static API key. Use the local server with that client.
Claude Code, first run only: the first time you launch claude (interactively, not with -p) in a project with a new or changed project-scoped .mcp.json, it shows a one-time trust/approval prompt for that server before connecting. Until you accept it, the server sits in a "pending approval" state and its tool is not actually available (running claude mcp list shows ⏸ Pending approval). Accept the prompt, or run /mcp in an existing session to approve it there. This gate does not apply to user scope (--scope user, stored in ~/.claude.json).
Once connected, you should see evaluate_fca_handbook_applicability available as a tool in your agent workflows. If it does not appear, check the Troubleshooting section below.
Verify by checking that the tool is listed. Connected in claude mcp list only means the server started: it does not prove your key is accepted. A key that was not set when your client started (the literal text ${METIS_API_KEY}