Resistance Tools
REMOTE · APP.RESISTANCE.DOG · SCANNED SEP 28
MCP tools for TON Sites, TON DNS and TON Storage.
Available components
Recent critical change
Authorization (16 Sept 2026). See the changelog before you install this server.
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (mcp.access.revoke_consent). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 Management98
- Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 6 additions. See how to fix → Fail
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
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
claude mcp add --transport http tonresistor-resistance-tools-mcp 'https://app.resistance.dog/api/mcp'
{
"mcpServers": {
"tonresistor-resistance-tools-mcp": {
"url": "https://app.resistance.dog/api/mcp"
}
}
} {
"servers": {
"tonresistor-resistance-tools-mcp": {
"type": "http",
"url": "https://app.resistance.dog/api/mcp"
}
}
} [mcp_servers.tonresistor-resistance-tools-mcp] url = "https://app.resistance.dog/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tonresistor-resistance-tools-mcp": {
"type": "remote",
"url": "https://app.resistance.dog/api/mcp",
"enabled": true
}
}
} openclaw mcp add tonresistor-resistance-tools-mcp --url 'https://app.resistance.dog/api/mcp' --transport streamable-http
mcp_servers:
tonresistor-resistance-tools-mcp:
url: "https://app.resistance.dog/api/mcp" {
"McpServers": {
"tonresistor-resistance-tools-mcp": {
"Transport": "http",
"Url": "https://app.resistance.dog/api/mcp"
}
}
} assistant mcp add tonresistor-resistance-tools-mcp -t streamable-http -u 'https://app.resistance.dog/api/mcp'
{
"mcpServers": {
"tonresistor-resistance-tools-mcp": {
"type": "http",
"url": "https://app.resistance.dog/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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
- 25 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
- 21 Sept 26 0
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 0.2.6 ▼ security
- Tool “payments.send_tx” was removed ▼ security
- 16 Sept 26 0
- Authorization: unverified → fail ▼ critical
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 0 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 15 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Authorization: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Schema quality: 0 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Sept 26 +1
- Stability: 0.97 → pass security
- 26 Aug 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
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 28 Sept 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=YE2,O=Let's Encrypt,C=US | 3 Sept 2026 | 2 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5f7db12402045ad5b7a976a66ae9c061734 |
| SANs: app.resistance.dog, tonsite.resistance.dog | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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. | present | 48736 | 8 | Verified |
| resistance.dog. | absent | 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 |
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 →
wallet.me Wallet context ~18
Return the authenticated MCP owner/actor wallet context.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.