Skip to content

Backed: NEAR solvency checks

io.github.rohan911438/backedrohan911438streamable-httpv0.1.0Scanned

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

3 tools: 1 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 1 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 1Claude Code: ask
  • 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • 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.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • 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.Reads text others writeNo findings

    Why it is in this group

    • The name "checker_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    What the on-chain Backed checker contract last recorded for a (protocol, token) pair: Healthy, Suspected or Confirmed breach, with owed, held and block.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__backed__check_backing",
      "mcp__backed__checker_status"
    ],
    "ask": [
      "mcp__backed__intents_backing_summary"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as backed. Review it before you use it.

Capability tags behind 3 rules
  • mcp__backed__check_backing untrusted-input
  • mcp__backed__intents_backing_summary untrusted-input
  • mcp__backed__checker_status untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/io.github.rohan911438/backed/verify?hash=252dfa41c835f65211e9d1dd8a7ecce8efd705e1d5efdb82759774afca3b8c7d" | jq -e '.changed == false'

Pinned hash 252dfa41c835, from Oct 25, 2026, 17:22 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.github.rohan911438/backed/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for io.github.rohan911438/backed
[![anlyon.dev](https://anlyon.dev/badge/io.github.rohan911438/backed.svg)](https://anlyon.dev/servers/io.github.rohan911438/backed)

Source: MCP Registry · repository. Synced Oct 25, 2026, 18:27 UTC.