Remote MCP · Endpoint

Backed: NEAR solvency checks MCP server

No. Backed: NEAR solvency checks answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://backed-near.vercel.app/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.rohan911438/backed
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
82 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Check if a NEAR protocol holds the tokens it owes, read at one block. Read-only.
Listing
From the official MCP registry (active).
Recent checks of Backed: NEAR solvency checks
CheckedResultHandshake
7 hours agoHandshake completed82 ms
4 days agoHandshake completed80 ms
14 days agoHandshake completed514 ms
15 days agoHandshake completed633 ms
15 days agoHandshake completed84 ms
17 days agoHandshake completed600 ms
18 days agoHandshake completed90 ms
19 days agoHandshake completed500 ms
20 days agoHandshake completed59 ms
21 days agoHandshake completed63 ms
23 days agoHandshake completed495 ms
26 days agoHandshake completed473 ms

The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 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 Backed: NEAR solvency checks and makes no claim about it beyond what these checks measured.