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.

x402 Forge

REMOTE · FORGE.FIZZL.EU

Tool shop for AI agents: ready x402 tools to call or own, or order one built for $1. Free tries.

Available components

67 Trust /100

Last scanned (19 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

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 Security63
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 954 tokens (~106/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 79% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "revise_order" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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 →

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1
    • Tool “buy_product” rewrote its description, which is the text the model reads security
    • Tool “search_products” rewrote its description, which is the text the model reads security
    • Tool “try_product” rewrote its description, which is the text the model reads security
    • Schema quality: 92 → 106 ▼ functional
    • New tool “call_tool” functional
  • 18 Nov 26 +1

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

  • 17 Nov 26 +2
    • HSTS header: fail → pass ▲ security
    • Tool “try_product” rewrote its description, which is the text the model reads security
  • 16 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 26 61

    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 21 Nov 2026 · Probed https://forge.fizzl.eu/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=forge.fizzl.eu CN=YE1,O=Let's Encrypt,C=US 14 Nov 2026 12 Feb 2027 ECDSA 256 ECDSA-SHA384 52cc0d909df5757979936a683c648c45ca2
SANs: forge.fizzl.eu
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 forge.fizzl.eu. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
eu. DS published 35926 8 Verified
fizzl.eu. 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=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'sha256-ww+TdwEdJLBiuFnYBT0Pn+YQ2th1b32RFhR3+8OpiJE='; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob:; connect-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://forge.fizzl.eu/mcp Verified 200
http (plaintext) http://forge.fizzl.eu/mcp HTTPS enforced 301 https://forge.fizzl.eu/mcp
MCP tools · 9 exposed · ~954 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
buy_product ~154

Get everything needed to buy one tool from x402 Forge: the x402 URL your wallet pays, the price, and what you receive. Each tool is sold once, to one owner: you get a small x402 server with the tool, Forge stops selling it, and your copy is listed under your wallet. This call itself is free and does not pay; pay the returned buy_url with an x402 client (for example an x402 fetch or payment tool, or the Fizzl Agent Wallet). To use a tool per call instead of owning it, use call_tool.

NameTypeReqDescription
formatstring–zip (default) or json files
slugstringyesThe tool's slug, from search_products

No output schema declared.

No examples provided.

call_tool ~185

Run an x402 Forge tool on your own input and get its answer ({ok, result, warnings}) plus a signed receipt. Paid per call with x402 inside this MCP call: without a payment the result is the payment terms (x402Version, accepts: the tool's own price in USDC, network and payee, the same as GET /p/{slug}); an x402 MCP client signs one and calls again with it in _meta["x402/payment"]. Never charged for an error: an unknown or sold tool and invalid input are refused before any price, and a failed run is not settled. Free first: try_product runs the example; describe_product shows the input schema.

NameTypeReqDescription
inputobjectyesThe tool's parameters as one JSON object (describe_product shows its input schema)
slugstringyesThe tool's slug, from search_products

No output schema declared.

No examples provided.

describe_product ~35

Full details of one product: input and output schema, examples, price, network and quality record.

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

order_product ~56

How to have x402 Forge build a tool for you: describe it in one sentence, pay $1.00 with x402, and send it back with revise_order if something is missing. Does not place or pay for an order.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

report_problem ~140

Bought a tool (alone or in a bundle) and something is wrong with it? Send the slug, your purchase receipt (the X-Forge-Receipt token) and one sentence about the fault. Free. Forge's agents pick it up within the hour; a real fault is fixed, passes the same checks, and you download the new version free at /forge/packages/{slug}/update with your receipt. No money back through this tool.

NameTypeReqDescription
problemstringyesWhat is wrong, one sentence, 10-300 characters
receiptstringyesThe X-Forge-Receipt token from your purchase
slugstringyes–

No output schema declared.

No examples provided.

revise_order ~154

Send a tool you ordered from x402 Forge back with one sentence about what is missing or should change. Free. Needs the revision_key from your order. We pick it up within the hour: a small change is rebuilt for free; a bigger one gets a price ($1-$5) shown on the order with a pay_url to pay with x402 before the rebuild. An independent judge agent must accept the new version before it replaces the live one. Up to 3 times per order.

NameTypeReqDescription
order_idstringyesord_...
requeststringyesWhat is missing or should change, 10-400 characters
revision_keystringyesrk_... from the order's 201 answer

No output schema declared.

No examples provided.

search_products ~66

Search the x402 Forge tool shop by keywords. Returns each tool's slug, the buyer's question it answers, a plain summary, whether it is still for sale, and its buy URL.

NameTypeReqDescription
querystringyesKeywords, e.g. 'iban' or 'working days'

No output schema declared.

No examples provided.

suggest_tool ~87

Missing a tool? Say in one sentence what it should do (what goes in, what comes out). Free, no wallet. Forge's agents read every suggestion and build the useful ones in the next shift; they show up in search_products when live. Nothing is promised and nothing is charged.

NameTypeReqDescription
wishstringyesOne sentence, 10-300 characters: the tool you need

No output schema declared.

No examples provided.

try_product ~77

Run a product on its built-in example input, free of charge. The answer also shows how to use it on your own input (call_tool here in MCP, or the x402 URL, at the per-call price) and how to own it (the package and its kit bundle, when for sale).

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

Install

How do I install the x402 Forge MCP server?

x402 Forge is a hosted endpoint at https://forge.fizzl.eu/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 · forge.fizzl.eu

# add to Claude Code
claude mcp add --transport http fizzl13-x402-forge 'https://forge.fizzl.eu/mcp'
Common questions

What is the x402 Forge MCP server?

x402 Forge is an MCP server listed in the public MCP registry as io.github.Fizzl13/x402-forge. Tool shop for AI agents: ready x402 tools to call or own, or order one built for $1. Free tries. This page covers its hosted endpoint (https://forge.fizzl.eu/mcp).

Is the x402 Forge MCP server safe to use?

x402 Forge scores 67 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 x402 Forge MCP server expose?

x402 Forge exposes 9 tools: search_products, report_problem, suggest_tool, describe_product, try_product, and 4 more. Their descriptions and schemas cost roughly 954 tokens of context every time the server is loaded.

Does the x402 Forge MCP server require authentication?

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

Is the x402 Forge MCP server still maintained?

x402 Forge 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 x402 Forge MCP server?

VerifyMCP ran 12 checks on x402 Forge, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about x402 Forge: Authorization. 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.