# 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.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `forge.fizzl.eu`: 67/100 (this document), [markdown](https://verifymcp.io/servers/fizzl13-x402-forge/forge.md), [page](https://verifymcp.io/servers/fizzl13-x402-forge/forge)

## Channel facts

- Endpoint: `https://forge.fizzl.eu/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 954 tokens (~106/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 79% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http fizzl13-x402-forge 'https://forge.fizzl.eu/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "fizzl13-x402-forge": {
      "url": "https://forge.fizzl.eu/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fizzl13-x402-forge": {
      "type": "http",
      "url": "https://forge.fizzl.eu/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fizzl13-x402-forge]
url = "https://forge.fizzl.eu/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fizzl13-x402-forge": {
      "type": "remote",
      "url": "https://forge.fizzl.eu/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fizzl13-x402-forge --url 'https://forge.fizzl.eu/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fizzl13-x402-forge:
    url: "https://forge.fizzl.eu/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fizzl13-x402-forge": {
      "Transport": "http",
      "Url": "https://forge.fizzl.eu/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fizzl13-x402-forge -t streamable-http -u 'https://forge.fizzl.eu/mcp'
```

### Other

```json
{
  "mcpServers": {
    "fizzl13-x402-forge": {
      "type": "http",
      "url": "https://forge.fizzl.eu/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 67, +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.

### 2026-11-19 (score 66, +1)

- [security] 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
- [functional regression] Schema quality: 92 → 106
- [functional] New tool “call_tool”

### 2026-11-18 (score 65, +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.

### 2026-11-17 (score 64, +2)

- [security improvement] HSTS header: fail → pass
- [security] Tool “try_product” rewrote its description, which is the text the model reads

### 2026-11-16 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-15 (score 61)

First indexed and scored.

## MCP tools (9)

### `search_products` (~66 tokens)

Search products

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.

Input parameters:

- `query` (string, required): Keywords, e.g. 'iban' or 'working days'

### `report_problem` (~140 tokens)

Report a problem with a tool you bought

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.

Input parameters:

- `problem` (string, required): What is wrong, one sentence, 10-300 characters
- `receipt` (string, required): The X-Forge-Receipt token from your purchase
- `slug` (string, required)

### `suggest_tool` (~87 tokens)

Suggest a tool

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.

Input parameters:

- `wish` (string, required): One sentence, 10-300 characters: the tool you need

### `describe_product` (~35 tokens)

Describe product

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

Input parameters:

- `slug` (string, required)

### `try_product` (~77 tokens)

Try product for free

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).

Input parameters:

- `slug` (string, required)

### `call_tool` (~185 tokens)

Call a tool (paid per call via x402)

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.

Input parameters:

- `input` (object, required): The tool's parameters as one JSON object (describe_product shows its input schema)
- `slug` (string, required): The tool's slug, from search_products

### `buy_product` (~154 tokens)

Buy a tool (exclusive)

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.

Input parameters:

- `format` (string): zip (default) or json files
- `slug` (string, required): The tool's slug, from search_products

### `order_product` (~56 tokens)

Order a tool in one sentence

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.

### `revise_order` (~154 tokens)

Send an ordered tool back

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.

Input parameters:

- `order_id` (string, required): ord_...
- `request` (string, required): What is missing or should change, 10-400 characters
- `revision_key` (string, required): rk_... from the order's 201 answer

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/fizzl13-x402-forge/forge#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 66
- 2026-11-19: 66
- 2026-11-18: 65
- 2026-11-17: 64
- 2026-11-16: 62
- 2026-11-15: 61

## 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.

## Links

- Remote endpoint: https://forge.fizzl.eu/mcp
- Website: https://forge.fizzl.eu/
- Changelog RSS feed: https://verifymcp.io/servers/fizzl13-x402-forge/forge.xml
- Changelog JSON feed: https://verifymcp.io/servers/fizzl13-x402-forge/forge/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/fizzl13-x402-forge/forge.json
- HTML version of this page: https://verifymcp.io/servers/fizzl13-x402-forge/forge
