Remote MCP · Endpoint

ComputeFirst MCP server

No. ComputeFirst answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://computefirst.net/mcp

The last check completed an MCP handshake.

Registry name
io.github.321zz321/computefirst
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
629 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free deterministic tools for math, data transforms, dates, text, statistics, finance, and units.
Listing
From the official MCP registry (active).
Recent checks of ComputeFirst
CheckedResultHandshake
13 minutes agoHandshake completed629 ms
10 days agoHandshake completed689 ms
10 days agoHandshake completed712 ms
11 days agoHandshake completed547 ms
13 days agoHandshake completed512 ms
14 days agoHandshake completed482 ms
14 days agoHandshake completed451 ms
15 days agoHandshake completed357 ms
17 days agoHandshake completed74 ms
19 days agoHandshake completed55 ms
21 days agoHandshake completed83 ms
24 days agoHandshake completed205 ms
26 days agoHandshake completed684 ms
28 days agoHandshake completed261 ms

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