Live: Tor + abuse feeds refreshed every 6 hours

LayerCall

MCP server

One endpoint, and any client that speaks the protocol.

Server URL

https://www.layercall.com/api/mcp

Transport is Streamable HTTP. Authenticate with your API key as a bearer token — a free key covers 1,000 lookups a month.

Setup

Pick your client.

Run this in your terminal — it writes the config for you.

claude mcp add --transport http layercall https://www.layercall.com/api/mcp \
  --header "Authorization: Bearer YOUR_KEY"

Replace YOUR_KEY with a LayerCall API key. A test-mode key works here too and never bills — the right choice while an agent is calling things in a loop.

Tools

Seven tools, each returning the same shape as its REST endpoint.

score_ip

VPN, proxy, Tor, datacenter, geolocation and ASN for an IP — naming the VPN provider where its own published list confirms it.

verify_email

Syntax, MX, disposable providers, role accounts, homograph lookalikes and domain age.

lookup_phone

Numbering-plan validation worldwide, E.164, line type. Global, not US-only.

score_domain

RDAP registration date, registrar, MX/SPF/DMARC, disposable and risky-TLD detection.

score_device

Device fingerprint reputation and bot probability — including the same device reappearing across unrelated accounts.

verify_agent

Web Bot Auth (RFC 9421): proves a signed agent is who it claims to be, rather than inferring it from a user-agent string.

score_user

All of the above weighted into one verdict for a whole signup. A block on any single component floors the combined score at review, so one red flag is never averaged away by four clean ones.

Every tool takes an optional strictness of 0–3 and returns a 0–100 risk_score with an allow / review / block verdict.

Billing

A tool call costs exactly what the equivalent REST call costs and draws on the same monthly quota — the connector is not a way around it. Test-mode keys work here and never bill, which is what you want while an agent is calling things in a loop.

Checking it works

initialize and tools/list answer without a key, so you can confirm the endpoint is reachable before configuring credentials.

curl -X POST https://www.layercall.com/api/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'