TollNode
REMOTE · TOLLNODE.COM
AI models plus live data from LinkedIn, Google, YouTube, TikTok, Amazon and more. Pay per call.
Available components
Last scanned (14 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 21 Nov 2026.
Category AI and Machine Learning
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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1656 tokens (~236/item across 7 items; 7 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 Management0
- Stability check failed: schema churn in the 6 days we've observed: 139 tool removals, 0 breaking changes, 0 auth/transport breaks, 7 additions. See how to fix → Fail
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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 →
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.
- 20 Nov 26 0
- Tool “get_call” rewrote its description, which is the text the model reads security
- Tool “list_calls” rewrote its description, which is the text the model reads security
- “list_calls” reworded the description of “status” cosmetic
- “run_tool” reworded the description of “idempotency_key” cosmetic
- 18 Nov 26 +1
- Stability: 0.07 → fail ▼ security
- Tool “ai-content-check” was removed ▼ security
- Tool “airbnb-search” was removed ▼ security
- Tool “amazon” was removed ▼ security
- Tool “amazon-product” was removed ▼ security
- Tool “amazon-reviews” was removed ▼ security
- Tool “audio-stable-audio-2-5” was removed ▼ security
- Tool “base-wallet-balance” was removed ▼ security
- Tool “booking” was removed ▼ security
- Tool “claude-opus-5-5” was removed ▼ security
- Tool “claude-sonnet-5” was removed ▼ security
- Tool “company-contacts” was removed ▼ security
- Tool “company-registry” was removed ▼ security
- Tool “data-file” was removed ▼ security
- Tool “document-to-markdown” was removed ▼ security
- Tool “domain” was removed ▼ security
- Tool “ebay-sold-prices” was removed ▼ security
- Tool “elevenlabs-turbo-speech” was removed ▼ security
- Tool “elevenlabs-v3-speech” was removed ▼ security
- Tool “email-verify” was removed ▼ security
- Tool “expand-image” was removed ▼ security
- Tool “facebook” was removed ▼ security
- Tool “flux-1-1-pro” was removed ▼ security
- Tool “flux-1-1-pro-ultra” was removed ▼ security
- Tool “flux-2-klein” was removed ▼ security
- Tool “flux-2-max” was removed ▼ security
- Tool “flux-2-pro” was removed ▼ security
- Tool “flux-3-image” was removed ▼ security
- Tool “flux-dev” was removed ▼ security
- Tool “flux-fast” was removed ▼ security
- Tool “flux-fill-pro” was removed ▼ security
- Tool “flux-kontext-fast” was removed ▼ security
- Tool “flux-kontext-max” was removed ▼ security
- Tool “flux-kontext-pro” was removed ▼ security
- Tool “flux-krea” was removed ▼ security
- Tool “google” was removed ▼ security
- Tool “google-reviews” was removed ▼ security
- Tool “gpt-image-1-5” was removed ▼ security
- Tool “gpt-image-2” was removed ▼ security
- Tool “gpt-image-2-5-flare” was removed ▼ security
- Tool “gpt-image-2-5-sunburst” was removed ▼ security
- Tool “gpt-image-2-6-flare” was removed ▼ security
- Tool “gpt-image-2-6-sunburst” was removed ▼ security
- Tool “grok-imagine-image” was removed ▼ security
- Tool “grok-imagine-image-2” was removed ▼ security
- Tool “hotel-search” was removed ▼ security
- Tool “ideogram-4-5” was removed ▼ security
- Tool “ideogram-4-5-edit” was removed ▼ security
- Tool “ideogram-v3-turbo” was removed ▼ security
- Tool “image-describe” was removed ▼ security
- Tool “image-edit-instant” was removed ▼ security
- Tool “image-flash” was removed ▼ security
- Tool “image-instant” was removed ▼ security
- Tool “indeed-jobs” was removed ▼ security
- Tool “instagram” was removed ▼ security
- Tool “instagram-posts” was removed ▼ security
- Tool “instagram-profile” was removed ▼ security
- Tool “krea-3” was removed ▼ security
- Tool “linkedin” was removed ▼ security
- Tool “linkedin-company” was removed ▼ security
- Tool “linkedin-company-posts” was removed ▼ security
- Tool “linkedin-company-search” was removed ▼ security
- Tool “linkedin-jobs” was removed ▼ security
- Tool “linkedin-post-search” was removed ▼ security
- Tool “list_models” was removed ▼ security
- Tool “maps-business-search” was removed ▼ security
- Tool “meta-ad-library” was removed ▼ security
- Tool “minimax-image-01” was removed ▼ security
- Tool “music-lyria-3” was removed ▼ security
- Tool “music-lyria-3-5” was removed ▼ security
- Tool “music-minimax-1-5” was removed ▼ security
- Tool “music-minimax-2-5” was removed ▼ security
- Tool “music-song” was removed ▼ security
- Tool “nano-banana” was removed ▼ security
- Tool “nano-banana-2” was removed ▼ security
- Tool “nano-banana-2-1” was removed ▼ security
- Tool “nano-banana-2-lite” was removed ▼ security
- Tool “nano-banana-pro” was removed ▼ security
- Tool “news-search” was removed ▼ security
- Tool “p-image-ideogram” was removed ▼ security
- Tool “product-page” was removed ▼ security
- Tool “qr-code” was removed ▼ security
- Tool “qwen-image” was removed ▼ security
- Tool “qwen-image-2” was removed ▼ security
- Tool “qwen-image-3” was removed ▼ security
- Tool “qwen-image-3-pro” was removed ▼ security
- Tool “qwen-image-edit-2511” was removed ▼ security
- Tool “qwen-image-edit-plus” was removed ▼ security
- Tool “recraft-v4” was removed ▼ security
- Tool “recraft-v4-pro” was removed ▼ security
- Tool “recraft-v4-svg” was removed ▼ security
- Tool “reddit-search” was removed ▼ security
- Tool “remove-background” was removed ▼ security
- Tool “restore-photo” was removed ▼ security
- Tool “runway-gen-4-image” was removed ▼ security
- Tool “sanctions-screen” was removed ▼ security
- Tool “search-trends” was removed ▼ security
- Tool “seedream-4” was removed ▼ security
- Tool “seedream-4-5” was removed ▼ security
- Tool “seedream-5-lite” was removed ▼ security
- Tool “seedream-5-pro” was removed ▼ security
- Tool “speech-chatterbox-turbo” was removed ▼ security
- Tool “speech-qwen3” was removed ▼ security
- Tool “speech-realtime” was removed ▼ security
- Tool “speech-to-text” was removed ▼ security
- Tool “threads” was removed ▼ security
- Tool “threads-posts” was removed ▼ security
- Tool “tiktok” was removed ▼ security
- Tool “tiktok-hashtag” was removed ▼ security
- Tool “tripadvisor-reviews” was removed ▼ security
- Tool “trustpilot-reviews” was removed ▼ security
- Tool “upscale-crisp” was removed ▼ security
- Tool “upscale-fast” was removed ▼ security
- Tool “upscale-instant” was removed ▼ security
- Tool “url-to-markdown” was removed ▼ security
- Tool “video-gemini-omni-flash” was removed ▼ security
- Tool “video-grok-imagine” was removed ▼ security
- Tool “video-grok-imagine-1-5” was removed ▼ security
- Tool “video-hailuo-2-3” was removed ▼ security
- Tool “video-happyhorse-1-1” was removed ▼ security
- Tool “video-kling-3” was removed ▼ security
- Tool “video-kling-4” was removed ▼ security
- Tool “video-kling-4-flash” was removed ▼ security
- Tool “video-ltx-2-5-fast” was removed ▼ security
- Tool “video-ltx-2-fast” was removed ▼ security
- Tool “video-minimax-h3” was removed ▼ security
- Tool “video-minimax-h3-highspeed” was removed ▼ security
- Tool “video-minimax-h3-lite” was removed ▼ security
- Tool “video-p-video” was removed ▼ security
- Tool “video-p-video-2” was removed ▼ security
- Tool “video-p-video-2-pro” was removed ▼ security
- Tool “video-p-video-2-pro-avatar” was removed ▼ security
- Tool “video-p-video-2-pro-reference” was removed ▼ security
- Tool “video-p-video-2-pro-replace” was removed ▼ security
- Tool “video-p-video-2-voice” was removed ▼ security
- Tool “video-p-video-animate” was removed ▼ security
- Tool “video-p-video-avatar” was removed ▼ security
- Tool “video-p-video-edit” was removed ▼ security
- Tool “video-p-video-replace” was removed ▼ security
- Tool “video-p-video-voice” was removed ▼ security
- Tool “video-pixverse-v6-max” was removed ▼ security
- Tool “video-runway-gen-4-5” was removed ▼ security
- Tool “video-seedance-1-lite” was removed ▼ security
- Tool “video-seedance-1-pro-fast” was removed ▼ security
- Tool “video-seedance-2” was removed ▼ security
- Tool “video-seedance-2-5” was removed ▼ security
- Tool “video-seedance-2-fast” was removed ▼ security
- Tool “video-seedance-2-mini” was removed ▼ security
- Tool “video-upscale-4k” was removed ▼ security
- Tool “video-veo-3-1” was removed ▼ security
- Tool “video-veo-3-1-fast” was removed ▼ security
- Tool “video-wan-2-2” was removed ▼ security
- Tool “video-wan-2-2-text” was removed ▼ security
- Tool “video-wan-3” was removed ▼ security
- Tool “vin-decode” was removed ▼ security
- Tool “wan-2-7-image-pro” was removed ▼ security
- Tool “wan-image-small” was removed ▼ security
- Tool “weather” was removed ▼ security
- Tool “web-search” was removed ▼ security
- Tool “web-search-markdown” was removed ▼ security
- Tool “webpage-screenshot” was removed ▼ security
- Tool “website-reader” was removed ▼ security
- Tool “x-search” was removed ▼ security
- Tool “x-twitter” was removed ▼ security
- Tool “youtube” was removed ▼ security
- Tool “youtube-comments” was removed ▼ security
- Tool “youtube-search” was removed ▼ security
- Tool “youtube-transcript” was removed ▼ security
- Tool “z-image-turbo” was removed ▼ security
- Tool “z-image-turbo-lora” was removed ▼ security
- Tool “zillow-home” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 83% → 100% ▲ functional
- Schema quality: 34415 → 1552 ▲ functional
- Schema quality: good → excellent functional
- Destructive annotations: 100 → pass functional
- Server version: 1.0.0 → 1.4.0 functional
- New tool “get_balance” functional
- New tool “get_call” functional
- New tool “get_tool” functional
- New tool “list_calls” functional
- New tool “run_tool” functional
- New tool “search_tools” functional
- New tool “upload_file” functional
- 17 Nov 26 0
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- Tool “document-to-markdown” rewrote its description, which is the text the model reads security
- Tool “elevenlabs-turbo-speech” rewrote its description, which is the text the model reads security
- Tool “elevenlabs-v3-speech” rewrote its description, which is the text the model reads security
- Tool “flux-2-pro” rewrote its description, which is the text the model reads security
- Tool “flux-dev” rewrote its description, which is the text the model reads security
- Schema quality: 182 → 202 ▼ functional
- “document-to-markdown” reworded the description of “file” cosmetic
- “expand-image” reworded the description of “image” cosmetic
- “flux-3-image” reworded the description of “images” cosmetic
- “flux-dev” dropped the optional parameter “image” cosmetic
- “flux-dev” dropped the optional parameter “prompt_strength” cosmetic
- 15 Nov 26 71
First indexed and scored.
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://tollnode.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.tollnode.com | CN=YR1,O=Let's Encrypt,C=US | 8 Nov 2026 | 6 Feb 2027 | RSA 2048 | SHA256-RSA | 69223adb8c48a0b9fe75dee453c79a9d309 |
| SANs: *.tollnode.com, tollnode.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tollnode.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| tollnode.com. | 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=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tollnode.com/mcp | Verified | 200 | |
| http (plaintext) | http://tollnode.com/mcp | HTTPS enforced | 308 | https://tollnode.com/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 →
get_balance Get your account balance ~68
Free; reads only. Returns your prepaid account balance in US dollars, so you can check a batch is affordable before running it. Needs an account API key on the connection (Authorization: Bearer tn_live_…). With x402 there is no balance: each call is paid from your own wallet.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_call Look up an earlier call ~183
Free; reads only. Looks up one of your earlier account calls by its request id (given after every charged run_tool result and in errors): whether it is running, succeeded, failed or was rejected, what it was charged, the error code and message if it failed, the API key that made it, and its result again. Use it to recover a result after a dropped connection instead of paying twice: a call can't be cancelled and keeps running to the end even if you disconnect. list_calls finds request ids. Needs an account API key on the connection; x402 calls are not looked up here.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | The request id, a UUID such as 3f2b6c1e-8d4a-4f7e-9a1b-2c3d4e5f6a7b. |
No output schema declared.
No examples provided.
get_tool Get a tool's inputs and price ~123
Free; reads only. Returns everything needed to run one tool: what it does, when to use it and when not, its full JSON input schema with limits, its price per call and price options, its actions (for platform tools such as linkedin or google), an example input and its web page. Call it after search_tools and before run_tool so the input is right the first time.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The tool's name from search_tools, e.g. 'gpt-image-2-5-sunburst', 'linkedin' or 'weather'. |
No output schema declared.
No examples provided.
list_calls List your recent calls and charges ~232
Free; reads only. Lists your recent account calls, newest first: the tool, whether it succeeded, failed, was rejected (refused before running) or is still running, what it was charged (failed and rejected calls cost $0), the error code and message of a failed or rejected call, the name of the API key that made it, and its request id, plus the total charged on the page. Use it to review spending or find a request id for get_call. Filter by status, page back with before (the next value from the previous page). Needs an account API key on the connection; x402 calls are paid from your own wallet and show in its history instead.
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | Only calls made before this time (ISO 8601). Use the createdAt of the last call on the previous page. |
| limit | integer | – | How many calls to return, 1 to 50. Default 20. |
| status | string | – | Only calls with this status (rejected = refused before running, e.g. a rate limit). Leave out for all. |
No output schema declared.
No examples provided.
run_tool Run a tool (paid) ~324
Runs one TollNode tool and returns its result: text, data, or links to the files it made. Spends money: the tool's price (see get_tool) is charged only when the call returns a usable result; a refused input, a failure or an empty result costs nothing. Every successful call is charged again, so do not repeat one that worked; send idempotency_key to make a retry safe. Pay from an account balance (API key on the connection) or with x402: the first call answers with the payment requirements as an error result; sign them and call again with the payment in params._meta["x402/payment"]. Account results end with the amount charged and a request id for get_call. The whole request is capped at 4.5 MB: send photos, audio and video as https links, or call upload_file first for anything over about 3 MB and pass its fileUrl.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Optional, any unique text. Repeating an account call with the same key returns the first successful result without charging again. A call that was refused (rate limit, bad input, low balance) or fail… |
| input | object | yes | The tool's input fields, exactly as get_tool's inputSchema describes them, e.g. {"action": "current", "location": "Lisbon"}. |
| name | string | yes | The tool's name from search_tools, e.g. 'weather'. |
No output schema declared.
No examples provided.
search_tools Search TollNode tools ~222
Free; reads only. Finds the TollNode tools for a task and returns each match's name, title, one-line purpose, category and price per call, best matches first. Use it first whenever you need a capability (make an image or video, a voice or song, read a web page, search Google or Maps, get LinkedIn, YouTube, Amazon or other platform data, check a domain, weather or public data). Then call get_tool with the name you pick, then run_tool. With no query it lists everything in the category, or the whole catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only this category, e.g. Image, Video, Audio, Search, Social, Shopping, Business, Travel, Lookup, Document. |
| limit | integer | – | Most results to return, 1 to 50. Default 20 |
| query | string | – | The task, model or platform in plain words, e.g. 'remove background', 'video with sound', 'linkedin company', 'gpt image'. Leave out to list all. |
No output schema declared.
No examples provided.
upload_file Get an upload link for a big file ~276
Free. A tool request is capped at 4.5 MB in total, and inline base64 files count toward it (base64 adds a third). For a bigger file, or any local file you would rather not inline (a long voice track, a full-size photo, a video), call this first: it returns a one-time uploadUrl and the fileUrl the file will have. PUT the file's raw bytes to uploadUrl within 15 minutes with the returned content-type header (the response includes a ready curl command; up to 100 MB), then pass fileUrl in the tool's file field (for example image or audio) with run_tool. One file per link. The file is deleted once a call that used it succeeds, so upload again for each new call; if no call succeeds with it, it is deleted after 6 hours.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | – | The file's media type: image/jpeg, image/png, image/webp, image/gif, audio/mpeg, audio/wav, audio/flac, audio/ogg, audio/mp4, video/mp4, video/webm, video/quicktime or application/pdf. |
| filename | string | – | Optional instead of content_type: the file's name, e.g. 'voice.mp3'; its extension sets the type. |
No output schema declared.
No examples provided.
How do I install the TollNode MCP server?
TollNode is a hosted endpoint at https://tollnode.com/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 · tollnode.com
claude mcp add --transport http tollnodemcp-tollnode 'https://tollnode.com/mcp'
What is the TollNode MCP server?
TollNode is an MCP server listed in the public MCP registry as io.github.tollnodemcp/tollnode. AI models plus live data from LinkedIn, Google, YouTube, TikTok, Amazon and more. Pay per call. This page covers its hosted endpoint (https://tollnode.com/mcp).
Is the TollNode MCP server safe to use?
TollNode scores 72 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 TollNode MCP server expose?
TollNode exposes 7 tools: search_tools, get_tool, run_tool, get_call, list_calls, and 2 more. Their descriptions and schemas cost roughly 1,428 tokens of context every time the server is loaded.
Does the TollNode MCP server require authentication?
No. We connected to TollNode without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TollNode MCP server still maintained?
TollNode 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 TollNode MCP server?
VerifyMCP ran 13 checks on TollNode, 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.