es.veridexia/veridex-mcp · v0.1.1 · crypto-web3
VERIDEX is healthy: it completed an MCP handshake in 1425 ms and exposes 3 tools.
Verify Spanish companies by CIF: registry data, status and BORME filings, paid per call over x402.
Endpoint: https://mcp.veridexia.es/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 3 |
| Latency | 1425 ms |
| Last checked (UTC) | 2026-10-16T02:40:13.779Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-16T02:40:13.779Z | Healthy | 1425 | |
| 2026-10-14T23:50:36.984Z | Healthy | 3132 |
verify_company_by_cif | Verify a Spanish company by its CIF and get its registry data, status in the BORME, recent published acts and an explainable 0-100 risk score. This is an x402-paid endpoint. The first call returns ok=false with error.code='payment_required' and a complete `payment` challenge (price, network, asset, |
get_veridex_info | Describe the VERIDEX service: what it does, its price, the settlement network and asset, the receiving address and the available endpoints. Reads the public discovery manifest at /.well-known/x402. Needs no credentials and costs nothing. Call this before verifying if you need to know what a verific |
health_check | Check whether the VERIDEX API is up, and see today's demand: uptime, the number of verification calls served today and the distinct callers. Free and unauthenticated. The request count excludes the service's own healthchecks and local tests, so it answers 'is anyone using this?' rather than 'is the |