Remote MCP · Endpoint

INPUT · buscador MCP server

No. INPUT · buscador answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes ago

Server URL

https://input.ink/mcp

The last check completed an MCP handshake.

Registry name
ink.input/buscador
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
466 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 5 checks
Described by its publisher as
Notas, lugares, discos y juegos argentinos de INPUT, magazine cultural de Buenos Aires.
Listing
From the official MCP registry (active).
Recent checks of INPUT · buscador
CheckedResultHandshake
53 minutes agoHandshake completed466 ms
3 days agoHandshake completed207 ms
12 days agoHandshake completed209 ms
13 days agoHandshake completed181 ms
14 days agoHandshake completed598 ms

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

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 INPUT · buscador and makes no claim about it beyond what these checks measured.