payg mcp registry risk derived
api.relayshield.netMarket dataderived
POST https://api.relayshield.net/v1/payg/mcp-registry-risk
passlisted in Coinbasecounted above 76% of Market data
0.35 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 5
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-08-30 19:34 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.35 USDC
- Networks
- 2
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 28 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
api.relayshield.net serves payg mcp registry risk, a POST endpoint that TOLL places in market data, listed in the Coinbase registry.
On Base, payg mcp registry risk asks 0.35 USDC per call.
The request to payg mcp registry risk is a json body with the field server_url.
payg mcp registry risk accepts payment on Base and Solana, 2 options in all, to 2 different wallets.
A response from payg mcp registry risk, as declared, includes ok and data.
The daily sweep got a valid payment challenge from payg mcp registry risk on 2026-09-15, as at every sweep since 2026-09-11.
payg mcp registry risk is the only listed endpoint on api.relayshield.net.
One payer accounts for all 5 calls to payg mcp registry risk over 30 days.
payg mcp registry risk was last called 16 days before the snapshot.
Closest in price to payg mcp registry risk within market data: distribution balance exchanges relative at x402.glassnode.com and smart money netflow at api.nansen.ai.
payg mcp registry risk is near the top of prices in market data; 97% of comparable listings are cheaper.
payg mcp registry risk out-counts 76% of the 5,172 endpoints in market data that carry counters.
The payee wallet of payg mcp registry risk appears on no other listing.
the payment options, as of 2026-09-15 16:57 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.35 USDC | exact | 0x002CfD…412bAc |
| Coinbase | solana: | USDC | 0.35 USDC | exact | E64PiTT7…Vqp7M6 |
the checks, as of 2026-09-15 07:08 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-15 07:08 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 06:34 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 06:23 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 13:56 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 14:53 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-08-30 19:34 UTC · method · live
The input and output block
{
"input": {
"body": {
"server_url": "https://example-mcp-server.com"
},
"type": "http",
"method": "POST",
"bodyType": "json",
"discoverable": true
},
"output": {
"type": "json",
"example": {
"ok": true,
"data": {
"verdict": "LOW",
"findings": []
}
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-15 16:57 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "payg mcp registry risk on api.relayshield.net", snapshot of 2026-09-15 16:57 UTC. https://tollindex.com/e/api-relayshield-net-v1-payg-mcp-registry-risk-fcab5f/at/2026-09-15T16-57Z. Accessed [access date].
BibTeX
@misc{toll-e-api-relayshield-net-v1-payg-mcp-registry-risk-fcab5f-2026-09-15T16-57Z,
author = {TOLL},
title = {payg mcp registry risk on api.relayshield.net},
howpublished = {\url{https://tollindex.com/e/api-relayshield-net-v1-payg-mcp-registry-risk-fcab5f/at/2026-09-15T16-57Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-15 16:57 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.