Skip to main content
Glama

Backed: NEAR solvency checks

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
rohan911438/Backed
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.5/5.0

Scored across 3 tools

Disambiguation4/5

The three tools target distinct tiers: a live on-chain computation (check_backing), a stored verdict lookup (checker_status), and an aggregate daily scan for one specific protocol (intents_backing_summary). The only mild overlap is between check_backing and checker_status, since both answer 'is this pair backed?', but the live-vs-recorded distinction is spelled out.

Naming Consistency3/5

All names are snake_case, which helps, but the patterns differ: verb_noun (check_backing), noun_noun (checker_status), and a prefixed noun compound (intents_backing_summary). Readable, but an agent cannot infer a naming convention to guess a fourth tool.

Tool Count4/5

Three tools is lean but proportionate for a narrow, single-purpose solvency-checking server. Each tool covers a genuinely different need (on-demand check, recorded status, ecosystem-wide scan), so nothing feels padded.

Completeness3/5

The core read paths are covered, but there is no discovery surface: no tool to list supported protocols/tokens or to enumerate all token balances for an arbitrary protocol (the aggregate scan is hard-coded to intents.near). No historical or batch-per-token checking exists either, forcing per-token calls once an address is known.

Available Tools

3 tools
check_backingA
Read-only
Inspect

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.

Inputs: target (required), tokens (required), adapter.

checker_statusB
Read-only
Inspect

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

Inputs: token (required), target (required), checker, network.

intents_backing_summaryA
Read-only
Inspect

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.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to inspect NEAR mainnet account state changes, permissions, balances, and payment receipts, and to run transfer preflights with unsigned wallet templates.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server for NEAR blockchain wallet data, providing account summaries, transaction history, token transfers, and activity reports via the NearBlocks API.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI agents and developer tools read access to a blockchain network's blocks, transactions, accounts, validators, staking tiers, contract reads and fee estimates, plus post-quantum signature status checks and unsigned transfers for the user's own wallet to sign. It never signs, holds keys, or broadcasts.
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.