io.github.99blakeD99/the-metis-fca-handbook-ai-harness-mcp
PYPI · FCA-HANDBOOK-HARNESS-MCP · SCANNED SEP 20
MCP server for FCA Handbook compliance analysis with verbatim citations.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 32 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 17 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 556 tokens (~556/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.99blakeD99/the-metis-fca-handbook-ai-harness-mcp server?
io.github.99blakeD99/the-metis-fca-handbook-ai-harness-mcp runs locally as a PyPI package, launched with uvx fca-handbook-harness-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · fca-handbook-harness-mcp
claude mcp add 99blaked99-the-metis-fca-handbook-ai-harness-mcp -- uvx fca-handbook-harness-mcp
{
"mcpServers": {
"99blaked99-the-metis-fca-handbook-ai-harness-mcp": {
"command": "uvx",
"args": [
"fca-handbook-harness-mcp"
]
}
}
} {
"servers": {
"99blaked99-the-metis-fca-handbook-ai-harness-mcp": {
"command": "uvx",
"args": [
"fca-handbook-harness-mcp"
]
}
}
} codex mcp add 99blaked99-the-metis-fca-handbook-ai-harness-mcp -- uvx fca-handbook-harness-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"99blaked99-the-metis-fca-handbook-ai-harness-mcp": {
"type": "local",
"command": [
"uvx",
"fca-handbook-harness-mcp"
],
"enabled": true
}
}
} openclaw mcp add 99blaked99-the-metis-fca-handbook-ai-harness-mcp --command uvx --arg fca-handbook-harness-mcp
mcp_servers:
99blaked99-the-metis-fca-handbook-ai-harness-mcp:
command: "uvx"
args: ["fca-handbook-harness-mcp"] {
"McpServers": {
"99blaked99-the-metis-fca-handbook-ai-harness-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"fca-handbook-harness-mcp"
]
}
}
} assistant mcp add 99blaked99-the-metis-fca-handbook-ai-harness-mcp -t stdio -c uvx -a fca-handbook-harness-mcp
{
"mcpServers": {
"99blaked99-the-metis-fca-handbook-ai-harness-mcp": {
"command": "uvx",
"args": [
"fca-handbook-harness-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 −3
- Stability: pass → 0.77 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- Package version: 0.1.1 → 0.1.3 functional
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
- Package version: 0.1.1 → 0.1.3 functional
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
- 8 Sept 26 +1
- Package version: 0.1.1 → 0.1.3 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/fca-handbook-harness-mcp@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
evaluate_fca_handbook_applicability ~556
Evaluate which FCA Handbook entries apply to an entity, via the Metis FCA Handbook AI Harness. Calls a live compliance reasoning run, billed to the configured account. Use for questions about FCA authorisation, permissions, or obligations for a specific firm/product/service. Reports progress as it runs — show these to the user if your host displays them, they contain genuinely useful detail about what is happening (e.g. which stage of reasoning is underway), not filler. 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's providing it (platform/adviser/bank/etc.), its key features, the target market (retail/institutional/professional), 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 to the account at a flat rate regardless of input quality, so a vague call followed by a refinement round costs twice what one good call would have. The result includes refinement_suggestions — gaps the Harness couldn't 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). If you already have grounded information addressing one (from this conversation, documents you were given, or other tools you've called), fold it into a new user_input and call again yourself, rather than just relaying the suggestion to the user as a question. Do not speculate or infer plausible-sounding detail you do not actually have to fill a gap — that reintroduces the hallucination risk this Harness exists to avoid, one level up. Only ask the user for whatever's left that you genuinely do not know. Args: user_input: Everything together as one piece of text (up to 5000 characters) — the specific compliance question, the product/s…
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_mode | string | – | – |
| user_input | string | yes | – |
No output schema declared.
No examples provided.
What is the io.github.99blakeD99/the-metis-fca-handbook-ai-harness-mcp server?
io.github.99blakeD99/the-metis-fca-handbook-ai-harness-mcp is listed in the public MCP registry as io.github.99blakeD99/the-metis-fca-handbook-ai-harness-mcp. MCP server for FCA Handbook compliance analysis with verbatim citations. This page covers its PyPI package (fca-handbook-harness-mcp).
Is the io.github.99blakeD99/the-metis-fca-handbook-ai-harness-mcp server safe to use?
io.github.99blakeD99/the-metis-fca-handbook-ai-harness-mcp scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.99blakeD99/the-metis-fca-handbook-ai-harness-mcp server expose?
io.github.99blakeD99/the-metis-fca-handbook-ai-harness-mcp exposes 1 tool: evaluate_fca_handbook_applicability. Their descriptions and schemas cost roughly 556 tokens of context every time the server is loaded.
Is the io.github.99blakeD99/the-metis-fca-handbook-ai-harness-mcp server still maintained?
io.github.99blakeD99/the-metis-fca-handbook-ai-harness-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.