Remote MCP · Endpoint

ModelSpec MCP server

No. ModelSpec answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://api.modelspec.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.turbobeest/modelspec
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
218 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Find AI models that fit a job from your requirements, sourced benchmarks and real cost.
Listing
From the official MCP registry (active).
Recent checks of ModelSpec
CheckedResultHandshake
1 day agoHandshake completed218 ms
1 day agoHandshake completed437 ms
2 days agoHandshake completed439 ms
4 days agoHandshake completed201 ms
5 days agoHandshake completed171 ms
6 days agoHandshake completed234 ms
7 days agoHandshake completed220 ms
8 days agoHandshake completed261 ms
9 days agoHandshake completed392 ms
12 days agoHandshake completed275 ms
15 days agoHandshake completed584 ms
17 days agoHandshake completed395 ms
19 days agoHandshake completed229 ms
21 days agoHandshake completed156 ms
23 days agoHandshake completed236 ms

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

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