# @pipeworx/factline-x402-health

Health of x402 sellers and facilitators: Factline's nightly seller probes and hourly facilitator probes, proxied live per request.

Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1864+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

## Tools

- `x402_facilitator_health(facilitator?)` -- all tracked x402 facilitators with current status (up/down/unknown), 7-day uptime, latency and supported networks, or one by id, name or URL. Refreshes hourly.
- `x402_seller_health(query?, tag?, network?, limit?)` -- x402 sellers ranked by 30-day payers, each with a health reading (healthy/degraded/unhealthy/insufficient_data/unprobed) from nightly probes. Covers the full tracked index (about 1,000 sellers today); raise `limit` past the default 25 to reach further down the ranking, or narrow with query, tag or network.
- `x402_seller_lookup(origin)` -- one seller by origin, host or URL: per-day probe history, uptime, listed payTo wallets, health reading. Use before paying a seller.

Every response carries `source`, `license`, `terms`, `cite_as`, `cadence`, `data_as_of` and `warnings`.

## Auth

Keyless. Factline offered these feeds free of charge for agent use.

## Data sources

- Factline, x402 Seller Health Index -- nightly probes of sellers listed in public x402 catalogues.
- Factline, x402 Facilitator Health -- hourly probes of x402 facilitators.

Cite as "Source: Factline (factline.dev)". Cadence: sellers nightly, facilitators hourly; `data_as_of` is the latest probe, and a `warnings` entry appears when it is older than the cadence implies.

## Reading the results

- Absence is not health. `found:false` or `count:0` means unknown or unmatched, never "fine". The pack says so in the payload.
- The seller feed lists at most 100 sellers per request with no paging (about 1,000 tracked); `coverage_note` states the cut.
- `health` and `status_now` are this pack's reading of Factline's numbers (rules in `health_basis` / `status_basis`), not Factline's own verdict. A facilitator that requires an API key is probed on `/supported` only (`verify_tested: false`).
- Seller probes check that a sample endpoint answers a valid payment challenge; no payment is made and nothing is said about the quality of what the seller sells.

## Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

```json
{
  "mcpServers": {
    "factline-x402-health": {
      "url": "https://gateway.pipeworx.io/factline-x402-health/mcp"
    }
  }
}
```

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/factline-x402-health/mcp` returns the tools in the table
above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's `initialize` response states its exact scope, and
is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
`ask_pipeworx`, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed
directly, instead of just this one's:

```json
{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}
```

Both URLs reach the same gateway and the same 1864+ data sources. The
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
reaches all of them from either one.

## No MCP client? Call it over HTTP

```bash
curl -X POST https://gateway.pipeworx.io/v1/tools/x402_facilitator_health \
  -H 'Content-Type: application/json' \
  -d '{"facilitator":"payai"}'
```

No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/x402_facilitator_health`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.

## Run it from npm

`@pipeworx/mcp-factline-x402-health` is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with `npx`, and it forwards every call to the same
`https://gateway.pipeworx.io/factline-x402-health/mcp` endpoint shown above. It needs network access;
there is no offline mode.

```json
{
  "mcpServers": {
    "factline-x402-health": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-factline-x402-health"]
    }
  }
}
```

Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
`"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.

It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
also list `ask_pipeworx` and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
your Node version's documentation.

## Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English —
this works on the pack endpoint above as well as on the full gateway:

```
ask_pipeworx({ question: "your question about Factline X402 Health data" })
```

The gateway picks the right tool and fills the arguments automatically.

## More

- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)

## License

MIT