# Quietforge x402 Tools (remote · qf-api.quietforge-studio.workers.dev)

Free tools: x402 endpoint directory + probe, on-chain x402 demand signal, sudoku, API pricing.

- Trust score: 69/100 (medium)
- Change this week: +11
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `qf-api.quietforge-studio.workers.dev`: 69/100 (this document), [markdown](https://verifymcp.io/servers/quietforgestudio-x402-tools/qf-api.md), [page](https://verifymcp.io/servers/quietforgestudio-x402-tools/qf-api)

## Channel facts

- Endpoint: `https://qf-api.quietforge-studio.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.1`

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

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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 (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1155 tokens (~165/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Quietforge x402 Tools MCP server?

Quietforge x402 Tools is a hosted endpoint at https://qf-api.quietforge-studio.workers.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.

### Claude

```bash
claude mcp add --transport http quietforgestudio-x402-tools 'https://qf-api.quietforge-studio.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "quietforgestudio-x402-tools": {
      "url": "https://qf-api.quietforge-studio.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "quietforgestudio-x402-tools": {
      "type": "http",
      "url": "https://qf-api.quietforge-studio.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.quietforgestudio-x402-tools]
url = "https://qf-api.quietforge-studio.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "quietforgestudio-x402-tools": {
      "type": "remote",
      "url": "https://qf-api.quietforge-studio.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add quietforgestudio-x402-tools --url 'https://qf-api.quietforge-studio.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  quietforgestudio-x402-tools:
    url: "https://qf-api.quietforge-studio.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "quietforgestudio-x402-tools": {
      "Transport": "http",
      "Url": "https://qf-api.quietforge-studio.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add quietforgestudio-x402-tools -t streamable-http -u 'https://qf-api.quietforge-studio.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "quietforgestudio-x402-tools": {
      "type": "http",
      "url": "https://qf-api.quietforge-studio.workers.dev/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-09-28 (score 69, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 69, +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-09-25 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 67, 0)

- [security regression] HTTPS: unverified → fail

### 2026-09-23 (score 67, +10)

- [security improvement] Authorization: unverified → partial
- [security] Tool “x402_demand” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 134 → 165
- [functional improvement] Tool coverage: 0% → 100%
- [functional] Schema quality: good → excellent
- [functional] Server version: 1.2.0 → 1.2.1
- [cosmetic] “sudoku_puzzle” reworded the description of “level”
- [cosmetic] “sudoku_puzzle” reworded the description of “seed”
- [cosmetic] “x402_probe” reworded the description of “method”
- [cosmetic] “x402_probe” reworded the description of “url”
- [cosmetic] “x402_search” reworded the description of “alive”
- [cosmetic] “x402_search” reworded the description of “limit”
- [cosmetic] “x402_search” reworded the description of “max_price_usd”
- [cosmetic] “x402_search” reworded the description of “network”
- [cosmetic] “x402_search” reworded the description of “offset”
- [cosmetic] “x402_search” reworded the description of “q”
- [cosmetic] “x402_search” reworded the description of “source”
- [cosmetic] “x402_service” reworded the description of “id”
- [cosmetic] Tool “quietforge_pricing” changed its title: Quietforge paid x402 routes and prices
- [cosmetic] Tool “sudoku_puzzle” changed its title: Generate one solver-verified sudoku
- [cosmetic] Tool “x402_demand” changed its title: x402 market demand, on-chain, last 24h
- [cosmetic] Tool “x402_index_stats” changed its title: x402 directory size and breakdown
- [cosmetic] Tool “x402_probe” changed its title: Probe one URL for an x402 payment challenge
- [cosmetic] Tool “x402_search” changed its title: Search the x402 endpoint directory
- [cosmetic] Tool “x402_service” changed its title: Get one x402 endpoint with probe history

### 2026-09-22 (score 57, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “x402_search” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [functional] Server version: 1.1.0 → 1.2.0
- [functional] Server version: 1.0.2 → 1.1.0
- [functional] Server version: 1.0.1 → 1.0.2
- [functional] New tool “x402_demand”

### 2026-09-21 (score 58)

First indexed and scored.

## MCP tools (7)

### `x402_search` (~302 tokens)

Search the x402 endpoint directory

Search a health-probed directory of live x402 pay-per-call HTTP endpoints on Base, Solana and other networks (x402_index_stats gives the current count). Returns id, resource URL, method, network, USD price, description, 30-day call/payer counts and our own uptime/probe data. Data is re-crawled a few times a day, not real-time. Quietforge operates this directory and also operates some listed endpoints (source=quietforge) under the same per-host cap as every operator; ordering is by 30-day usage, then liveness, then freshness, never by operator.

Input parameters:

- `alive`: true = answered its paid route on our last probe; false = did not; omit for both.
- `limit` (integer): Page size, 1-100; out-of-range values are clamped.
- `max_price_usd`: Only endpoints priced at or below this USD amount per call.
- `network`: CAIP-2 network id to filter on, e.g. eip155:8453 (Base mainnet); omit for all networks.
- `offset` (integer): Rows to skip for paging; negative is treated as 0.
- `q`: Case-insensitive substring matched against the resource URL, description and service name.
- `source`: Listing source: cdp (Coinbase CDP bazaar), payai (PayAI discovery) or quietforge (our own endpoints).

### `x402_service` (~61 tokens)

Get one x402 endpoint with probe history

One endpoint from the x402 service index by id (from x402_search), with its last 20 health probes (status code, latency, alive) and uptime across them.

Input parameters:

- `id` (string, required): Service id exactly as returned by x402_search.

### `x402_index_stats` (~42 tokens)

x402 directory size and breakdown

Summary of the x402 service index: totals, how many endpoints answered on the last probe, counts per network and per source, and when the crawl ran.

### `x402_demand` (~127 tokens)

x402 market demand, on-chain, last 24h

Market-level demand signal for the x402 ecosystem, verified against on-chain USDC settlement on Base rather than self-reported call counts: how many seller addresses were paid in the last 24h, total USD settled, and the distribution of sellers by payment count. Free and aggregate-only; the per-seller breakdown (distinct payers per address; payer counts include sampler/grader wallets that pay many sellers once, so read them as an upper bound on customers) is the paid GET /v1/x402/demand route. Refuses to answer rather than serve a stale snapshot.

### `x402_probe` (~165 tokens)

Probe one URL for an x402 payment challenge

Make ONE live unpaid request to a public http(s) URL and report whether it is an x402 endpoint: status code, latency, alive flag, whether a PAYMENT-REQUIRED challenge came back and the parsed USD price. GET only, except that a URL already in the index is probed with its listed method. Public hosts only (redirects re-checked), delisted hosts never contacted, results cached 60 s, 3 probes per host per 5 min and 30 per minute overall.

Input parameters:

- `method` (string): HTTP method. GET unless the URL is already in the index with a different listed method (then that method is allowed).
- `url` (string, required): Absolute http(s) URL to probe, max 2048 chars; public hosts only.

### `sudoku_puzzle` (~124 tokens)

Generate one solver-verified sudoku

Generate ONE sudoku puzzle with a unique solution, 180-degree symmetry, graded by the solving techniques it needs (easy | medium | hard | expert). Returns 81-char puzzle and solution strings (row by row, 0 = empty), given count and technique list. Deterministic when a seed is supplied. 20 per minute shared by all clients.

Input parameters:

- `level` (string): Difficulty by solving technique: easy, medium, hard or expert.
- `seed`: Integer 1-2147483647 for a reproducible puzzle; omit for a random one.

### `quietforge_pricing` (~74 tokens)

Quietforge paid x402 routes and prices

List Quietforge's paid x402 routes (document conversion, PDF text extraction, URL/HTML → PNG/JPEG/PDF rendering, sudoku books, manuscript typesetting, x402 index JSON API) with USD prices, the pay-to address and network, and how an x402 client pays. Free, read-only.

## Diagnostics

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

## Score history

- 2026-09-28: 69
- 2026-09-27: 69
- 2026-09-26: 68
- 2026-09-25: 68
- 2026-09-24: 67
- 2026-09-23: 67
- 2026-09-22: 57
- 2026-09-21: 58

## Common questions

### What is the Quietforge x402 Tools MCP server?

Quietforge x402 Tools is an MCP server listed in the public MCP registry as io.github.quietforgestudio/x402-tools. Free tools: x402 endpoint directory + probe, on-chain x402 demand signal, sudoku, API pricing. This page covers its hosted endpoint (https://qf-api.quietforge-studio.workers.dev/mcp).

### Is the Quietforge x402 Tools MCP server safe to use?

Quietforge x402 Tools scores 69 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 Quietforge x402 Tools MCP server expose?

Quietforge x402 Tools exposes 7 tools: x402_search, x402_service, x402_index_stats, x402_demand, x402_probe, and 2 more. Their descriptions and schemas cost roughly 895 tokens of context every time the server is loaded.

### Does the Quietforge x402 Tools MCP server require authentication?

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

### Is the Quietforge x402 Tools MCP server still maintained?

Quietforge x402 Tools is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://qf-api.quietforge-studio.workers.dev/mcp
- Website: https://quietforge-studio.pages.dev/docs-api/
- Changelog RSS feed: https://verifymcp.io/servers/quietforgestudio-x402-tools/qf-api.xml
- Changelog JSON feed: https://verifymcp.io/servers/quietforgestudio-x402-tools/qf-api.json
- HTML version of this page: https://verifymcp.io/servers/quietforgestudio-x402-tools/qf-api