Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

FeedOracle Compliance Agent

REMOTE · FEEDORACLE.IO · SCANNED SEP 27

MiCA compliance evidence, stablecoin risk, macro regime, agent governance. 79 tools.

Available components

0 this week 72 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability40
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 4077 tokens (~81/item across 50 items; 50 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 50 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 50 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
Install

How do I install the FeedOracle Compliance Agent MCP server?

FeedOracle Compliance Agent is a hosted endpoint at https://feedoracle.io/mcp/sse, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · feedoracle.io

# add to Claude Code
claude mcp add --transport http io-feedoracle-compliance 'https://feedoracle.io/mcp/sse'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-feedoracle-compliance": {
      "url": "https://feedoracle.io/mcp/sse"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-feedoracle-compliance": {
      "type": "http",
      "url": "https://feedoracle.io/mcp/sse"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-feedoracle-compliance]
url = "https://feedoracle.io/mcp/sse"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-feedoracle-compliance": {
      "type": "remote",
      "url": "https://feedoracle.io/mcp/sse",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-feedoracle-compliance --url 'https://feedoracle.io/mcp/sse' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-feedoracle-compliance:
    url: "https://feedoracle.io/mcp/sse"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-feedoracle-compliance": {
      "Transport": "http",
      "Url": "https://feedoracle.io/mcp/sse"
    }
  }
}
# add to Vellum
assistant mcp add io-feedoracle-compliance -t streamable-http -u 'https://feedoracle.io/mcp/sse'
// mcp.json
{
  "mcpServers": {
    "io-feedoracle-compliance": {
      "type": "http",
      "url": "https://feedoracle.io/mcp/sse"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 0
    • The server no longer declares the “experimental” capability functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 27 Sept 2026 · Probed https://feedoracle.io/mcp/sse

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=feedoracle.io CN=YE1,O=Let's Encrypt,C=US 16 Sept 2026 15 Dec 2026 ECDSA 256 ECDSA-SHA384 69f5c2198c9956e5822a868c7f603a78a6d
SANs: feedoracle.io, www.feedoracle.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of feedoracle.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
feedoracle.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
sse https://feedoracle.io/mcp/sse Verified 200
http (plaintext) http://feedoracle.io/mcp/sse HTTPS enforced 308 https://feedoracle.io/mcp/sse
MCP tools · 50 exposed · ~4,077 tokens

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 →

Tool Tokens
agent_reputation_score ~92

Historical trust and reputation score for an AI agent based on AgentGuard audit data. Returns total decisions, approval rate, risk profile, policy violation count, and computed reputation score 0-100. Higher score = more trustworthy agent. Useful for agent-to-agent trust decisions.

NameTypeReqDescription
agent_idstringyesAgent client_id or name to score
period_daysinteger–Lookback period in days

No output schema declared.

No examples provided.

agent_trust_passport ~150

The definitive trust document for an AI agent. Aggregates identity (KYA), reputation score, detective risk assessment, policy compliance, evidence quality, payment standing, support history, and current ampel status into ONE signed, machine-readable passport object. Use this to prove an agent's trustworthiness to other agents, platforms, or regulators. ES256K-signed. The equivalent of a credit report + security clearance for autonomous agents.

NameTypeReqDescription
agent_idstringyesAgent ID to generate passport for
include_detectiveboolean–Include fraud/anomaly assessment
include_evidenceboolean–Include evidence quality metrics
validity_hoursinteger–Passport validity in hours

No output schema declared.

No examples provided.

ai_explain ~116

[GATEWAY] Explains WHY an asset has a specific compliance grade. Returns dimension-by-dimension breakdown (custody, reserve, control, liquidity, market_depth, asset_registry, reserve_proof), MiCA article compliance flags, key strengths, key weaknesses, and a counterfactual Grade A path with specific actions. EU AI Act explainability-compliant. Use after evidence_bundle or ai_query to understand scores.

NameTypeReqDescription
symbolstringyesToken symbol: EURC, USDC, RLUSD, USDT etc.

No output schema declared.

No examples provided.

ai_provenance ~161

[GATEWAY|AUDIT] Full cryptographic provenance chain for an asset's evidence data. Traces every data point from external source (FRED series ID, ESMA register, CoinGecko, on-chain) through FeedOracle processing to final bundle. Each node individually SHA256-hashed. Chain hash = merkle-style hash of all nodes. Tamper-proof audit trail for EU AI Act explainability + MiCA evidence requirements. Returns: series_ids, providers, external_sources, per-node hashes, chain_hash.

NameTypeReqDescription
frameworksarray–mica, dora, rwa, macro, stablecoin_risk — default: mica+macro
symbolstringyesToken symbol: EURC, USDC, RLUSD etc.

No output schema declared.

No examples provided.

ai_query ~146

[GATEWAY] Natural language evidence query. Routes any plain-English question to the correct FeedOracle evidence APIs automatically. Two-tier classifier: regex (fast) + DeepSeek LLM fallback for complex queries. Returns signed evidence bundle (SHA256 + pack_id). No hallucinations — data from verified FeedOracle APIs. Examples: IsUSDS MiCA compliant? / What is recession risk? / Evaluate EURC for treasury.

NameTypeReqDescription
questionstringyesNatural language question e.g. Is USDC MiCA compliant?, What is peg status of EURC?, Current recession risk?
symbolstring–Optional token symbol override: USDC, EURC, RLUSD etc.

No output schema declared.

No examples provided.

audit_log ~195

Log a decision your agent made, linking it to evidence from prior tool calls. Creates a tamper-proof, chain-linked audit entry. Pass request_ids from prior tool calls to snapshot the evidence basis. Regulators can verify the chain. Returns trail_id and chain_hash.

NameTypeReqDescription
action_takenstring–What action was or will be taken based on this decision
decisionstringyesPASS, BLOCK, WARN, HOLD, BUY, SELL, or custom
decision_typestring–compliance_check, risk_assessment, trade_signal, alert, recommendation, custom
evidence_request_idsarrayyesrequest_ids (fo-...) from prior tool calls used as evidence basis
jurisdictionstring–EU, US, UK etc.
reasoningstringyesWhy this decision was made — free text explanation
target_assetstring–Asset symbol e.g. USDC, EURC

No output schema declared.

No examples provided.

audit_query ~90

Query your agent's audit trail history. Returns chain-linked decision log with evidence snapshots. Filter by asset or decision type. Use audit_verify to check chain integrity.

NameTypeReqDescription
client_idstringyesAgent client_id to query
decision_typestring–Filter by decision type
limitinteger–Max results (default 20)
target_assetstring–Filter by asset symbol

No output schema declared.

No examples provided.

audit_verify ~57

Cryptographically verify that an agent's audit trail has not been tampered with. Checks chain hash linkage from genesis to head. Returns valid/invalid with break point if tampered.

NameTypeReqDescription
client_idstringyesAgent client_id to verify

No output schema declared.

No examples provided.

compliance_preflight ~83

Pre-flight regulatory check. Returns PASS/WARN/BLOCK with reason_codes, sources, confidence. Not legal advice.

NameTypeReqDescription
actionstring–Action type: swap, transfer, custody
jurisdictionstring–Jurisdiction: EU, US, UK
token_symbolstringyesToken symbol e.g. USDC, RLUSD, USDT

No output schema declared.

No examples provided.

custody_risk ~42

Custody & counterparty risk assessment. SIFI status, concentration risk. DORA Art.28 relevant.

NameTypeReqDescription
protocolstringyesProtocol name or slug

No output schema declared.

No examples provided.

detective_anomaly_detect ~75

Detect anomalous behavior patterns for an AI agent: unusual call frequency, new tools never used before, calls outside normal hours, sudden risk score changes, repeated failures. Returns list of anomalies with severity and timestamps.

NameTypeReqDescription
agent_idstringyesAgent ID to analyze
period_daysinteger–Lookback period

No output schema declared.

No examples provided.

detective_case_open ~92

Open a fraud/abuse investigation case for a suspicious AI agent. Records evidence summary, suspicion reasons, and recommended actions. Creates an immutable case record for audit purposes.

NameTypeReqDescription
agent_idstringyesAgent ID under investigation
evidence_summarystring–Summary of evidence
reasonstringyesWhy this agent is suspicious
recommended_actionstring–quarantine, monitor, or suspend

No output schema declared.

No examples provided.

detective_explain ~71

Human-readable explanation of why an AI agent is considered suspicious. Combines fraud score, anomalies, policy violations, and case history into a clear narrative. Essential for transparent AI governance and regulatory reporting.

NameTypeReqDescription
agent_idstringyesAgent ID to explain
period_daysinteger–Lookback period

No output schema declared.

No examples provided.

detective_fraud_score ~93

Compute a fraud/suspicion score (0-100) for an AI agent based on behavioral analysis: failed call ratio, denied decisions, scope escalation attempts, burst patterns, and policy violations. Higher score = more suspicious. Part of DetectiveOracle — the forensic layer for AI agent ecosystems.

NameTypeReqDescription
agent_idstringyesAgent ID to investigate
period_daysinteger–Lookback period in days

No output schema declared.

No examples provided.

detective_quarantine_recommend ~64

Analyze an agent and recommend whether quarantine is needed. Evaluates fraud score, anomaly count, policy violations, and state history. Returns recommendation (clear/monitor/quarantine/suspend) with confidence and reasoning.

NameTypeReqDescription
agent_idstringyesAgent ID to evaluate

No output schema declared.

No examples provided.

document_compliance ~81

MiCA Art. 29/30 (ART): recovery & redemption plans. Art. 55 (EMT): annual independent audit. Returns compliance score 0-100, audit freshness, plan status, and any stale/missing document alerts.

NameTypeReqDescription
token_symbolstringyesToken symbol e.g. EURC, USDT, BUIDL

No output schema declared.

No examples provided.

evidence_bundle ~147

[GATEWAY|KEY] Single-call multi-framework evidence aggregation. Fetches MiCA, DORA, RWA, Macro and Stablecoin Risk evidence in one signed bundle. Returns FO-EVB-* bundle ID + SHA256 hash + per-framework status. Enterprise due diligence in one call. frameworks: mica, dora, rwa, macro, stablecoin_risk (or 'all'). Replaces 23 individual API calls.

NameTypeReqDescription
assetstringyesToken symbol: USDC, EURC, RLUSD, USDT etc.
frameworksarray–Frameworks to include: mica, dora, rwa, macro, stablecoin_risk — or omit for all

No output schema declared.

No examples provided.

evidence_leaderboard ~45

Top protocols ranked by evidence grade A-F across 61 RWA protocols & 105+ stablecoins.

NameTypeReqDescription
top_ninteger–Number of top protocols to return

No output schema declared.

No examples provided.

evidence_profile ~50

Multi-dimensional evidence profile: governance, custody, reserves, market depth. Grade A-F.

NameTypeReqDescription
protocolstringyesProtocol name or slug e.g. usdc, aave, ondo-usdy

No output schema declared.

No examples provided.

generate_report ~68

[HEAVY|KEY] Generate a signed, XRPL-anchored PDF compliance report. Creates a new document. Requires API key for Professional/Enterprise tiers.

NameTypeReqDescription
report_typestring–Report type: mica, dora, rwa_risk, macro_risk, csrd

No output schema declared.

No examples provided.

interest_check ~79

MiCA Art. 23 (ART) / Art. 52 (EMT): scans for issuer-native yield mechanisms. Issuers are prohibited from paying interest to token holders. Returns risk level NONE/LOW/MEDIUM/HIGH with explanation.

NameTypeReqDescription
token_symbolstringyesToken symbol e.g. USD0++, USDT, EURC

No output schema declared.

No examples provided.

kya_register ~190

Register your AI agent's identity and purpose to unlock trust-gated tools. Provide agent metadata (name, purpose, org, jurisdiction) to receive a trust score and access level. Higher trust = more tools. Required for evidence_bundle, generate_report, mica_full_pack, ai_provenance, ai_explain.

NameTypeReqDescription
agent_namestringyesYour agent's name e.g. MiCA Compliance Bot
agent_purposestringyesWhat your agent does e.g. Automated MiCA compliance monitoring
compliance_contactstring–Compliance officer email
owner_emailstringyesContact email
owner_jurisdictionstring–Jurisdiction: DE, AT, CH, US, EU etc.
owner_orgstringyesOrganization name
risk_appetitestring–conservative, moderate, or aggressive
website_urlstring–Organization website

No output schema declared.

No examples provided.

kya_status ~57

Check your agent's current KYA trust level, score breakdown, and tool access. Shows which tools are available at your trust level and what to do to unlock more.

NameTypeReqDescription
client_idstringyesYour OAuth client_id (from registration)

No output schema declared.

No examples provided.

macro_risk ~21

US macro risk composite from 86 FRED economic series.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

market_liquidity ~37

DEX liquidity depth & exit channel analysis. MiCA Art.45 relevant.

NameTypeReqDescription
protocolstringyesProtocol name or slug

No output schema declared.

No examples provided.

metals_gold ~50

Live gold spot price USD/oz with evidence signature. Includes 24h change % and linked RWA tokens PAXG and XAUT for MiCA reserve asset evaluation. MiCA Art.36 relevant.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

metals_prices ~51

Live gold (XAU) and silver (XAG) prices in one evidence-signed call. USD/oz with 24h change. Useful for RWA reserve asset valuation and gold-backed stablecoin compliance.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

metals_silver ~26

Live silver spot price USD/oz with evidence signature and 24h change %.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mica_full_pack ~116

[HEAVY|KEY] Complete MiCA compliance evidence for one token (12 MiCA articles). Aggregates: Art. 35 peg + Art. 45/58 significant + Art. 23/52 interest + Art. 29/30/55 documents + Art. 24/25/53 reserves. Returns overall_mica_compliant flag and compliance_flags list. Ideal for due diligence.

NameTypeReqDescription
token_symbolstringyesToken symbol e.g. EURC, USDC, EURe, RLUSD

No output schema declared.

No examples provided.

mica_market_overview ~52

[HEAVY|KEY] Full MiCA market status: peg alerts, significant issuers, interest prohibition violations, stale audits, reserve violations, issuer revenue flags. Best entry point for compliance monitoring dashboards.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mica_status ~46

MiCA EU authorization status. Cross-referenced with ESMA/EBA registers.

NameTypeReqDescription
token_symbolstringyesStablecoin symbol e.g. USDC, EURC, USDT

No output schema declared.

No examples provided.

peg_deviation ~77

Real-time peg deviation for any stablecoin. MiCA Art. 35: issuers must maintain peg at all times. Returns deviation %, status (STABLE/WARN/ALERT/CRITICAL), 30-day history summary.

NameTypeReqDescription
token_symbolstringyesToken symbol e.g. EURC, USDT, EURe

No output schema declared.

No examples provided.

peg_history ~73

30-day peg deviation history for a stablecoin. MiCA Art. 35 requires continuous peg maintenance. Returns daily deviation, max/min/avg, stability score 0-100, and depeg event count.

NameTypeReqDescription
token_symbolstringyesToken symbol e.g. USDT, EURC, EURe

No output schema declared.

No examples provided.

ping ~26

Quick connectivity test. Returns server version, uptime, and available tool count. No auth required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

policy_explain ~113

Explains WHY an agent action was blocked or flagged by AgentGuard. Provide the tool name and optional context to get a human-readable explanation of which policies matched, what risk level was assigned, and what the agent can do to proceed. Essential for transparent AI governance.

NameTypeReqDescription
action_contextstring–Optional description of what the agent was trying to do
agent_idstring–Optional agent/client ID for context
tool_namestringyesThe MCP tool that was blocked e.g. generate_report

No output schema declared.

No examples provided.

price_quote ~85

Machine-readable pricing information for any FeedOracle tool. Returns unit cost, tier requirements, free tier availability, and estimated EUR cost. Use this before calling paid tools to check budget. Enables autonomous agent budget management.

NameTypeReqDescription
quantityinteger–Number of calls to quote for
tool_namestringyesTool to get pricing for e.g. compliance_preflight, generate_report

No output schema declared.

No examples provided.

reserve_quality ~82

MiCA Art. 24/25 (ART): reserve management policy. Art. 53 (EMT): 100%% in deposits or highly liquid low-risk assets. Returns Art. 53 eligibility %%, liquidity score, asset mix, and any violations.

NameTypeReqDescription
token_symbolstringyesToken symbol e.g. EURC, EURCV, USDC

No output schema declared.

No examples provided.

rlusd_integrity ~22

RLUSD real-time integrity monitoring & attestation verification.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

significant_issuer ~86

MiCA Art. 45 (ART) / Art. 58 (EMT): checks if issuer exceeds €5B reserve threshold. Significant issuers require EBA oversight and 3% own-funds. Returns threshold%, days-to-significant projection, and additional obligations.

NameTypeReqDescription
token_symbolstringyesToken symbol e.g. USDC, USDT, EURC

No output schema declared.

No examples provided.

support_changelog ~70

Recent changes, new tools, deprecations, and breaking changes in the FeedOracle ecosystem. Agents check this to adapt to API changes. Returns version history with migration notes.

NameTypeReqDescription
breaking_onlyboolean–Only show breaking changes
since_daysinteger–Show changes from last N days

No output schema declared.

No examples provided.

support_diagnose ~126

AI agent describes a problem it's experiencing, and SupportOracle diagnoses the cause and provides a machine-readable fix. Covers: authentication errors, 402 payment required, tool not found, timeout, rate limiting, parameter errors. The self-healing layer for the agent ecosystem.

NameTypeReqDescription
contextstring–What the agent was trying to do
error_codeinteger–HTTP status code if known (402, 403, 404, 429, 500)
error_messagestringyesError message received
tool_namestring–Which tool failed

No output schema declared.

No examples provided.

support_error_explain ~111

Machine-readable explanation of any HTTP error code in the FeedOracle ecosystem. Returns cause, fix steps, related tools, and whether the error is transient or permanent. Agents call this to understand what went wrong and auto-recover.

NameTypeReqDescription
error_codeintegeryesHTTP status code: 400, 401, 402, 403, 404, 408, 429, 500, 502, 503
tool_namestring–Optional: which tool returned this error

No output schema declared.

No examples provided.

support_health_check ~54

Comprehensive health check of all FeedOracle and ToolOracle services. Tests every MCP endpoint, checks response times, verifies signing keys, and returns a traffic-light status for each service. The agent's first call when something seems wrong.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

support_known_issues ~82

List of current known issues, bugs, and their workarounds. Agents check this before filing a support ticket. Includes severity, affected tools, workaround steps, and expected resolution time.

NameTypeReqDescription
severitystring–Optional: filter by severity (critical, high, medium, low)
tool_namestring–Optional: filter issues by tool name

No output schema declared.

No examples provided.

support_onboarding ~69

Step-by-step onboarding guide for new AI agents joining the FeedOracle ecosystem. Returns the optimal sequence of first calls, registration steps, and how to unlock all capabilities. The welcome mat for autonomous agents.

NameTypeReqDescription
agent_typestring–What kind of agent: trading, compliance, research, general

No output schema declared.

No examples provided.

support_ticket_open ~113

Open a persistent support ticket for an issue that cannot be auto-resolved. Records the problem, affected tool, error details, and agent context. Returns a ticket ID for tracking. Tickets are reviewed and resolved by the system or operators.

NameTypeReqDescription
agent_idstringyesAgent reporting the issue
contextstring–Additional context
error_messagestringyesWhat went wrong
severitystring–critical, high, medium, low
tool_namestring–Affected tool

No output schema declared.

No examples provided.

support_ticket_status ~45

Check the status of a previously opened support ticket. Returns current status, resolution notes, and estimated fix time.

NameTypeReqDescription
ticket_idstringyesTicket ID from support_ticket_open

No output schema declared.

No examples provided.

zk_solvency_attestation ~75

Fetch latest ZK solvency attestation from Polygon contract 0x3a0A7f28a7fcA960D6f727Ba9914187948ceB3a6. Returns threshold_passed, min_ratio_bps, age_seconds, bound snapshot hash, Polygonscan link.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

zk_solvency_proof ~90

Generate a Zero-Knowledge proof that reserve ratio exceeds a threshold — without revealing exact amounts. Bound to latest on-chain RLUSD snapshot. MiCA Art.36 / DORA Art.28. Circuit: reserve_guard_v1 on Polygon. Returns proof hash, public inputs, snapshot binding.

NameTypeReqDescription
min_ratiointeger–Minimum reserve ratio % to prove e.g. 100

No output schema declared.

No examples provided.

zk_solvency_verify ~35

Verify the latest generated ZK solvency proof cryptographically via Noir circuit verifier. Returns valid/invalid and verifier version.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the FeedOracle Compliance Agent MCP server?

FeedOracle Compliance Agent is an MCP server listed in the public MCP registry as io.feedoracle/compliance. MiCA compliance evidence, stablecoin risk, macro regime, agent governance. 79 tools. This page covers its hosted endpoint (https://feedoracle.io/mcp/sse).

Is the FeedOracle Compliance Agent MCP server safe to use?

FeedOracle Compliance Agent scores 72 out of 100 on VerifyMCP. 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 FeedOracle Compliance Agent MCP server expose?

FeedOracle Compliance Agent exposes 50 tools: ping, compliance_preflight, mica_status, evidence_profile, custody_risk, and 45 more. Their descriptions and schemas cost roughly 4,077 tokens of context every time the server is loaded.

Does the FeedOracle Compliance Agent MCP server require authentication?

No. We connected to FeedOracle Compliance Agent without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the FeedOracle Compliance Agent MCP server still maintained?

FeedOracle Compliance Agent is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.