Home / MCP registry index / io.github.TONresistor/resistance-tools-mcp

Resistance Tools

io.github.TONresistor/resistance-tools-mcp in the official MCP registry. Endpoint https://app.resistance.dog/api/mcp. Source: github.com/TONresistor/resistance-tools-mcp.

The registry describes it as: MCP tools for TON Sites, TON DNS and TON Storage.

We read its 51 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

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

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "resistance-tools-mcp": {
      "url": "https://app.resistance.dog/api/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"resistance-tools-mcp","type":"http","url":"https://app.resistance.dog/api/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

auth.status auth.policy wallet.me mcp.access.list mcp.audit.list mcp.audit.summary mcp.access.revoke_consent sites.list_domains sites.preflight_domain sites.attach_domain sites.unlink_domain sites.list sites.get_content sites.send_link_tx sites.list_releases sites.publish_files sites.publish_template sites.rollback sites.delete deployments.list domains.list_usernames dns.send_transfer_tx dns.lookup domains.list domains.records dns.send_record_tx dns.send_name_tx dns.send_renew_tx subdomains.list_collections subdomains.list_items subdomains.get_collection subdomains.get_item subdomains.control subdomains.create_collection_tx subdomains.mint_tx subdomains.collection_action_tx subdomains.transfer_item_tx subdomains.recovery_tx media.upload_image storage.list_bags storage.bag_details storage.providers storage.provider_funding_session storage.provider_funding_preview storage.provider_quote storage.provider_operation storage.send_bag_link_tx storage.send_provider_tx storage.create_bag storage.pin_bag storage.delete_bag

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-tonresistor-resistance-tools-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-tonresistor-resistance-tools-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.