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.

Nanotoll MCP

REMOTE · MCP.NANOTOLL.DEV · SCANNED AUG 26

7 agent tools (prune, convert, estimate, diff, patch, generate, validate). USDC on Base L2.

Available components

remote · mcp.nanotoll.dev 4
4 Trust /100

Degraded

One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

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 →

Endpoint Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the Nanotoll MCP server?

Nanotoll MCP is a hosted endpoint at https://mcp.nanotoll.dev/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 · mcp.nanotoll.dev

# add to Claude Code
claude mcp add --transport http dev-nanotoll-nanotoll-mcp 'https://mcp.nanotoll.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-nanotoll-nanotoll-mcp": {
      "url": "https://mcp.nanotoll.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-nanotoll-nanotoll-mcp": {
      "type": "http",
      "url": "https://mcp.nanotoll.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.dev-nanotoll-nanotoll-mcp]
url = "https://mcp.nanotoll.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-nanotoll-nanotoll-mcp": {
      "type": "remote",
      "url": "https://mcp.nanotoll.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-nanotoll-nanotoll-mcp --url 'https://mcp.nanotoll.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-nanotoll-nanotoll-mcp:
    url: "https://mcp.nanotoll.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-nanotoll-nanotoll-mcp": {
      "Transport": "http",
      "Url": "https://mcp.nanotoll.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add dev-nanotoll-nanotoll-mcp -t streamable-http -u 'https://mcp.nanotoll.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "dev-nanotoll-nanotoll-mcp": {
      "type": "http",
      "url": "https://mcp.nanotoll.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 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
  • 21 Aug 26 4

    First indexed and scored.

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 26 Aug 2026 · Probed https://mcp.nanotoll.dev/mcp

TLS unreached
DNSSEC inconclusive

Validation of mcp.nanotoll.dev. — Inconclusive

Zone DS Keys Algorithms Outcome
mcp.nanotoll.dev. Error no A/AAAA/CNAME RRset answered for the name
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.nanotoll.dev/mcp Unreachable
http (plaintext) http://mcp.nanotoll.dev/mcp HTTPS enforced
MCP tools

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.

No tool schema has been captured from this endpoint yet.

Common questions

What is the Nanotoll MCP server?

Nanotoll MCP is listed in the public MCP registry as dev.nanotoll/nanotoll-mcp. 7 agent tools (prune, convert, estimate, diff, patch, generate, validate). USDC on Base L2. This page covers its hosted endpoint (https://mcp.nanotoll.dev/mcp).

Is the Nanotoll MCP server safe to use?

Nanotoll MCP scores 4 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.

Does the Nanotoll MCP server require authentication?

Its publisher declares that Nanotoll MCP requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.