All servers · Payments & accounting
Backed: NEAR solvency checks
io.github.rohan911438/backed · v0.1.0
New (7 days)
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Read-only (all tools declare readOnlyHint) |
| Capabilities declared | tools |
| Tool definitions | 3 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Check if a NEAR protocol holds the tokens it owes, read at one block. Read-only.
Connect
streamable-http · https://backed-near.vercel.app/api/mcp
claude mcp add --transport http backed https://backed-near.vercel.app/api/mcp{
"mcpServers": {
"backed": {
"url": "https://backed-near.vercel.app/api/mcp"
}
}
}Tools as reported by the server
check_backingRead 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.intents_backing_summaryThe 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.checker_statusWhat the on-chain Backed checker contract last recorded for a (protocol, token) pair: Healthy, Suspected or Confirmed breach, with owed, held and block.
Repository · Website · JSON · Text for agents · Registry updated 2026-10-25