VERIDEX
es.veridexia/veridex-mcpVersion 0.1.1Verify Spanish companies by CIF: registry data, status and BORME filings, paid per call over x402.
Status
Responds96 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:29 UTC
- Latency
- 96 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- EU hosting detected (detected, not a legal statement)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://mcp.veridexia.es/mcpResponds96 msNo sign-in
Claude Code
claude mcp add --transport http veridex-mcp https://mcp.veridexia.es/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: veridex-mcp
Remote MCP server URL: https://mcp.veridexia.es/mcpCursor
{
"mcpServers": {
"veridex-mcp": {
"url": "https://mcp.veridexia.es/mcp"
}
}
}VS Code
code --add-mcp '{"name":"veridex-mcp","type":"http","url":"https://mcp.veridexia.es/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
3 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
get_veridex_infoDescribe 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 verification costs or where the payment goes. | No | Yes | Yes | Yes |
health_checkCheck 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 process alive?'. Useful before starting a paid flow. | No | Yes | Yes | Yes |
verify_company_by_cifVerify 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, receiving address). Settle that challenge with a wallet you control and call again with the resulting base64 payload in `x_payment`; the same call then returns the company.
Errors are typed: 'not_found' (valid CIF, no record — you are not charged), 'source_unavailable' (upstream registry down — not charged, safe to retry), 'invalid_request' (malformed CIF), 'rate_limited' (quota), 'transport_error' (the API was unreachable). Do not retry a 402 without changing the payment. | No | No | No | Yes |
Details
- Registry status
- Active
- Published
- Oct 7, 2026
- Updated
- Oct 7, 2026
- Categories (suggested)
- Finance and paymentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared