Backed: NEAR solvency checks

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

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
73%
Naming quality
93%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~438Tokens (tool definitions)
~821 BTypical response size
Minimal attention impact (0.34% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://backed-near.vercel.app/api/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢check_backing(target, tokens, adapter)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "target": {
      "type": "string",
      "description": "Protocol account, e.g. intents.near"
    },
    "tokens": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "maxItems": 10,
      "description": "NEP-141 token contracts, e.g. usdt.tether-token.near"
    },
    "adapter": {
      "type": "string",
      "enum": [
        "nep245",
        "burrow",
        "backed"
      ],
      "description": "How to read 'owed'. Guessed for intents.near and contract.main.burrow.near; default backed (backed_solvency)."
    }
  },
  "required": [
    "target",
    "tokens"
  ]
}
🟢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.

Input Schema

{
  "type": "object",
  "properties": {}
}
🟢checker_status(target, token, checker, network)

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

Input Schema

{
  "type": "object",
  "properties": {
    "target": {
      "type": "string"
    },
    "token": {
      "type": "string"
    },
    "checker": {
      "type": "string",
      "description": "Checker contract account. Default: the testnet deployment."
    },
    "network": {
      "type": "string",
      "enum": [
        "testnet",
        "mainnet"
      ],
      "description": "Default: testnet"
    }
  },
  "required": [
    "target",
    "token"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools