Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "trust-api": {
      "type": "http",
      "url": "https://www.layercall.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${TRUST_API_TOKEN}"
      }
    }
  }
}

claude mcp add --transport http trust-api https://www.layercall.com/api/mcp --header "Authorization: Bearer ${TRUST_API_TOKEN}"

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

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "trust-api": {
      "type": "remote",
      "url": "https://www.layercall.com/api/mcp",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer {env:TRUST_API_TOKEN}"
      }
    }
  }
}

{
  "mcpServers": {
    "trust-api": {
      "type": "http",
      "url": "https://www.layercall.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${TRUST_API_TOKEN}"
      }
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=trust-api&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vd3d3LmxheWVyY2FsbC5jb20vYXBpL21jcCIsImhlYWRlcnMiOnsiQXV0aG9yaXphdGlvbiI6IkJlYXJlciAke1RSVVNUX0FQSV9UT0tFTn0ifX0%3D"
}

{
  "servers": {
    "trust-api": {
      "type": "http",
      "url": "https://www.layercall.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${TRUST_API_TOKEN}"
      }
    }
  }
}

{
  "mcpServers": {
    "trust-api": {
      "httpUrl": "https://www.layercall.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${TRUST_API_TOKEN}"
      }
    }
  }
}

extensions:
  "trust-api":
    enabled: true
    name: "trust-api"
    type: streamable_http
    uri: "https://www.layercall.com/api/mcp"
    headers:
      "Authorization": "Bearer ${TRUST_API_TOKEN}"
    timeout: 300

Placeholders to fill from your own secret store: ${TRUST_API_TOKEN}. The registry never accepts secret values.

Quality 79 / 100good

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene71 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
fail
tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: verify_email (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); score_user (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); score_ip (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
pass
tools.token_costabout 1,023 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

7 tools, about 1,023 tokens to load them all · tool set 5baf1e219d99 · checked 2026-10-19 10:52 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 97 / 100

provenance100

liveness100

freshness85

hygiene100

+repository +namespace-matches-repo +dns-namespace +website +reachable +uptime-100% ~updated-76d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://www.layercall.com/api/mcp` streamable-http	api_key `${TRUST_API_TOKEN}`	yes	100%	852 ms	2025-06-18	2026-10-19

Tools (7)

`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.
`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_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.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "com.layercall/trust-api",
  "title": "LayerCall",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://www.layercall.com/api/mcp",
      "type": "streamable-http",
      "headers": [
        {
          "name": "Authorization",
          "isSecret": true,
          "isRequired": true,
          "description": "Bearer <your LayerCall API key>. Free key at https://www.layercall.com/get-key — 1,000 lookups a month, no card."
        }
      ]
    }
  ],
  "version": "1.0.0",
  "repository": {
    "url": "https://github.com/LayerCall/layercall-sdk",
    "source": "github"
  },
  "websiteUrl": "https://www.layercall.com/docs/mcp",
  "description": "Score an IP, email, phone, domain or device for fraud in one call, with the signals behind it."
}