Backed: NEAR solvency checks

io.github.rohan911438Published by GitHub account rohan911438v0.1.0Updated Oct 26, 2026

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

The publisher's own server: Agent Market

VerifiedStreamable HTTPWeb executableFinance Security & Monitoring

Server details

Identifier: io.github.rohan911438/backed
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 26, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account rohan911438 for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.rohan911438%2Fbacked.svg)](https://sourceweft.com/mcp/io.github.rohan911438%2Fbacked?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Read-only NEAR solvency checker: compares what a protocol owes with the tokens it actually holds at one block, before you deposit.

What you can do: Check a protocol's backing: read what a NEAR contract owes and what it holds at the same block, for intents.near, Burrow lending and any contract implementing backed_solvency
Review the latest daily scan of every NEP-141 token in NEAR Intents, showing which are backed, which are under-backed and by how much
Look up the on-chain checker contract's last recorded verdict for a protocol and token pair: Healthy, Suspected or Confirmed breach, with owed, held and block
When to use it: Use it before depositing into a NEAR protocol, or when you want a quick read on whether NEAR Intents tokens are fully backed. It is a read-only sanity check rather than a trading or portfolio tool.
Requirements: A remote streamable HTTP endpoint; no package, account, API key or environment variable is declared. Network access to the hosted endpoint is needed.

Before you install

Results reflect the protocol's own accounting view and on-chain balances at a single block, so they can go stale; the daily scan is a snapshot. Treat verdicts as a signal to investigate, not a guarantee, and verify before moving funds.

Installation

In SourceWeft

Open Backed: NEAR solvency checks in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.rohan911438%2Fbacked/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

This repository has no README.

Tools

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.

Parameterstargetrequiredtokensrequiredadapter

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.

Takes no parameters.

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.

Parameterstokenrequiredtargetrequiredcheckernetwork

Version history

v0.1.0LatestOct 26, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.

Other Near integrations

Agent Market

ai.near.marketOfficial publisher

Remote Agent Market endpoint that lets an assistant find AI agents for a task, brief one, and follow the job through to its result.

Streamable HTTPWeb executableAuth

AI & MLCredential requiredNov 7, 2026

NEARpedia

Published by GitHub account UnityNodes

Remote NEAR knowledge server that lets an assistant check whether NEAR code, packages and APIs are stale, and read live protocol, governance and ecosystem data.

Streamable HTTPWeb executable

Databases27 toolsNov 5, 2026