Remote MCP · Endpoint

modelright MCP server

No. modelright answered an MCP handshake 55 minutes ago.

UpLast checked 55 minutes ago

Server URL

https://modelright.dev/api/mcp

The last check completed an MCP handshake.

Registry name
dev.modelright/modelright
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
93 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Live registry of AI model specs, context windows, and per-token pricing.
Listing
From the official MCP registry (active).
Recent checks of modelright
CheckedResultHandshake
55 minutes agoHandshake completed93 ms
1 day agoHandshake completed105 ms
4 days agoHandshake completed104 ms
6 days agoHandshake completed130 ms
9 days agoHandshake completed123 ms
11 days agoHandshake completed112 ms
13 days agoHandshake completed101 ms
15 days agoHandshake completed96 ms
17 days agoHandshake completed103 ms
19 days agoHandshake completed95 ms
21 days agoHandshake completed100 ms
22 days agoHandshake completed121 ms
23 days agoHandshake completed101 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.

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