Remote MCP · Endpoint

ScoreCompute MCP server

No. ScoreCompute answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://scorecompute.com/mcp

The last check completed an MCP handshake.

Registry name
com.scorecompute/scorecompute
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
327 ms
Tools exposed
38 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
38 MCP tools: Rust computation, Discovery, composition, counterexample scans and signed checks.
Listing
From the official MCP registry (active).
Recent checks of ScoreCompute
CheckedResultHandshake
1 hour agoHandshake completed327 ms
2 days agoHandshake completed366 ms
4 days agoHandshake completed595 ms
6 days agoHandshake completed403 ms
8 days agoHandshake completed405 ms
10 days agoHandshake completed433 ms
13 days agoHandshake completed408 ms
14 days agoHandshake completed401 ms
16 days agoHandshake completed432 ms
17 days agoHandshake completed353 ms
18 days agoHandshake completed387 ms
21 days agoHandshake completed375 ms
22 days agoHandshake completed454 ms
24 days agoHandshake completed447 ms

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

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