Remote MCP · Endpoint

VERIDEX MCP server

No. VERIDEX answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.veridexia.es/mcp

The last check completed an MCP handshake.

Registry name
es.veridexia/veridex-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
343 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Verify Spanish companies by CIF: registry data, status and BORME filings, paid per call over x402.
Listing
From the official MCP registry (active).
Recent checks of VERIDEX
CheckedResultHandshake
1 hour agoHandshake completed343 ms
23 hours agoHandshake completed395 ms
2 days agoHandshake completed318 ms
4 days agoHandshake completed310 ms
6 days agoHandshake completed327 ms
9 days agoHandshake completed381 ms
11 days agoHandshake completed318 ms
13 days agoHandshake completed382 ms
15 days agoHandshake completed341 ms
17 days agoHandshake completed329 ms
19 days agoHandshake completed328 ms
21 days agoHandshake completed343 ms
23 days agoHandshake completed361 ms
24 days agoHandshake completed322 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with VERIDEX and makes no claim about it beyond what these checks measured.