Remote MCP · Endpoint

Oddi Forge MCP server

Yes, as of 7 hours ago: the server returned an HTTP error.

DownLast checked 7 hours ago

Server URL

https://oddiforge.com/api/mcp

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

Registry name
com.oddiforge/oddiforge
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
58.3% from 12 checks
Described by its publisher as
Read-only facts about Oddi Forge ($ODDI) on Solana: launch status, official contract, FAQ.
Listing
From the official MCP registry (active).
Recent checks of Oddi Forge
CheckedResultHandshake
7 hours agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
14 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
17 days agoHandshake completed312 ms
18 days agoHandshake completed330 ms
19 days agoHandshake completed292 ms
20 days agoHandshake completed285 ms
21 days agoHandshake completed344 ms
23 days agoHandshake completed291 ms
26 days agoHandshake completed289 ms

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

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