# Metis FCA Handbook AI Harness — MCP Server An MCP (Model Context Protocol) server that integrates the Metis FCA Handbook AI Harness into Claude Desktop and other MCP-compatible agents. **Tool name:** `evaluate_fca_handbook_applicability` Use this tool to analyze FCA Handbook applicability for a product, service, or firm. Returns structured compliance reasoning with verbatim handbook citations. ## Why choose The Metis FCA Handbook AI Harness? - **Efficiency** Multiplies effectiveness of compliance advice. Saves £80+ in token fees per Harness run. - **Deals with "Hard Problem"**, in which LLMs' token incentives prioritise training data so results are unreliable. - **Verbatim citations** Quotes verbatim entries from the FCA Handbook. Other AI systems struggle to do this. - **Matches real-world need** You do not have to start off knowing which sections you are looking for. Carries out structured searches across all 10,000+ FCA Handbook entries. - **Secure Design** Harness compartmentalisation, one-shot structure, and statelessness fits natively with emerging AI agent security standards such as OWASP Top 10 for Agentic Applications 2026. - **AI Accessible** Integrates easily with AI workflows and agents. Your LLM can use it as a tool. ## Design Principles The Harness is built on proven principles: - **Stateless** — Each request is independent; no session coupling - **One-shot** — Complete analysis in a single call; no multi-turn state - **Clear contract** — Explicit input/output schemas for easy integration - **Hosted** — Single canonical source; no version drift or stale data ## Use Cases ### Compliance AI Platforms Embed FCA reasoning as a service within your compliance platform. Users ask natural-language questions; your platform calls the Harness and presents structured reasoning. ### AI Agent Workflows Agents building compliance workflows can include FCA Handbook reasoning as a composed tool—no external API calls, just MCP configuration. ### Compliance Review Automation Integrate into document review or due-diligence pipelines. Automatically screen new rules against FCA applicability. ## For Regulatory Screening FS firms screening MCP servers will find: - **Simple model:** Stateless, no hidden state, no background jobs - **Clear contract:** Explicit input schema, output schema, error modes - **Transparent updates:** Version pinning; no automatic upgrades - **Single point of failure:** If the Harness is down, it is obvious; no cascading config issues - **Audit-friendly:** All calls logged centrally, not distributed

MCP readiness

B · 82/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B+, 89.3/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (488 ms).
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	18/18 probes succeeded over 30 days (100%).
Tool declaration	5/10	Lists 1 tool(s) with descriptions.
Verified identity	7/10	Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	0/5	How to authenticate is not stated.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (488 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 55% of peers; This listing 82 · peer median 81
Latency: Faster than 34% of peers; This listing 465 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Tool declaration −5 — Declare every tool with a description and input schema.
Now: Lists 1 tool(s) with descriptions.
Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.
Verified identity −3 — Claim the listing and prove control of its domain.
Now: Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

agenstry since 2026-10-26 ↗ mcp-registry since 2026-10-28

How to connect

MCP endpoint (streamable-http)

https://fcahandbookharnessimplementation.onrender.com/mcp

JSON-RPC initialize probe

curl -X POST https://fcahandbookharnessimplementation.onrender.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://fcahandbookharnessimplementation.onrender.com

Listed at (agenstry)

https://agenstry.com/mcp/blakeD99/the-metis-fca-handbook-ai-harness-mcp