Feedoracle MCP Server

FeedOracle Compliance Evidence Infrastructure — MCP server for MiCA, DORA, and AMLR compliance evidence, signed and verifiable

Local serverstdioPython

What is the Feedoracle MCP MCP server?

Connect Feedoracle MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. FeedOracle Compliance Evidence Infrastructure — MCP server for MiCA, DORA, and AMLR compliance evidence, signed and verifiable. The feedoracle mcp mcp server is what makes that connection.

What the server does

FeedOracle is compliance-evidence infrastructure for regulated entities and their AI agents. It turns questions like "Is USDT compliant for trading in the EU under MiCA?" into signed, sourced, auditable answers instead of an LLM guess.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Live — MCP server, MiCA/DORA/AMLR tool set, x402 micropayments, signed evidence objects, KYA self-registration
  • Beta — mesh-wide routing improvements across OracleNet
  • Planned — broader regulatory framework coverage (CSRD, NIS2) — tracked in CHANGELOG.md
  • Server — Tools
  • AmpelOracle — 50
  • MiCAOracle — 24
  • ReserveOracle — 11
  • RiskOracle — 7
  • PredictionGuard — 28

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Where it fits

Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Feedoracle MCP's toolset — Live, Beta, Planned and 6 more — is a fair guide to whether it matches your workflow. It is maintained by feedoracle; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Feedoracle MCP.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
LiveMCP server, MiCA/DORA/AMLR tool set, x402 micropayments, signed evidence objects, KYA self-registration
Betamesh-wide routing improvements across OracleNet
Plannedbroader regulatory framework coverage (CSRD, NIS2) — tracked in [CHANGELOG.md](CHANGELOG.md)
ServerTools
AmpelOracle50
MiCAOracle24
ReserveOracle11
RiskOracle7
PredictionGuard28

How to install the Feedoracle MCP MCP server

```json
{
  "mcpServers": {
    "feedoracle": {
      "url": "https://feedoracle.io/mcp/"
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Feedoracle MCP to Live.
  • Use Feedoracle MCP to Beta.
  • Use Feedoracle MCP to Planned.

Frequently asked questions

It connects Feedoracle MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (Live, Beta, Planned, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Feedoracle MCP directly.