Remote MCP · Endpoint

Obento MCP server

Yes, as of 39 minutes ago: the server returned an HTTP error.

DownLast checked 39 minutes ago

Server URL

https://obentoapp.com/mcp

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

Registry name
com.obentoapp/obento
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
6 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Live USDC rates on Base, any address's Obento position, and deposits and withdrawals to sign.
Listing
From the official MCP registry (active).
Recent checks of Obento
CheckedResultHandshake
39 minutes agoFailed - the server returned an HTTP error—
3 days agoHandshake completed1.18 s
13 days agoHandshake completed1.84 s
13 days agoHandshake completed153 ms
15 days agoHandshake completed309 ms
16 days agoHandshake completed112 ms
17 days agoHandshake completed103 ms
18 days agoHandshake completed68 ms
18 days agoHandshake completed93 ms
20 days agoHandshake completed94 ms
22 days agoHandshake completed77 ms
25 days agoHandshake completed125 ms
27 days agoHandshake completed113 ms
29 days agoHandshake completed87 ms

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

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