# Factline X402 Health (npm · @pipeworx/mcp-factline-x402-health)

factline-x402-health -- x402 seller and facilitator health.

- Trust score: 83/100 (high trust)
- Change this week: +19
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 76/100, [markdown](https://verifymcp.io/servers/pipeworx-io-factline-x402-health/factline-x402-health-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-factline-x402-health/factline-x402-health-mcp)
- npm · `@pipeworx/mcp-factline-x402-health`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-factline-x402-health/pipeworx-mcp-factline-x402-health.md), [page](https://verifymcp.io/servers/pipeworx-io-factline-x402-health/pipeworx-mcp-factline-x402-health)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-factline-x402-health`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-factline-x402-health).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 637 tokens (~212/item across 3 items; 3 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Factline X402 Health MCP server?

Factline X402 Health runs locally as an npm package, launched with npx -y @pipeworx/mcp-factline-x402-health. 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 pipeworx-io-factline-x402-health -- npx -y @pipeworx/mcp-factline-x402-health
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-factline-x402-health -- npx -y @pipeworx/mcp-factline-x402-health
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-factline-x402-health": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-factline-x402-health"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-factline-x402-health --command npx --arg -y --arg @pipeworx/mcp-factline-x402-health
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-factline-x402-health:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-factline-x402-health"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-factline-x402-health": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-factline-x402-health"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-factline-x402-health -t stdio -c npx -a -y @pipeworx/mcp-factline-x402-health
```

### Other

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

## 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-05 (score 83, +1)

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

### 2026-11-03 (score 82, +1)

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

### 2026-11-01 (score 81, +2)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] First check of Schema quality: unverified
- [functional] Schema quality: good → excellent
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 79, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-29 (score 64)

First indexed and scored.

## MCP tools (3)

### `x402_facilitator_health` (~166 tokens)

Health of x402 payment facilitators from Factline's hourly probes (no money moves): current status (up/down/unknown), 7-day uptime, latency, networks supported. Omit "facilitator" to list all tracked facilitators (about a dozen); pass an id (e.g. "cdp", "payai"), name, or facilitator URL to look one up. A facilitator that is not in the feed returns found:false with the tracked ids; absence is NOT evidence of health. Every response carries source, data_as_of (latest probe time) and warnings (stale or empty feed).

Input parameters:

- `facilitator` (string): Optional facilitator id (cdp, payai, dexter...), name, or URL. Omit to list all.

### `x402_seller_health` (~260 tokens)

Rank/search x402 sellers with a health reading from Factline's nightly probes (does a sample endpoint still answer a valid x402 payment challenge). Covers the FULL tracked index (about 1,000 sellers from public x402 catalogues, ranked by 30-day unique payers) -- raise "limit" past the default 25 to reach further down the ranking, or narrow with "query", "tag" or "network". An empty result (count:0) means the filter matched nothing among the tracked sellers; it is NOT evidence that anything is healthy. To check one specific seller use x402_seller_lookup. Returns source, license, data_as_of, origins_tracked and warnings.

Input parameters:

- `limit` (number): Max sellers to return, 1-1200 (default 25). The tracked index is under 1,100 sellers today, so a high limit reaches all of them.
- `network` (string): Network filter (e.g. "base", "solana")
- `query` (string): Free text matched against seller name/host/tags (e.g. "sanctions", "exa")
- `tag` (string): Seller tag filter (e.g. "search", "llm")

### `x402_seller_lookup` (~152 tokens)

Look up ONE x402 seller by origin, host or URL (e.g. "api.exa.ai" or "https://stableenrich.dev") and get Factline's nightly probe history (per-day ok/latency), uptime, listed payTo wallets, and a health reading. Check this before paying a seller. A seller Factline does not track returns found:false ("not tracked yet"), which means UNKNOWN, not healthy and not unhealthy. Returns source and data_as_of (date of the latest probe; null with retrieved_at when the seller is not tracked).

Input parameters:

- `origin` (string, required): Seller origin, host or any URL on the seller (e.g. "api.exa.ai")

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-factline-x402-health/pipeworx-mcp-factline-x402-health#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 64

## Common questions

### What is the Factline X402 Health MCP server?

Factline X402 Health is an MCP server listed in the public MCP registry as io.github.pipeworx-io/factline-x402-health. factline-x402-health -- x402 seller and facilitator health. This page covers its npm package (@pipeworx/mcp-factline-x402-health).

### Is the Factline X402 Health MCP server safe to use?

Factline X402 Health scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Factline X402 Health MCP server expose?

Factline X402 Health exposes 3 tools: x402_facilitator_health, x402_seller_health, x402_seller_lookup. Their descriptions and schemas cost roughly 578 tokens of context every time the server is loaded.

### Is the Factline X402 Health MCP server still maintained?

Factline X402 Health is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Factline X402 Health MCP server under?

Factline X402 Health declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-factline-x402-health
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-factline-x402-health
- Repository: https://github.com/pipeworx-io/mcp-factline-x402-health
- Website: https://pipeworx.io/packs/factline-x402-health
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-factline-x402-health/pipeworx-mcp-factline-x402-health.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-factline-x402-health/pipeworx-mcp-factline-x402-health.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-factline-x402-health/pipeworx-mcp-factline-x402-health