MCP server for minia2a.uk — discover and call 1,600+ x402 pay-per-call APIs with USDC payments.
Nothing to run from here
Factline X402 Health is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
100/100
trust score
44
downloads a day
local
or remote
799
downloads in 30d
What it does
factline-x402-health -- x402 seller and facilitator health.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user factline-x402-health-mcp '--' npx -y @pipeworx/mcp-factline-x402-health
# 2 — ask your agent for something these tools do
# x402_facilitator_health, x402_seller_health, x402_seller_lookup
Factline X402 Health costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PIAll 1913 servers
pipeworx-io1913 servers
29 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user factline-x402-health-mcp '--' npx -y @pipeworx/mcp-factline-x402-healthReconnect, or start a new session, and the tools appear in the model’s tool list.
Or connect to its publisher’s address
Its publisher also runs it at https://gateway.pipeworx.io/factline-x402-health/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http factline-x402-health-mcp https://gateway.pipeworx.io/factline-x402-health/mcpFree on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take PIPEWORX_API_KEY (Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.) if you want to set it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
3 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| facilitator | string | no | Optional facilitator id (cdp, payai, dexter...), name, or URL. Omit to list all. |
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 ~1,000 sellers from public x402 catalogues but each call returns at most 100, ranked by 30-day unique payers: use "query", "tag" or "network"…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Free text matched against seller name/host/tags (e.g. "sanctions", "exa") |
| tag | string | no | Seller tag filter (e.g. "search", "llm") |
| network | string | no | Network filter (e.g. "base", "solana") |
| limit | number | no | Max sellers to return, 1-100 (default 25) |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| origin | string | yes | Seller origin, host or any URL on the seller (e.g. "api.exa.ai") |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Factline X402 Health or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 100 / 100
Release 0.2.1 · scanned 2 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest24f051a6c5422b073a639867309ab9c35f11c5393dc49d361a69890507fb0a19
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest24f051a6c5422b07
Scanned2026-11-02
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.1. Pin a release below and the command asks for exactly that one.
0.2.1
1 Nov 2026
latestNo release note was published with this version.
0.2.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Factline X402 Health can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.