layercall

endpoint

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

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is layercall live?

Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.

Is layercall free to use?

Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.

What tools does layercall have?

7 tools: score_ip, verify_email, score_domain, score_device, verify_agent, score_user, lookup_phone.

Is layercall safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• lookup_phone reads auth-required 26h ago

  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.

  mcp-tool

  123456789101112131415161718192021

  {
    "type": "object",
    "required": [
      "phone"
    ],
    "properties": {
      "phone": {
        "type": "string",
        "description": "Number in international form (+14155552671) or national form with country set"
      },
      "country": {
        "type": "string",
        "description": "ISO 3166-1 alpha-2, required only for national-format numbers"
      },
      "strictness": {
        "type": "integer",
        "maximum": 3,
        "minimum": 0
      }
    }
  }

  arguments 21 lines copy
• score_ip reads unknown never probed

  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.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "required": [
      "ip"
    ],
    "properties": {
      "ip": {
        "type": "string",
        "description": "IPv4 or IPv6 address, e.g. 8.8.8.8"
      },
      "strictness": {
        "type": "integer",
        "maximum": 3,
        "minimum": 0,
        "description": "0 lenient, 1 balanced (default), 2 strict, 3 paranoid. Moves the verdict thresholds only; the score is unchanged."
      }
    }
  }

  arguments 18 lines copy
• verify_email reads unknown never probed

  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.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "required": [
      "email"
    ],
    "properties": {
      "email": {
        "type": "string",
        "description": "Full email address"
      },
      "strictness": {
        "type": "integer",
        "maximum": 3,
        "minimum": 0
      }
    }
  }

  arguments 17 lines copy
• score_domain reads unknown never probed

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

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "domain"
    ],
    "properties": {
      "domain": {
        "type": "string",
        "description": "Bare domain, e.g. example.com"
      }
    }
  }

  arguments 12 lines copy
• score_device reads unknown never probed

  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.

  mcp-tool

  12345678910111213141516

  {
    "type": "object",
    "required": [
      "device_id"
    ],
    "properties": {
      "ip": {
        "type": "string",
        "description": "Visitor IP, so timezone-vs-country can be checked"
      },
      "device_id": {
        "type": "string",
        "description": "Hex fingerprint from /fp.js"
      }
    }
  }

  arguments 16 lines copy
• verify_agent reads unknown never probed

  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.

  mcp-tool

  123456789101112131415161718192021

  {
    "type": "object",
    "required": [
      "url",
      "headers"
    ],
    "properties": {
      "url": {
        "type": "string",
        "description": "Absolute URL the agent requested from you"
      },
      "method": {
        "type": "string",
        "description": "HTTP method, default GET"
      },
      "headers": {
        "type": "object",
        "description": "Request headers, including signature, signature-input and signature-agent"
      }
    }
  }

  arguments 21 lines copy
• score_user reads unknown never probed

  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.

  mcp-tool

  1234567891011121314151617181920212223

  {
    "type": "object",
    "properties": {
      "ip": {
        "type": "string"
      },
      "email": {
        "type": "string"
      },
      "phone": {
        "type": "string"
      },
      "strictness": {
        "type": "integer",
        "maximum": 3,
        "minimum": 0
      },
      "phone_country": {
        "type": "string",
        "description": "ISO 3166-1 alpha-2 for national-format numbers"
      }
    }
  }

  arguments 23 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.