Remote MCP · Endpoint

contix herramientas MCP server

No. contix herramientas answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.contix.es/api/v1/mcp/herramientas

The last check completed an MCP handshake.

Registry name
es.contix/herramientas
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
300 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free no-auth tools for Spain: validate IBAN, EU VAT check (VIES), Modelo 303 sums, Veri*factu dates.
Listing
From the official MCP registry (active).
Recent checks of contix herramientas
CheckedResultHandshake
2 hours agoHandshake completed300 ms
2 days agoHandshake completed300 ms
4 days agoHandshake completed296 ms
7 days agoHandshake completed310 ms
9 days agoHandshake completed293 ms
11 days agoHandshake completed295 ms
13 days agoHandshake completed293 ms
15 days agoHandshake completed393 ms
16 days agoHandshake completed299 ms
18 days agoHandshake completed375 ms
19 days agoHandshake completed295 ms
20 days agoHandshake completed302 ms
23 days agoHandshake completed298 ms
24 days agoHandshake completed304 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 contix herramientas and makes no claim about it beyond what these checks measured.