Nanotoll MCP
REMOTE · MCP.NANOTOLL.DEV
7 agent tools (prune, convert, estimate, diff, patch, generate, validate). USDC on Base L2.
Available components
Last scanned (9 hours ago)
Scores higher than 95% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Developer Tools
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1165 tokens (~145/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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
- 26 Sept 26 0
- Stability: 0.97 → pass security
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +3
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2025-03-26 → 2026-07-28 functional
- Server version: 0.3.2 → 3.4.0 functional
- 1 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 952 → 1165 ▼ functional
- New tool “read” functional
- “prune” reworded the description of “comment_prefix” cosmetic
- 30 Aug 26 0
- Tool “convert” rewrote its description, which is the text the model reads security
- Tool “estimate” rewrote its description, which is the text the model reads security
- 29 Aug 26 0
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “convert” rewrote its description, which is the text the model reads security
- Tool “diff” rewrote its description, which is the text the model reads security
- Tool “estimate” rewrote its description, which is the text the model reads security
- Tool “generate” rewrote its description, which is the text the model reads security
- Tool “patch” rewrote its description, which is the text the model reads security
- Tool “prune” rewrote its description, which is the text the model reads security
- Tool “validate” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 40% → 100% ▲ functional
- Schema quality: good → excellent functional
- “convert” reworded the description of “from_format” cosmetic
- “convert” reworded the description of “to_format” cosmetic
- “diff” reworded the description of “text_a” cosmetic
- “diff” reworded the description of “text_b” cosmetic
- “estimate” reworded the description of “input_tokens” cosmetic
- “estimate” reworded the description of “output_tokens” cosmetic
- “generate” reworded the description of “endpoints” cosmetic
- “generate” reworded the description of “links” cosmetic
- “generate” reworded the description of “name” cosmetic
- “generate” reworded the description of “overview” cosmetic
- “generate” reworded the description of “pricing” cosmetic
- “generate” reworded the description of “tagline” cosmetic
- “patch” reworded the description of “text” cosmetic
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 23 Oct 2026 · Probed https://mcp.nanotoll.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.nanotoll.dev | CN=YE1,O=Let's Encrypt,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5400299c166ad82813326e184b418d144cc |
| SANs: mcp.nanotoll.dev | ||||||
| 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 mcp.nanotoll.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| nanotoll.dev. | 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; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.nanotoll.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.nanotoll.dev/mcp | HTTPS enforced | 308 | https://mcp.nanotoll.dev/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 →
convert ~137
Transform text between JSON, YAML, TOML, and CSV formats. Returns the converted text and input/output character metrics. Note some conversions can be lossy (e.g. JSON to CSV flattens nested structures). Requires a valid API key (Bearer token); billing is per input character — insufficient balance returns HTTP 402. For removing comments use `prune`, for generating llms.txt use `generate`.
| Name | Type | Req | Description |
|---|---|---|---|
| from_format | string | yes | Source format of the input payload. |
| payload | string | yes | Text to convert (1 char min, 10 MiB max). |
| to_format | string | yes | Target format to convert into. |
No output schema declared.
No examples provided.
diff ~96
Generate a unified diff between two text versions (the before and after). Returns the diff text plus metrics (lines added, lines removed, output chars). Requires a valid API key (Bearer token); billing is per combined input characters. To apply a diff, use `patch`.
| Name | Type | Req | Description |
|---|---|---|---|
| text_a | string | yes | First text version (the "before" text). |
| text_b | string | yes | Second text version (the "after" text). |
No output schema declared.
No examples provided.
estimate ~151
Estimate the USD cost of an LLM API call using the CWEP four-flow model (request generation, request processing, response generation, response reception). Returns a JSON object with the per-flow cost breakdown, the total, and the pricing source date. Unknown model names return HTTP 422 — check GET /api/v1/pricing on costa.nanotoll.dev for the supported list (no auth needed). Requires a valid API key (Bearer token); billing is per input character.
| Name | Type | Req | Description |
|---|---|---|---|
| input_tokens | integer | yes | Number of input (prompt) tokens. |
| model | string | yes | Model name (e.g. gpt-4o). |
| output_tokens | integer | yes | Number of output (completion) tokens. |
No output schema declared.
No examples provided.
generate ~222
Generate an llms.txt agent-discovery file from structured service metadata (name, endpoints, overview, links, pricing). Returns the llms.txt content and output metrics. Requires a valid API key (Bearer token); billing is per input character. To check an existing llms.txt for spec compliance, use `validate`.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoints | array | yes | API endpoints to list in the llms.txt. Each item has method, path, and description. |
| links | array | – | Optional related links (docs, source, etc.). Each item has title and url. |
| name | string | yes | Service name (H1 title of the llms.txt file). |
| overview | array | – | Paragraphs of prose describing the service. Each array element becomes a paragraph in the llms.txt Overview section. |
| pricing | string|null | – | Pricing summary string (e.g. "$0.0002 per call"). Pass null to omit. |
| tagline | string|null | – | One-line summary of the service, shown as a subtitle below the H1. Pass null to omit. |
No output schema declared.
No examples provided.
patch ~75
Apply a unified diff patch to text, producing the transformed output. Returns the patched text. Requires a valid API key (Bearer token); billing is per combined input characters. To generate a diff, use `diff`.
| Name | Type | Req | Description |
|---|---|---|---|
| patch | string | yes | Unified diff patch text. |
| text | string | yes | Original text to apply the patch to. |
No output schema declared.
No examples provided.
prune ~175
Strip comments and empty lines from text to reduce token count before sending to an LLM. Returns the pruned text and character metrics. Requires a valid API key (Bearer token); billing is per input character — insufficient balance returns HTTP 402. For format conversion use `convert`, for generating llms.txt use `generate`.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_prefix | string | – | Optional. Explicit comment-line prefix to strip outside code fences (e.g. '//' for C-style code). Omit for format-aware pruning: markdown '#' headings are preserved (v101 #12 note), no line stripping… |
| payload | string | yes | Text to prune (1 char min, 10 MiB max). |
| remove_empty_lines | boolean | – | If true, empty lines outside code fences are removed. |
No output schema declared.
No examples provided.
read ~169
Fetch a web page and return clean GitHub-flavored markdown at a strict token budget. DOM-density scoring strips boilerplate (CSS, JS, navbars, tracking) — raw HTML averages 80-95% noise. Requires a valid API key (Bearer token); billing is $0.0005 flat per read — insufficient balance returns HTTP 402. Fetch failures return HTTP 422 and are refunded.
| Name | Type | Req | Description |
|---|---|---|---|
| include_links | boolean | – | If true, hyperlinks are kept as markdown links. |
| max_tokens | integer | – | Optional token budget — markdown is truncated to this many estimated tokens. Omit for full page. |
| preserve_tables | boolean | – | If true, HTML tables are preserved as GFM tables. |
| url | string | yes | URL of the web page to fetch and convert to markdown. |
No output schema declared.
No examples provided.
validate ~81
Validate an llms.txt payload for spec compliance (H1 title, endpoints section, pricing section, structure). Returns a validation report with errors, warnings, and structural flags. Requires a valid API key (Bearer token); billing is per input character. To generate new llms.txt, use `generate`.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | llms.txt content to validate. |
No output schema declared.
No examples provided.
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
claude mcp add --transport http dev-nanotoll-nanotoll-mcp 'https://mcp.nanotoll.dev/mcp'
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 87 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 Nanotoll MCP server expose?
Nanotoll MCP exposes 8 tools: prune, convert, estimate, diff, patch, and 3 more. Their descriptions and schemas cost roughly 1,106 tokens of context every time the server is loaded.
Does the Nanotoll MCP server require authentication?
No. We connected to Nanotoll MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nanotoll MCP server still maintained?
Nanotoll MCP is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.