eucompliance-tools
https://server.smithery.ai/office-sxl6/eucompliance-tools/mcp2. Description (Markdown erlaubt, zum Kopieren): Compliance and pre-transaction checks for agents, priced per call. No account, no API key. **On-chain pre-flight** — will this transaction go through? Gas vs. balance, full simulation with the **revert reason decoded into plain text**, stuck nonces, contract-or-wallet recipient, ERC-20 allowance, plus a sanctions screen of the counterparty. One call, `send` / `do not send` with every blocking reason. Also allowance and balance on Base, Ethereum, Arbitrum, Optimism and Polygon, and transaction status with the revert reason recovered by replaying the call against its block. **EU compliance** — sanctions screening against the official EU, UN and UK lists (re-indexed daily), VAT ID validation against the live VIES register, IBAN checks, counterparty due diligence with GLEIF LEI, EU VAT treatment with EN 16931 codes (BT-151 category, BT-121 exemption reason), and e-invoice validation for XRechnung, ZUGFeRD, Factur-X and Peppol BIS. `validate_vat` and `validate_iban` are **free**. The rest settle per call over [x402](https://x402.org) in USDC on Base, from $0.002 — an agent with a wallet pays automatically, one without still connects and uses the free tools. Every answer carries an EIP-191 signed receipt that verifies offline with no network and no trust in us: `pip install eucompliance-verify`.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (3596 ms); slow response -1. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 41 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 0/5 | not seen in a source for over 30 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 55% of peers
- This listing 82 · peer median 81
- Latency
- Faster than 5% of peers
- This listing 1,313 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Freshness + modern flags −5
— Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/office-sxl6/eucompliance-tools/mcp
curl -X POST https://server.smithery.ai/office-sxl6/eucompliance-tools/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'