Security & Testing

layercall.com

Provides security risk scoring and validation for IPs, emails, phones, domains, and devices.

1 endpoint7 known toolsFirst detected August 5, 2026Last detected September 5, 2026

ENDPOINT 1

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

No auth detected

MCP server metadata

Name: layercall
Version: 1.0.0

Capabilities

tools

Server instructions

Trust and fraud signals for IPs, emails, phone numbers, domains and whole signups. Every tool returns a 0-100 risk_score (higher is riskier) and a verdict of allow, review or block. Prefer score_user when judging a person: it weights the components together and will not average away a hard block on one of them — it bills one lookup per component supplied, and returns billable_lookups so you can see what each call cost. Requires a LayerCall API key sent as `Authorization: Bearer <key>`; a free key covers 1,000 lookups a month — 1,000 single-value calls, or around 250 four-component score_user calls.

Known tools 7

score_ip

Risk-score an IPv4 or IPv6 address.

Inferred read-only

verify_email

Check an email for syntax, MX records, disposable/throwaway providers, role accounts (info@, admin@), homograph lookalikes and domain age.

Potential side effects

lookup_phone

Validate a phone number worldwide against its national numbering plan.

Inferred read-only

score_domain

Profile a domain: registration date from RDAP, registrar, MX/SPF/DMARC configuration, disposable-mail and risky-TLD detection.

Inferred read-only

score_device

Judge a browser fingerprint from /fp.

Inferred read-only

verify_agent

Cryptographically verify a Web Bot Auth signature (RFC 9421) — proof of WHICH agent is calling, not a guess from the user-agent.

Inferred read-only

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.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.layercall]
url = "https://www.layercall.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "layercall": {
      "type": "http",
      "url": "https://www.layercall.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: layercall
Remote MCP URL: https://www.layercall.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "layercall": {
      "type": "http",
      "url": "https://www.layercall.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "layercall",
  "transport": "streamable-http",
  "url": "https://www.layercall.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for layercall.com was fetched 2026-08-11T03:45:20.195Z.

Trust status Neutral

layercall.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.