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.

funn.to Funnel Generator

REMOTE · FUNN.TO · SCANNED SEP 20

Generate Amazon affiliate sales funnels from product URLs. AI-powered, free.

Available components

+1 this week 79 Trust /100
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 → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 362 tokens (~120/item across 3 items; 3 tools + 0 resources), lean.Pass
  • 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
Install

How do I install the funn.to Funnel Generator MCP server?

funn.to Funnel Generator is a hosted endpoint at https://funn.to/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 · funn.to

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

  • 20 Sept 26 +1
    • Tool “generate_funnel” rewrote its description, which is the text the model reads security
    • Schema quality: 52 → 120 functional
    • Schema quality: good → excellent functional
    • “generate_funnel” reworded the description of “amazon_url” cosmetic
    • “generate_funnel” reworded the description of “store_id” cosmetic
  • 19 Sept 26 +45
    • Injection markers: unverified → pass security
    • Stability: unverified → pass security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: not serving MCP → reachable functional
    • Tool coverage: unverified → 100 functional
    • MCP protocol: unverified → pass functional
  • 18 Sept 26 −45
    • Endpoint reachability: reachable → not serving MCP security
    • Stability: pass → unverified security
    • Tool safety: pass → unverified security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
  • 11 Sept 26 0
    • Stability: 0.97 → pass security
  • 10 Sept 26 0
    • Stability: pass → 0.97 functional
  • 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
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

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 20 Sept 2026 · Probed https://funn.to/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=funn.to CN=YR2,O=Let's Encrypt,C=US 15 Sept 2026 14 Dec 2026 RSA 2048 SHA256-RSA 535d5332a21d604fd0c6d9df8a54655432a
SANs: funn.to
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
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 funn.to. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
to. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://funn.to/mcp Verified 200
http (plaintext) http://funn.to/mcp HTTPS enforced 301 https://funn.to/mcp
MCP tools · 3 exposed · ~362 tokens

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 →

Tool Tokens
generate_funnel ~315

Generate a hosted Amazon affiliate landing page from a US amazon.com product URL the user gave you. One call takes ~4 minutes and costs real money, with no undo and no refund, so call it only for a link the user actually supplied. Never build a URL from an ASIN you remember, and never submit an example URL. If you do not have the user's link, ask for it instead of calling. No account needed.

NameTypeReqDescription
amazon_urlstringyesThe amazon.com product URL exactly as the user gave it to you: copy it, do not retype or reconstruct it. Shape: https://www.amazon.com/<product-slug>/dp/<ASIN> or https://www.amazon.com/dp/<ASIN>. Th…
axesobjectStyle axes, all 0-100, omitted default to 50. Use list_axes for details.
store_idstringThe user's own Amazon Associates Store ID, if they gave it to you in this conversation (US tags end in -20). Omit it when unsure. Never guess one and never reuse a tag from an example or another conv…

No output schema declared.

No examples provided.

get_funnel_status ~31

Check the status of a funnel being generated.

NameTypeReqDescription
slugstringyesFunnel slug from the URL

No output schema declared.

No examples provided.

list_axes ~16

List available style axes for funnel generation.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the funn.to Funnel Generator MCP server?

funn.to Funnel Generator is an MCP server listed in the public MCP registry as to.funn/funnel-generator. Generate Amazon affiliate sales funnels from product URLs. AI-powered, free. This page covers its hosted endpoint (https://funn.to/mcp).

Is the funn.to Funnel Generator MCP server safe to use?

funn.to Funnel Generator scores 79 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 funn.to Funnel Generator MCP server expose?

funn.to Funnel Generator exposes 3 tools: generate_funnel, get_funnel_status, list_axes. Their descriptions and schemas cost roughly 362 tokens of context every time the server is loaded.

Does the funn.to Funnel Generator MCP server require authentication?

No. We connected to funn.to Funnel Generator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the funn.to Funnel Generator MCP server still maintained?

funn.to Funnel Generator is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.