MCP server list / Lead Intelligence
Pay-per-call lead intelligence tools with free MCP discovery and x402 payments.
Answered:
4 of 4 checks
- Status
- responds
- Typical response time
- 184.5 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 262 ms.
- Address
- https://api.timzinin.com/
mcp/ lead-intelligence - Listed in:
- official MCP registry
mcp_registry - Registry name
- com.timzinin.api/
lead-intelligence - Transport
- streamable HTTP
streamable-http - Host
api.timzinin.com
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- zinin-m2m-hub-lead-intelligence
- Version:
- 1.0.0
- MCP features it lists:
- tools
- Tool names:
pricing_infocareers-page-scraperclinic-reception-gap-lead-finderdomain-to-verified-work-emailjob-posting-to-hiring-manager-emaillead-list-cleanernew-opening-permit-lead-radarrestaurant-booking-gap-lead-finder- Instructions excerpt:
- Lead Intelligence. 7 pay-per-call tools plus one free tool, `pricing_info`. Every other tool charges per call: USDC on base over x402. Attach the signed payment payload as a plain JSON object in params._meta["x402/payment"] of the tools/call request. Without it the call is answered with isError:true and the payment requirements in structuredContent, and no…
Reported Aug 17, 2026, 05:10 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 118 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 204 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 165 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 262 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.