the-metis-fca-handbook-ai-harness-mcp server
io.github.99blakeD99/the-metis-fca-handbook-ai-harness-mcp99blakeD99streamable-httpv0.1.13Scanned
MCP server for FCA Handbook compliance analysis with verbatim citations.
1 tool: 1 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the the-metis-fca-handbook-ai-harness-mcp server can do
The the-metis-fca-handbook-ai-harness-mcp server is published by the GitHub account 99blakeD99. It has 1 tool. It can create or change data (1 tool: evaluate_fca_handbook_applicability), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 0.1.13.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
1 tool
Changes things 1Claude Code: ask
evaluate_fca_handbook_applicabilityEvaluate which FCA Handbook entries apply to a situation as input by the user, using the Metis FCA Handbook AI Harness.1 finding
Why it is in this group
- The name "evaluate_fca_handbook_applicability" says "evaluate": a word for a change.
Findings
- Info
The description is 4,067 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...efining" above for when to switch and why to confirm with the user first."
Description, as the server wrote it Evaluate 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 obligations for a specific firm/product/service. This call takes 60-120 seconds in 'quick' mode and 90-120 seconds in 'full' mode, and the longest stretch, the main reasoning step (node 6), shows nothing new on the user's screen, so it can look as if the call has crashed. Before you call the tool, always tell the user in plain words that the Harness is about to do substantial reasoning work, that this takes a minute or two, and that it has not crashed if the screen is quiet. Do not go silent. The Harness attempts to stream progress messages as each reasoning node completes - if you receive them, relay each one to the user as it arrives — they contain genuine detail, not filler. Billing rule: every call is a separate charge. After a result arrives, never start another call, whether 'quick' or 'full', in the same turn or without the user's explicit yes to that specific further run, even when the refinement suggestions make another pass look clearly worthwhile. First call: use analysis_mode='quick'. Before calling, check whether you already have (from this conversation, documents you were given, or other tools) grounded answers to these six things — the specific compliance question, the product/service, who is providing it (platform/adviser/ bank/etc.), its key features, the target market (retail/institutional/ professional/customer segment), and what data it handles. If you are missing more than one or two, ask the user for them first rather than calling with thin input. Every call is billed at a flat rate regardless of input quality, so a vague call incurs unnecessary cost. The result includes refinement_suggestions — gaps the Harness could not resolve from user_input alone, typically subtler than the six basics above (e.g. a regulatory edge case, not a missing fact you could have just asked for). For each suggestion worth pursuing, get the grounded information — retrieve it from this conversation, documents you were given, or other tools if you already have it; otherwise ask the user directly. Do not speculate or infer plausible-sounding detail you do not actually have — that reintroduces the hallucination risk this Harness exists to avoid, one level up. Refining (second call onward): use analysis_mode='full'. Either way, before calling again, stop and ask the user whether they want a further 'full' pass with the refined input, saying that it is a further charge, and wait for their answer — never call again unilaterally, and do not just list the gaps and stop. Repeat this pattern for further rounds if the new result still leaves suggestions worth resolving. The result's citations field contains verbatim quotes from the FCA Handbook — this is a core part of what the Harness offers, not generative invention, and distinct from the summary/obligations text. They can best be viewed as an Appendix. Citations can be long, so ask the user whether they want the relevant verbatim citations included, rather than omitting them by default as mere detail. Args: user_input: Everything together as one piece of text (up to 5000 characters) — the specific compliance question, the product/service, who is providing it, its key features, the target market, and what data it handles. On later rounds, refine all six using existing chat context and whatever additional detail later rounds have gathered. See "First call" and "Refining" above. analysis_mode: 'quick' for the first call (default, ~60-120 seconds); 'full' (~90-120 seconds) for refined calls after the first — detailed conditional reasoning: conditions, interactions between rules, and second-order implications. See "Refining" above for when to switch and why to confirm with the user first.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:24 UTC, unchanged since Oct 28, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://fcahandbookharnessimplementation.onrender.com/mcp: tools/list returned 1 tool to an anonymous client, including evaluate_fca_handbook_applicability (write)
Findings
Matches of fixed checks, with the text they matched.
The description is 4,067 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...efining" above for when to switch and why to confirm with the user first."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.13. Values in angle brackets are yours to fill in.
claude mcp add --transport http the-metis-fca-handbook-ai-harness https://fcahandbookharnessimplementation.onrender.com/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http the-metis-fca-handbook-ai-harness https://fcahandbookharnessimplementation.onrender.com/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__the-metis-fca-handbook-ai-harness__evaluate_fca_handbook_applicability"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as the-metis-fca-handbook-ai-harness. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.99blakeD99/the-metis-fca-handbook-ai-harness-mcp/verify?hash=60b7af6e7db793c441abe208171a64fa3c27a08b94373ffafe6813edc7447774" | jq -e '.changed == false'Pinned hash 60b7af6e7db7, from Nov 10, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.99blakeD99/the-metis-fca-handbook-ai-harness-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.99blakeD99/the-metis-fca-handbook-ai-harness-mcp)Source: MCP Registry · repository. Synced Oct 28, 2026, 18:17 UTC.
the-metis-fca-handbook-ai-harness-mcp server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the the-metis-fca-handbook-ai-harness-mcp server safe?
- No scan can promise that. What its definitions show: 1 tool, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the the-metis-fca-handbook-ai-harness-mcp server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the the-metis-fca-handbook-ai-harness-mcp server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the the-metis-fca-handbook-ai-harness-mcp server have?
- 1 tool: 1 write. evaluate_fca_handbook_applicability.
Does the the-metis-fca-handbook-ai-harness-mcp server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the the-metis-fca-handbook-ai-harness-mcp server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the the-metis-fca-handbook-ai-harness-mcp server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.