Agent Tools
List
Back to directory

Massachusetts Code

https://gateway.pipeworx.io/massachusetts-code/mcp
● healthy model-context-protocol-mcp

Massachusetts General Laws — state statutes by citation.

Category
model-context-protocol-mcp
Chains
base
Price
$0.0100 USDC / call

Quality grade

How grading works
B 66.1 / 100
Availability 40.0 / 40
Endpoint responded (HTTP 200)
Payability 20.0 / 20
  • ✓ Answers a real HTTP 402 challenge
  • ✓ Publishes a /.well-known/x402 descriptor
  • ✓ Payment address on record
  • ✓ Settlement network declared
  • ✓ Price declared
Demand 6.1 / 40
1 distinct payers, 10 USDC transfers in the last 30 days
Owner verified 0.0 / 3
Nobody has claimed this listing yet
Endpoint last checked 6 h ago. On-chain activity last read 2 d 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

C · 75/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, 66.1/100), which weighs availability, payability and on-chain demand. How the two differ

Valid payment requirements 10/10 Payment requirements carry a payee, a mainnet network and a price.
Live 402 challenge 20/25 Endpoint reachable; its 402 challenge was seen earlier (61 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 5/10 Declares 1 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 (61 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. Display only: search order uses the quality grade.

Compared with peers

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

Readiness
Higher than 30% of peers
This listing 75 · peer median 78
Latency
Faster than 97% of peers
This listing 61 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 (61 ms).
  • Resource declaration −5 — Declare each paid resource with its input and output schema.
    Now: Declares 1 paid resource(s).
  • 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.

How many agent tools actually work · All statistics

How to call

cURL · x402-fetch / x402-axios will auto-handle 402
curl -sS -i -X GET https://gateway.pipeworx.io/massachusetts-code/mcp  # expect HTTP 402 Payment Required (about 0.01 USDC/call)
MCP endpoint
https://gateway.pipeworx.io/massachusetts-code/mcp
/.well-known/x402.json
https://gateway.pipeworx.io/.well-known/x402

Listed in

Directories this entry was found in.

mcp since 2026-09-15