LayerCall MCP Server

by layercall Your server? Claim it

not responding

LayerCall is listed as active in the registry but did not answer our last check. It exposes 7 tools. Last commit 14 Sep 2026.

Score an IP, email, phone, domain or device for fraud in one call, with the signals behind it.

Uptime history 49 days of history · worst day 15%

49 days agonow

17.6%

Uptime 24h

16 of 91 checks

Tools

read from the server

827 ms

Response time

average over 24h

Stars

last commit 14 Sep 2026

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 31 August 2026. No other catalogue keeps this.

31 Aug a tool description was rewritten score_user

LayerCall does not always answer

Over the last week it answered 30.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add trust-api --transport http https://www.layercall.com/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "trust-api": {
      "url": "https://www.layercall.com/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.trust-api]
url = "https://www.layercall.com/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "trust-api": {
      "url": "https://www.layercall.com/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "trust-api": {
      "url": "https://www.layercall.com/api/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

score

score_device

Judge 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.

score_domain

Profile 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'.

score_ip

Risk-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.

score_user

Score 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.

verify

verify_agent

Cryptographically 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.

verify_email

Check 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.

lookup

lookup_phone

Validate 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.

Endpoints

URL	Transport	State	Latency	Checked
https://www.layercall.com/api/mcp	streamable-http	answering	130 ms	14 min ago

Alternatives to LayerCall

same job, measured the same way

Email Check

by kaiv

Email posture for any domain: can it receive mail, can it be spoofed? MX, SPF and DMARC.

4 tools answering

AstraVerify Domain Trust Check

by astraverify

Email security and AI discoverability scores for any domain, with the exact record or tag to fix.

5 tools answering

Website Change Watcher

by pavel-tashev

Detect what changed on a page, sitemap or feed since the last check, with a diff and email alert

answering

Shiply

by shiply

Publish any app in one call: SQL database, functions, email, and a custom domain. Flat price.

114 tools answering

Stabledrop escrow payments

by stabledrop

Stablecoin escrow payments the buyer can dispute, with a signed receipt. Pay a wallet or an email.

6 tools answering

Agentline

by jgottlieb84

Phone numbers, SMS, 2FA capture, voice calls, and email for AI agents.

70 installs/wk local only

Fidro

by fidro

Signup fraud checks: score emails and IPs, look up IPs and manage your blocklist.

answering

MX Probe

by mxprobe

Email verification for AI agents: send, hold or kill with the reason. Signup and credits by API.

110 installs/wk local only

LayerCall — questions

Answers built from our own checks of this server.

What can LayerCall do?

It exposes 7 tools, read directly from the server on our last check. Among them: lookup_phone, score_device, score_domain, score_ip, score_user, verify_agent and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is LayerCall mostly used for?

Its tools cluster around score and verify. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is LayerCall working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 16 of 91 checks got a reply (17.6%), average response time 827 ms. The bar chart above shows every period we have measured.

The registry lists LayerCall as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect LayerCall?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does LayerCall need an API key?

No. LayerCall completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is LayerCall?

It answers our handshake in 827 ms on average, which is faster than 14% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is LayerCall open source?

Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.