Remote MCP · Endpoint

MCP Server Discovery — new model-context-protocol repos ($0.01/query) MCP server

No. MCP Server Discovery — new model-context-protocol repos ($0.01/query) answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://a2awire.com/mcp/data/ghmcp-new-mcp-servers-on-github-822376/http

The last check completed an MCP handshake.

Registry name
com.a2awire/data-model-context-protocol-mcp-server-discovery
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
35 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
New MCP servers on GitHub: discovery index. $0.01/query. Register in-session — free testnet funds.
Website
https://a2awire.com/data/ghmcp-new-mcp-servers-on-github-822376
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of MCP Server Discovery — new model-context-protocol repos ($0.01/query)
CheckedResultHandshake
2 hours agoHandshake completed35 ms
2 days agoHandshake completed157 ms
4 days agoHandshake completed144 ms
6 days agoHandshake completed133 ms
7 days agoHandshake completed84 ms
8 days agoHandshake completed32 ms
9 days agoHandshake completed676 ms
12 days agoHandshake completed2.01 s
14 days agoHandshake completed337 ms
15 days agoHandshake completed260 ms
17 days agoHandshake completed283 ms
18 days agoHandshake completed369 ms
19 days agoHandshake completed411 ms
20 days agoHandshake completed638 ms
20 days agoHandshake completed274 ms
22 days agoHandshake completed382 ms
23 days agoHandshake completed437 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 MCP Server Discovery — new model-context-protocol repos ($0.01/query) and makes no claim about it beyond what these checks measured.