Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Resistance Tools

REMOTE · APP.RESISTANCE.DOG

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

0 this week 71 Trust /100

Last scanned (14 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Recent critical change

Authorization (16 Sept 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability36
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 2345 tokens (~41/item across 56 items; 51 tools + 5 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 14 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 53 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 21 Oct 26 0
    • Stability: fail → pass ▲ security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 0
    • New tool “dns.send_transfer_tx”, which the server declares destructive security
    • New tool “sites.attach_domain”, which the server declares destructive security
    • New tool “sites.unlink_domain”, which the server declares destructive security
    • Tool “domains.records” rewrote its description, which is the text the model reads security
    • Schema quality: 1910 → 2345 ▼ functional
    • New tool “domains.list_usernames” functional
    • New tool “sites.list_domains” functional
    • New tool “sites.preflight_domain” functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://app.resistance.dog/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=app.resistance.dog CN=YE1,O=Let's Encrypt,C=US 2 Nov 2026 31 Jan 2027 ECDSA 256 ECDSA-SHA384 5282b04297cd1a969dc6f1b77cd45c8fc01
SANs: app.resistance.dog, tonsite.resistance.dog
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.resistance.dog. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dog. DS published 56555 8 Verified
resistance.dog. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
referrer-policy no-referrer
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.resistance.dog/api/mcp Verified 200
http (plaintext) http://app.resistance.dog/api/mcp HTTPS enforced 301 https://app.resistance.dog/api/mcp
MCP tools · 51 exposed · ~2,200 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
wallet.me ~18

Return the authenticated MCP owner/actor wallet context.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Resistance Tools MCP server?

Resistance Tools is a hosted endpoint at https://app.resistance.dog/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · app.resistance.dog

# add to Claude Code
claude mcp add --transport http tonresistor-resistance-tools-mcp 'https://app.resistance.dog/api/mcp'
Common questions

What is the Resistance Tools MCP server?

Resistance Tools is an MCP server listed in the public MCP registry as io.github.TONresistor/resistance-tools-mcp. MCP tools for TON Sites, TON DNS and TON Storage. This page covers its hosted endpoint (https://app.resistance.dog/api/mcp).

Is the Resistance Tools MCP server safe to use?

Resistance Tools scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Resistance Tools MCP server expose?

Resistance Tools exposes 51 tools: auth.status, auth.policy, wallet.me, mcp.access.list, mcp.audit.list, and 46 more. Their descriptions and schemas cost roughly 2,200 tokens of context every time the server is loaded.

Does the Resistance Tools MCP server require authentication?

No. We connected to Resistance Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Resistance Tools MCP server still maintained?

Resistance Tools is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Resistance Tools MCP server?

VerifyMCP ran 13 checks on Resistance Tools, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.