phone-intel-mcp.fly.dev
● Live- Price
- $0.03
- Asked in its payment challenge
- Chain
- Base
- Paid in
- USDC
- Live
- 2 of 2 checks
Endpoint
GEThttps: //phone-intel-mcp.fly.dev /lookup /{phone}
$0.03 asked in its payment challenge on 17 Nov 2026
- phonepath, required+15165551234US phone number, URL-encoded E.164 preferred (+15165551234). Dashed and parenthesized formats are normalized server-side.
curl -i 'https://phone-intel-mcp.fly.dev/lookup/%2B15165551234'
Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/phone-intel-mcp.fly.dev
Recent checks
16 Nov 2026Taller is slower; grey is not live.17 Nov 2026
- Median response
- 50 ms
- Last checked
- 17 Nov, 15:23 UTC
Our probes look for a payment challenge. They don't test payment or delivery.
All 2 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 17 Nov, 15:23 UTC | Live | 402 | 61ms |
| 16 Nov, 00:22 UTC | Live | 402 | 38ms |
Questions
Did our last probe detect a payment challenge?
At our last probe on 17 Nov, 15:23 UTC, it returned HTTP 402 or another detected payment-challenge signal.
What payment terms does phone-intel-mcp.fly.dev advertise?
The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.
Something wrong on this page? Tell us.