Remote MCP · Endpoint

Occam MCP server

No. Occam answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://occam.fit/mcp/

The last check completed an MCP handshake.

Registry name
fit.occam/occam
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
47 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Finds the simplest equation consistent with your data. SINDy and PySR symbolic regression via MCP.
Listing
From the official MCP registry (active).
Recent checks of Occam
CheckedResultHandshake
1 hour agoHandshake completed47 ms
1 day agoHandshake completed92 ms
2 days agoHandshake completed50 ms
3 days agoHandshake completed59 ms
4 days agoHandshake completed43 ms
5 days agoHandshake completed477 ms
6 days agoHandshake completed52 ms
9 days agoHandshake completed49 ms
12 days agoHandshake completed88 ms
14 days agoHandshake completed49 ms
16 days agoHandshake completed47 ms
18 days agoHandshake completed70 ms
20 days agoHandshake completed59 ms
22 days agoHandshake completed44 ms
24 days agoHandshake completed49 ms
26 days agoHandshake completed57 ms
27 days agoHandshake completed65 ms
28 days agoHandshake completed45 ms

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

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