Is the Tonresistor Resistance Tools MCP server down?

mcp-registry/io.github.tonresistor/resistance-tools-mcp · v0.2.6

Also listed as glama/tonresistor/resistance-tools-mcp

healthy
Last checked 2026-10-18 03:42 UTC · handshake 521ms

As of 2026-10-18 03:42 UTC, the Tonresistor Resistance Tools MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 11 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.9%
checks observed
3,609
outages (90d)
11
tools
51

MCP tools for TON Sites, TON DNS and TON Storage.

Install Tonresistor Resistance Tools MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http tonresistor-resistance-tools-mcp-server https://app.resistance.dog/api/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "tonresistor-resistance-tools-mcp-server": {
      "type": "http",
      "url": "https://app.resistance.dog/api/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (67/100)

D (67/100): 0 error(s), 6 warning(s) across 51 tool(s); ~5,613 tokens of tool definitions.
Scores higher than 2% of 15,352 MCP servers Glimind has audited.
Its tool list costs an agent ~5,613 tokens per session — more than 60% of servers.
67 → 67 since 2026-10-17
no tool-poisoning patterns
Schemas89
Descriptions32
Safety hints100
Token cost75
Client compatibility20
Protocol100
Reliability85
Stability90

What to fix (7)

51 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

51 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).

Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →

Tools: auth.policy, auth.status, deployments.list, dns.lookup, dns.send_name_tx and 46 more

105 parameter(s) across 42 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: dns.lookup, dns.send_name_tx, dns.send_record_tx, dns.send_renew_tx, dns.send_transfer_tx and 37 more

1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: sites.publish_template

Handshake + tools/list takes ~2,540 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

In the last 30 days: 1 tool(s) removed and 0 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 51 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 42 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.tonresistor%2Fresistance-tools-mcp/fixes

auth.policy 1 change
{
  "name": "auth_policy",
  "description": "Return public MCP auth flows, scopes, safety controls, retention, and confirmation rules.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  },
  "title": "MCP auth and safety policy"
}
auth.status 1 change
{
  "name": "auth_status",
  "description": "Return whether this MCP session is authenticated.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  },
  "title": "MCP auth status"
}
deployments.list 1 change
{
  "name": "deployments_list",
  "description": "List retained deployments across the owner's sites.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": false
  },
  "title": "List deployments"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.tonresistor/resistance-tools-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.tonresistor/resistance-tools-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.tonresistor%2Fresistance-tools-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.tonresistor%2Fresistance-tools-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.tonresistor%2Fresistance-tools-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.tonresistor%2Fresistance-tools-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.tonresistor%2Fresistance-tools-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.tonresistor%2Fresistance-tools-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:51b10b175875d137…, first seen 2026-10-17, included at leaf 4587 of 20,170. Version history · verify what your client received.

Tools (51)

Compare: most reliable security servers · most reliable devops servers · most reliable knowledge servers · most reliable web servers · most reliable blockchain servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Tonresistor Resistance Tools MCP server down right now?

As of 2026-10-18 03:42 UTC, the Tonresistor Resistance Tools MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 11 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Tonresistor Resistance Tools MCP server provide?

Tonresistor Resistance Tools MCP server advertises 51 tools, including auth.policy, auth.status, deployments.list, dns.lookup, dns.send_name_tx.

How do I install Tonresistor Resistance Tools MCP server?

Point your MCP client at this streamable-http endpoint: https://app.resistance.dog/api/mcp

Is the Tonresistor Resistance Tools MCP server safe to connect to an AI agent?

Glimind scanned all 51 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Tonresistor Resistance Tools MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.