Remote MCP · Endpoint

sh.agentcard/agentcard MCP server

No. sh.agentcard/agentcard answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.agentcard.sh/mcp

The last check completed an MCP handshake.

Registry name
sh.agentcard/agentcard
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
316 ms
Tools exposed
55 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Prepaid virtual cards for AI agents: one-time cards, spend caps, human approvals.
Website
https://agentcard.sh/
Listing
From the official MCP registry (active).
Recent checks of sh.agentcard/agentcard
CheckedResultHandshake
1 hour agoHandshake completed316 ms
2 days agoHandshake completed909 ms
4 days agoHandshake completed197 ms
5 days agoHandshake completed543 ms
7 days agoHandshake completed316 ms
8 days agoHandshake completed387 ms
9 days agoHandshake completed349 ms
12 days agoHandshake completed513 ms
13 days agoHandshake completed721 ms
15 days agoHandshake completed303 ms
16 days agoHandshake completed259 ms
18 days agoHandshake completed310 ms
19 days agoHandshake completed372 ms
20 days agoHandshake completed352 ms
21 days agoHandshake completed210 ms
21 days agoHandshake completed435 ms
23 days agoHandshake completed188 ms

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

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 sh.agentcard/agentcard and makes no claim about it beyond what these checks measured.