Remote MCP · Endpoint

BenchGecko MCP server

No. BenchGecko answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://benchgecko.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.benchgecko/benchgecko
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
90 ms
Tools exposed
9 tools
Uptime, last 30 days
76.9% from 13 checks
Described by its publisher as
AI model prices per provider, benchmarks, own AI behavior tests and AI economy data, with sources.
Listing
From the official MCP registry (active).
Recent checks of BenchGecko
CheckedResultHandshake
1 hour agoHandshake completed90 ms
2 days agoHandshake completed520 ms
5 days agoHandshake completed102 ms
7 days agoHandshake completed59 ms
9 days agoHandshake completed153 ms
11 days agoHandshake completed112 ms
13 days agoFailed - the server returned an HTTP error—
15 days agoHandshake completed44 ms
17 days agoHandshake completed96 ms
19 days agoHandshake completed47 ms
20 days agoFailed - the server returned an HTTP error—
21 days agoFailed - the server returned an HTTP error—
22 days agoHandshake completed100 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 10 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.

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