Back to directory

bsv.cx

https://bsv.cx/mcp
● healthy model-context-protocol-mcp

Timestamp and verify evidence on-chain. Prove what your agent saw and when; verifying is free.

Category
model-context-protocol-mcp
Chains
—
Price
—

Quality grade

How grading works
B 55.9 / 100
Availability 20.0 / 20
Endpoint responded (HTTP 200)
Payability 14.0 / 15
  • ✓ Answers a real HTTP 402 challenge
  • ✓ Publishes a /.well-known/x402 descriptor
  • ✓ Payment address on record
  • ✓ Settlement network declared
  • ✗ Price declared
Demand 0.0 / 35
Payment address on record, not yet queried on-chain
Performance 9.9 / 10
Last probe answered in 220 ms (full marks at 200 ms or less)
Readiness 12.0 / 15
Agent readiness 80/100
Owner verified 0.0 / 5
Nobody has claimed this listing yet
Endpoint last checked 18 h ago. Availability and on-chain demand are both re-probed daily; the grade updates automatically on the next pass. This grade sets search order and leaderboards; the readiness score below is shown for reference only.

x402 readiness

B · 80/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 55.9/100), which weighs availability, payability and on-chain demand. How the two differ

Valid payment requirements 9/10 Findings: missing: price declared.
  • missing: price declared
Live 402 challenge 20/25 Endpoint reachable; its 402 challenge was seen earlier (220 ms).
x402 version n/a x402 version not observed yet.
Signed descriptor n/a No x402 standard defines a signed descriptor.
Uptime (30 days) 15/15 32/32 probes succeeded over 30 days (100%).
Resource declaration 10/10 Declares 6 paid resource(s).
Verified identity 5/10 Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
Freshness + modern flags 1/5 not seen in a source for over 30 days; declares x402.
Security declaration n/a Payment is the access control for an x402 resource.
Applicable criteria total 75 points, scaled to 100.
Responsiveness: Responsive (220 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Payment evidence: x402_challenge — We sent a request and got a live HTTP 402 challenge. Also: x402_manifest. Qualifies the payment claim; adds no points.
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily probe of the paid endpoint, its payment requirements and 30-day probe history. Signed descriptor and security declaration are n/a for x402 (payment is the access control), as is an x402 version we have not observed; the remaining points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. It also feeds 15 points of the x402 quality grade.

Compared with peers

Against 10,082 reachable x402 APIs in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 55% of peers
This listing 80 · peer median 78
Latency
Faster than 47% of peers
This listing 220 ms · peer median 205 ms

Where it loses the most points, and how to win them back

  • Live 402 challenge −5 — Answer the paid path with a valid 402 challenge.
    Now: Endpoint reachable; its 402 challenge was seen earlier (220 ms).
  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
  • Freshness + modern flags −4 — Keep the listing current in the registry or source it comes from.
    Now: not seen in a source for over 30 days; declares x402.

How many agent tools actually work · All statistics

Paid endpoints

6 resource(s) advertised by this origin. Each price below is that resource's own x402 price; the headline price is the range across them.

GET https://bsv.cx/pay/hello

demo endpoint — no marginal cost

GET https://bsv.cx/pay/time

demo endpoint — no marginal cost

GET https://bsv.cx/pay/proofpack/:txid

proof pack — a freshly SPV-verified BEEF + BUMP + tip attestation for a txid, in one call

POST https://bsv.cx/f

verifiable fetch — headless render + on-chain receipt per call

POST https://bsv.cx/shot

notarized capture — PNG or PDF of a page with the exact bytes anchored on-chain

POST https://bsv.cx/n/batch

batched timestamps — one Merkle root anchored on-chain for up to 3000 hashes

How to call

cURL · x402-fetch / x402-axios will auto-handle 402
curl -sS -i -X GET https://bsv.cx/mcp  # expect HTTP 402 Payment Required (price advertised in the 402 response)
MCP endpoint
https://bsv.cx/mcp
/.well-known/x402.json
https://bsv.cx/.well-known/x402

Listed in

Directories this entry was found in.

mcp since 2026-07-25