MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Code & DevOps

Backed: NEAR solvency checks

By rohan911438 Verified namespace

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

WebsiteSource code
Connect to Backed: NEAR solvency checks
Checks passed
14 / 22

1 failed · 7 not measured

Median response
649 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
3

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
103
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
310
Publisher identityCan the publisher be traced to its source?
402

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 430 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name backed.

  • Pass
    Lists tools

    tools/list returned 3 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 649 ms over 2 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 846 ms over 2 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    2 of 2 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Pass
    Stable tool list

    No tool was removed and no required parameter was added in the last 30 days.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Fail
    Parameters documented

    5 of 7 parameters have a description (71%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Not measured
    Website matches publisher

    This namespace is not a reverse domain, so the website comparison does not apply.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Pass
    Repo owner matches

    The GitHub repository owner matches the namespace login.

  • Pass
    Recently updated

    Updated 2026-10-25T17:17:54.183495Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Start using Backed: NEAR solvency checks

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

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

Capabilities

Tools 3

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.

Discovered
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.

Discovered
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.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected430 ms3
Connected868 ms3

Related servers

All alternatives

Same function and industry, ranked by checks passed then median latency.

Explore alternatives to Backed: NEAR solvency checks