Backed: NEAR solvency checks MCP Server

by rohan911438 Your server? Claim it

not responding

Backed: NEAR solvency checks is listed as active in the registry but did not answer our last check. It exposes 3 tools.

Check if a NEAR protocol holds the tokens it owes, read at one block. Read-only.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 14 days of history · worst day 10%

14 days agonow

29.7%

Uptime 24h

27 of 91 checks

Tools

read from the server

495 ms

Response time

average over 24h

open, no key

Access

streamable-http

Backed: NEAR solvency checks does not always answer

Over the last week it answered 26.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add backed --transport http https://backed-near.vercel.app/api/mcp

Settings → Connectors → Add custom connector, then paste this address

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

~/.codex/config.toml

[mcp_servers.backed]
url = "https://backed-near.vercel.app/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "backed": {
      "url": "https://backed-near.vercel.app/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "backed": {
      "type": "http",
      "url": "https://backed-near.vercel.app/api/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

backing

check_backing

Read what a NEAR protocol owes (its own accounting view) and what it holds (each token's ft_balance_of) at the same block, so the answer is exact. Use before depositing into a protocol. Works for intents.near, contract.main.burrow.near (Rhea lending) and any contract implementing backed_solvency.

checker

checker_status

What the on-chain Backed checker contract last recorded for a (protocol, token) pair: Healthy, Suspected or Confirmed breach, with owed, held and block.

intents

intents_backing_summary

The latest daily scan of every NEP-141 token in NEAR Intents (intents.near): how many are backed, which are under-backed and by how much, and why.

Endpoints

URL	Transport	State	Latency	Checked
https://backed-near.vercel.app/api/mcp	streamable-http	answering	68 ms	12 min ago

Alternatives to Backed: NEAR solvency checks

same job, measured the same way

Blocket MCP

by idoo

Read-only MCP server for Blocket.se: search ads, read one in full, check asking prices.

local only

cloudpin

by paureis

Read-only checks that cloud CLI commands run on the accounts a project pins in .cloudpin.yml.

588 installs/wk local only

X402 Bazaar MCP

by sukrutkrdg

Check, then act, on Base and NEAR: token-safety gates, then swaps at the best price — over x402.

136 installs/wk local only

Parallax Protocol

by parallaxprotocol

Read-only Parallax PoW chain data: blocks, transactions, mining, supply, explorer and network health

36 tools answering

The Hockey Analytics

by thehockeyanalytics

Read-only hockey analytics: compare teams and players, trends, fact checks. SHL, Allsvenskan, NHL.

answering

PrufGate

by guardianvigil-labs

Read-only tools that check whether code, and the tests that claim it works, are real.

624 installs/wk local only

Toys Hub

by toyshub

Browse Toys Hub: products, prices in ALL, stock, delivery and checkout links. Read-only, no sign-in.

7 tools answering

Facet

by halfspacelabs

Ask for a model and Facet does the rest: it builds, checks and serves a model for one task.

answering

Backed: NEAR solvency checks — questions

Answers built from our own checks of this server.

What can Backed: NEAR solvency checks do?

It exposes 3 tools, read directly from the server on our last check. Among them: check_backing, checker_status, intents_backing_summary. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Backed: NEAR solvency checks working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 27 of 91 checks got a reply (29.7%), average response time 495 ms. The bar chart above shows every period we have measured.

Is Backed: NEAR solvency checks still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

The registry lists Backed: NEAR solvency checks as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Backed: NEAR solvency checks?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Backed: NEAR solvency checks need an API key?

No. Backed: NEAR solvency checks completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Backed: NEAR solvency checks?

It answers our handshake in 495 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.