Remote MCP · Endpoint

io.github.archimedes-market/mcp-archimedes MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://archimedes.market/api/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.archimedes-market/mcp-archimedes
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
Discover verified deep-tech engineering bounties from any AI agent.
Listing
From the official MCP registry (active).
Recent checks of io.github.archimedes-market/mcp-archimedes
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
1 day agoHandshake completed120 ms
2 days agoHandshake completed83 ms
3 days agoHandshake completed102 ms
4 days agoHandshake completed398 ms
5 days agoHandshake completed94 ms
6 days agoHandshake completed215 ms
9 days agoHandshake completed114 ms
11 days agoHandshake completed66 ms
14 days agoHandshake completed80 ms
16 days agoHandshake completed152 ms
18 days agoHandshake completed137 ms
20 days agoHandshake completed120 ms
22 days agoHandshake completed110 ms
24 days agoHandshake completed174 ms
26 days agoHandshake completed104 ms
27 days agoHandshake completed144 ms
28 days agoHandshake completed133 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 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 io.github.archimedes-market/mcp-archimedes and makes no claim about it beyond what these checks measured.