Quietforge x402 Tools

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

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
67%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~1,699Tokens (tool definitions)
~1.2 KBTypical response size
Moderate attention impact (1.33% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://qf-api.quietforge-studio.workers.dev/mcpstreamable-http

What it can do

Tool inventory

Tools (7)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢x402_search(q, network, alive, max_price_usd, source, ...)

Use this to find a pay-per-call x402 API for a given task, network or price cap before calling it (mostly USDC on Base; check each row's network and asset, some are testnet or other assets). Searches 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 Schema

{
  "type": "object",
  "properties": {
    "q": {
      "description": "Case-insensitive substring matched against the resource URL, description and service name; omit for no text filter.",
      "title": "Q",
      "type": "string"
    },
    "network": {
      "description": "CAIP-2 network id to filter on, e.g. eip155:8453 (Base mainnet); omit for all networks.",
      "title": "Network",
      "type": "string"
    },
    "alive": {
      "description": "true = answered its paid route on our last probe; false = did not; omit for both.",
      "title": "Alive",
      "type": "boolean"
    },
    "max_price_usd": {
      "description": "Only endpoints priced at or below this USD amount per call; omit for any price.",
      "title": "Max Price Usd",
      "type": "number"
    },
    "source": {
      "description": "Listing source: cdp (Coinbase CDP bazaar), payai (PayAI discovery) or quietforge (our own endpoints); omit for all sources.",
      "title": "Source",
      "type": "string"
    },
    "limit": {
      "default": 20,
      "description": "Page size, 1-100; out-of-range values are clamped.",
      "title": "Limit",
      "type": "integer"
    },
    "offset": {
      "default": 0,
      "description": "Rows to skip for paging; negative is treated as 0.",
      "title": "Offset",
      "type": "integer"
    }
  },
  "title": "x402_searchArguments"
}

Output Schema

{
  "type": "object",
  "additionalProperties": true,
  "title": "x402_searchDictOutput"
}
🟢x402_service(id)

Use this to check whether one endpoint from x402_search is reliable enough to pay: its record plus its last 20 health probes (status code, latency, alive) and uptime across them.

Input Schema

{
  "type": "object",
  "properties": {
    "id": {
      "description": "Service id exactly as returned by x402_search.",
      "title": "Id",
      "type": "string"
    }
  },
  "required": [
    "id"
  ],
  "title": "x402_serviceArguments"
}

Output Schema

{
  "type": "object",
  "additionalProperties": true,
  "title": "x402_serviceDictOutput"
}
🟢x402_index_stats

Use this to see how much this index covers (it is a subset of the x402 market, not all of it) and to sanity-check x402_search coverage before relying on it. Summary of the index: totals, how many endpoints answered on the last probe, counts per network and per source, and when the crawl ran.

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "x402_index_statsArguments"
}

Output Schema

{
  "type": "object",
  "additionalProperties": true,
  "title": "x402_index_statsDictOutput"
}
🟢x402_demand

Use this to answer "is anyone actually paying for x402 APIs today" with settled on-chain numbers instead of listings. 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.

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "x402_demandArguments"
}

Output Schema

{
  "type": "object",
  "additionalProperties": true,
  "title": "x402_demandDictOutput"
}
🟢x402_probe(url, method)

Use this to check a URL you are about to pay (or one you operate) for a well-formed x402 challenge before sending funds; a challenge is no guarantee the service delivers. Makes ONE live unpaid request to a public http(s) URL and reports 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 Schema

{
  "type": "object",
  "properties": {
    "url": {
      "description": "Absolute http(s) URL to probe, max 2048 chars; public hosts only.",
      "title": "Url",
      "type": "string"
    },
    "method": {
      "default": "GET",
      "description": "HTTP method. GET unless the URL is already in the index with a different listed method (then that method is allowed).",
      "title": "Method",
      "type": "string"
    }
  },
  "required": [
    "url"
  ],
  "title": "x402_probeArguments"
}

Output Schema

{
  "type": "object",
  "additionalProperties": true,
  "title": "x402_probeDictOutput"
}
🟢sudoku_puzzle(level, seed)

Use this when a user wants a sudoku to play or print, or an app needs a verified puzzle at a named difficulty. Generates 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 Schema

{
  "type": "object",
  "properties": {
    "level": {
      "default": "medium",
      "description": "Difficulty by solving technique: easy, medium, hard or expert.",
      "title": "Level",
      "type": "string"
    },
    "seed": {
      "description": "Integer 1-2147483647 for a reproducible puzzle; omit for a random one.",
      "title": "Seed",
      "type": "integer"
    }
  },
  "title": "sudoku_puzzleArguments"
}

Output Schema

{
  "type": "object",
  "additionalProperties": true,
  "title": "sudoku_puzzleDictOutput"
}
🟢quietforge_pricing

Price-check Quietforge's paid x402 HTTP routes before paying (free read-only list, not tools here): convert docx, xlsx, pptx, csv to pdf; PDF text; URL/HTML to PNG; sudoku books; manuscript typesetting; crosswords; family trees from GEDCOM; dataset quality audits; x402 index API. USD prices, pay-to address, how an x402 client pays.

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "quietforge_pricingArguments"
}

Output Schema

{
  "type": "object",
  "additionalProperties": true,
  "title": "quietforge_pricingDictOutput"
}

Recommended Prompts

search_research
Search for information about [topic] using Quietforge x402 Tools
Expected tools: x402_search
find_specific
Find [specific item] using Quietforge x402 Tools
Expected tools: x402_search

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded7 tools
verifiedversion not recorded7 tools
verifiedversion not recorded7 tools
verifiedversion not recorded7 tools
verifiedversion not recorded7 tools
verifiedversion not recorded6 tools