The repository is unusually careful about what a PASS means: no adverse indicators were found in the sources checked, not a legal verdict — and it tells you to verify the signature and anchor fields each individual response actually returns rather than assuming a uniform set. That posture is the reason to use it: the answers are meant to be handed to an auditor, and an auditor will ask exactly those questions.
A hosted server that turns regulatory questions — is this token MiCA-authorised, is our DORA posture audit-ready — into evidence objects carrying source, timestamp, confidence and a content hash. It reads from live regulatory registers and internal risk models, and the response is meant to be verifiable independently rather than taken on trust.
- MiCA: `mica_status` for authorisation, `significant_issuer` for the issuer threshold, `document_compliance` for recovery and redemption plans, `reserve_quality` for eligible reserves, and `mica_full_pack` for a full evidence pack
- Stablecoin and risk: `peg_deviation`, `interest_check` for prohibited yield mechanisms, `custody_risk` for who holds the reserves, `macro_risk`
- Decision flow: `compliance_preflight` returns PASS, WARN or BLOCK for a jurisdiction, and `audit_log` records the decision and its reasoning against the request ids that informed it
- Audit: `audit_query` retrieves past decisions, `audit_verify` checks the chain is intact, `generate_report` produces a signed PDF
- Explanation: `evidence_bundle` pulls multi-framework evidence, `ai_explain` says why a token has the grade it has, `ai_provenance` says where each data point came from
- `ping` and `tools/list` are open with no signup; `kya_register` issues an API key and a starting balance of free units
Connect with `claude mcp add --transport http feedoracle https://feedoracle.io/mcp/`, or point any client at that URL. Most compliance tools need a free API key — call `kya_register` with your agent name, purpose and owner details and it returns one along with free welcome units; that call creates a real registration, so store the key rather than committing it. Beyond the free allowance, billing is pay-as-you-go through Stripe or the x402 protocol, and the current per-unit price comes back live in each tool's `402 payment_required` response. Public keys for verifying response signatures are at `https://feedoracle.io/.well-known/jwks.json`.
One command plus a key — claude mcp add --transport http feedoracle https://feedoracle.io/mcp/, then supply credentials