Home / MCP registry index / io.github.PatrickPi1312/eu-compliance

Agent Decision & Evidence Tools (MCP + x402)

io.github.PatrickPi1312/eu-compliance in the official MCP registry. Endpoint https://mcp.eucompliance.tools/mcp. Source: github.com/PatrickPi1312/eucompliance-tools.

The registry describes it as: 40 MCP tools: multi-chain RPC, market and transaction decisions, AI, EU compliance and US imports

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http eu-compliance https://mcp.eucompliance.tools/mcp

{
  "mcpServers": {
    "eu-compliance": {
      "url": "https://mcp.eucompliance.tools/mcp"
    }
  }
}

code --add-mcp '{"name":"eu-compliance","type":"http","url":"https://mcp.eucompliance.tools/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

validate_vat validate_iban recommend_agent_tool prepare_agentllm prepare_agentllm_micro agentllm_micro agentllm_basic agentllm_plus prepare_invoice_to_pay_eu invoice_to_pay_dossier_eu prepare_us_import_readiness us_import_readiness_guard recover_us_import_readiness screen_sanctions_eu eu_vat_rules check_counterparty_eu counterparty_dossier_eu validate_einvoice_eu verify_compliance_receipt must_verify_before_pay lookup_company_eu agent_spend_statement rpc_read_batch wallet_balance gas_estimate contract_info spot_price open_social_search perp_market_data coin_positioning_brief market_decision_pack soft_commodity_stress market_data market_history ai_act_disclosure prepare_x402_purchase_guard x402_purchase_guard tx_preflight tx_status token_status read_url

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-patrickpi1312-eu-compliance/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-patrickpi1312-eu-compliance)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers