Remote MCP · Endpoint

Extcord MCP server

No. Extcord answered an MCP handshake 58 minutes ago.

UpLast checked 58 minutes ago

Server URL

https://extcord.io/mcp

The last check completed an MCP handshake.

Registry name
io.extcord/extcord
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
320 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Agent utilities: read big pages without filling context, exact math, dates, parsing. Free.
Listing
From the official MCP registry (active).
Recent checks of Extcord
CheckedResultHandshake
58 minutes agoHandshake completed320 ms
1 day agoHandshake completed76 ms
4 days agoHandshake completed77 ms
6 days agoHandshake completed143 ms
9 days agoHandshake completed77 ms
11 days agoHandshake completed109 ms
13 days agoHandshake completed77 ms
15 days agoHandshake completed77 ms
17 days agoHandshake completed97 ms
19 days agoHandshake completed70 ms
21 days agoHandshake completed93 ms
22 days agoHandshake completed104 ms
23 days agoHandshake completed98 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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