LayerCall
com.layercall/trust-apiVersion 1.0.0Score an IP, email, phone, domain or device for fraud in one call, with the signals behind it.
Status
Responds236 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:04 UTC
- Latency
- 236 ms
- Remotes responding
- 1 of 1
- Sign-in
- API key
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://www.layercall.com/api/mcpResponds236 msNo sign-in
Claude Code
claude mcp add --transport http trust-api https://www.layercall.com/api/mcp --header 'Authorization: Bearer <YOUR_TOKEN>'Replace <YOUR_TOKEN> before running.
Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: trust-api
Remote MCP server URL: https://www.layercall.com/api/mcp
This server expects the header Authorization.Cursor
{
"mcpServers": {
"trust-api": {
"url": "https://www.layercall.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Replace <YOUR_TOKEN> before running.
VS Code
code --add-mcp '{"name":"trust-api","type":"http","url":"https://www.layercall.com/api/mcp","headers":{"Authorization":"Bearer <YOUR_TOKEN>"}}'Replace <YOUR_TOKEN> before running.
Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
7 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
lookup_phoneValidate a phone number worldwide against its national numbering plan. Returns E.164, country, line type (mobile/fixed/VoIP/toll-free/premium) and a risk score. Works globally, not US-only. | Not declared | Not declared | Not declared | Not declared |
score_deviceJudge a browser fingerprint from /fp.js: headless detection, automation frameworks (Selenium, Puppeteer, Playwright), timezone-versus-IP mismatch and repeat-device history. Note the ceiling honestly — the declared signals it relies on are the first thing stealth tooling patches, so a clean result is weaker evidence than a dirty one. | Not declared | Not declared | Not declared | Not declared |
score_domainProfile a domain: registration date from RDAP, registrar, MX/SPF/DMARC configuration, disposable-mail and risky-TLD detection. newly_registered is null when the age genuinely could not be determined — treat that as unknown, not as 'established'. | Not declared | Not declared | Not declared | Not declared |
score_ipRisk-score an IPv4 or IPv6 address. Detects commercial VPNs (naming the provider where its own published list confirms it), proxies, Tor exit nodes and datacenter hosting, and returns geolocation, ASN and a 0-100 risk score with an allow/review/block verdict. | Not declared | Not declared | Not declared | Not declared |
score_userScore an entire signup in one call — any combination of IP, email, phone and domain — returning a single weighted risk score, a verdict, and the top contributing signals. A hard block on any component is never averaged away. This is the tool to use when judging a person rather than a value. Costs one lookup PER COMPONENT supplied, not one per call, so four identifiers cost four; the response reports the exact figure as billable_lookups, and cached components are refunded. | Not declared | Not declared | Not declared | Not declared |
verify_agentCryptographically verify a Web Bot Auth signature (RFC 9421) — proof of WHICH agent is calling, not a guess from the user-agent. Returns verified true/false plus the agent's identity and declared purpose. This is the only check here that proves rather than infers, so it carries no score and no verdict: a verified assistant acting for a real user is usually welcome, a verified scraper usually is not, and that policy is the caller's. Pass the request the agent made to YOU — the signature covers its method, authority and path. | Not declared | Not declared | Not declared | Not declared |
verify_emailCheck an email for syntax, MX records, disposable/throwaway providers, role accounts (info@, admin@), homograph lookalikes and domain age. Returns a 0-100 risk score and an allow/review/block verdict. | Not declared | Not declared | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Aug 4, 2026
- Updated
- Aug 4, 2026
- Categories (suggested)
- CommunicationSecuritySuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared