Factline X402 Health
NPM · @PIPEWORX/MCP-FACTLINE-X402-HEALTH · 2 COMPONENTS
factline-x402-health -- x402 seller and facilitator health.
Available components
Last scanned (14 hours ago)
Scores higher than 76% of npm servers
Category Crypto and Web3
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-factline-x402-health). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +2
- 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. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 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 functional
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-factline-x402-health@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-factline-x402-health |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-factline-x402-health/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635935906 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e3ba234619da111286779100e08f0ee138888fc57965054f525b9354bfbc49293dc487ed7467e5a15675fe62953a236be1ef3e41bae37f31ac4fa18c1 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
x402_facilitator_health ~166
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).
| Name | Type | Req | Description |
|---|---|---|---|
| facilitator | string | – | Optional facilitator id (cdp, payai, dexter...), name, or URL. Omit to list all. |
No output schema declared.
No examples provided.
x402_seller_health ~260
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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") |
No output schema declared.
No examples provided.
x402_seller_lookup ~152
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).
| Name | Type | Req | Description |
|---|---|---|---|
| origin | string | yes | Seller origin, host or any URL on the seller (e.g. "api.exa.ai") |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-factline-x402-health
claude mcp add pipeworx-io-factline-x402-health -- npx -y @pipeworx/mcp-factline-x402-health
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.