Mmcp.market

LayerCall MCP server

by layercall.com·com.layercall/trust-api·v1.0.0
No reviews yet

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

A89/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A89/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed LayerCall yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

LayerCall tools (7, 1 write)

write = sends, deletes, buys or posts
  • lookup_phoneFree

    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.

  • score_deviceFree

    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_domainFree

    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_ipFree

    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_userFree

    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_agentFree

    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_emailwrite actionFree

    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.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1291ms20/20
  • Tool poisoning7 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 10 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10
Overall 89/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the LayerCall repository's README, as published. We do not edit it. Read it on GitHub

LayerCall SDKs

Official clients for LayerCall — score an IP, email, phone number, domain, or a whole signup for fraud in a single call.

Both clients have zero dependencies. A trust check sits on your signup path, which is the worst place in an application to introduce a dependency tree.

Get a free API key — 1,000 lookups a month, no card required, no daily cap.

Try it without installing anything

export LAYERCALL_API_KEY=tl_live_...
npx layercall ip 8.8.8.8
npx layercall email someone@mailinator.com
npx layercall domain example.com
npx layercall user --ip 1.2.3.4 --email a@b.com

What it returns

Every endpoint returns the same shape: a 0–100 risk_score, an allow | review | block verdict, and the signals behind it.

{
  "ip": "185.220.101.1",
  "risk_score": 60,
  "verdict": "review",
  "signals": {
    "is_vpn": true,
    "is_proxy": true,
    "is_datacenter": true,
    "is_tor": true,
    "recent_abuse": false
  },
  "geo": { "country": "DE", "city": "Berlin", "asn": "AS60729" },
  "vpn_provider": null
}

Two things worth reading before you integrate

Prefer step-up over rejection. The review band starts where an ordinary commercial VPN lands, and most VPN users are ordinary customers. Send them an OTP or a 3-D Secure challenge instead of a refusal: a real user clears it in seconds, an attacker cannot, and a false positive costs friction rather than a customer. This is what Stripe Radar and Sift both converged on.

null means unknown, not "no". newlyregistered is null when a TLD publishes no RDAP (.de, .ru, .ac.uk among them), and mailboxexists is null when the mail provider does not answer honestly — Gmail and Yahoo accept mail for addresses that do not exist. Treating either as a negative finding is the specific mistake these fields exist to prevent.

Endpoints

Full reference: layercall.com/docs · OpenAPI 3.1: layercall.com/openapi.json

Testing without spending anything

Test-mode keys return deterministic synthetic data, drawn from ranges reserved for exactly this purpose — RFC 5737 addresses, example.com, the 555-01XX fiction block. Same shape and fields as production, so your assertions are real ones. They never bill, never hit live data sources, and never write to the shared reputation network.

Every fixture is documented, so you can assert on exact values rather than "did it return a number": layercall.com/docs/test-mode

MCP — call it from an AI agent

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

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

LayerCall: common questions

Is LayerCall MCP server safe?
Yes, by our scan: it is graded A (89/100). Read the LayerCall safety report
How do I install LayerCall?
It runs remotely at www.layercall.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
Does LayerCall need an API key?
Yes. The registry entry asks for Authorization.
Is LayerCall maintained?
The last commit was 10 days ago (2026-09-14). The latest release is v1.0.0.
Is LayerCall up?
100% of our last 20 checks got an answer. We check remote servers about four times a day.
What can I use instead of LayerCall?
Servers from other publishers that do the same job: CosVoice MCP server, MCP server and Shipmail MCP server. Compare all LayerCall alternatives.

Alternatives to LayerCall

Same job from other publishers: the closest match first, then the best rated.

All LayerCall alternatives →
  • CosVoice
    A real phone number and email for your AI Chief of Staff. Calls, bookings by phone, summaries.
    A
  • MCP
    20 domain recon tools for AI agents: DNS, SSL, headers, email, subdomains, lookalikes, changes.
    A
  • Shipmail
    Shipmail MCP server for AI agent custom-domain email inboxes with REST API and webhooks.
    A
  • ContrastAPI
    55 tools, 7 Resources, Sigma rules, email SPF/DMARC, MITRE, CVE/KEV, risk_score. No key.
    B
  • smbCloud Mail & Auth
    Email infrastructure and authentication for developers: domains, inbox routes, auth apps, deploys.
    A
LayerCall vs CosVoiceLayerCall vs MCPLayerCall vs Shipmail

More from layercall.com →