# LayerCall (remote · www.layercall.com)

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

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-07

## Components

- remote · `www.layercall.com`: 62/100 (this document), [markdown](https://verifymcp.io/servers/com-layercall-trust-api/api-mcp.md), [page](https://verifymcp.io/servers/com-layercall-trust-api/api-mcp)

## Channel facts

- Endpoint: `https://www.layercall.com/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-07.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 880 tokens (~125/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-layercall-trust-api --url https://www.layercall.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-layercall-trust-api:
    url: "https://www.layercall.com/api/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-06 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-05 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-04 (score 61)

First indexed and scored.

## MCP tools (7)

### `score_ip` (~130 tokens)

Score an IP address

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.

Input parameters:

- `ip` (string, required): IPv4 or IPv6 address, e.g. 8.8.8.8
- `strictness` (integer): 0 lenient, 1 balanced (default), 2 strict, 3 paranoid. Moves the verdict thresholds only; the score is unchanged.

### `verify_email` (~75 tokens)

Verify an email address

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.

Input parameters:

- `email` (string, required): Full email address
- `strictness` (integer)

### `lookup_phone` (~107 tokens)

Validate a phone number

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.

Input parameters:

- `country` (string): ISO 3166-1 alpha-2, required only for national-format numbers
- `phone` (string, required): Number in international form (+14155552671) or national form with country set
- `strictness` (integer)

### `score_domain` (~75 tokens)

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

Input parameters:

- `domain` (string, required): Bare domain, e.g. example.com

### `score_device` (~106 tokens)

Score a device fingerprint

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.

Input parameters:

- `device_id` (string, required): Hex fingerprint from /fp.js
- `ip` (string): Visitor IP, so timezone-vs-country can be checked

### `verify_agent` (~164 tokens)

Verify a signed AI agent (Web Bot Auth)

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.

Input parameters:

- `headers` (object, required): Request headers, including signature, signature-input and signature-agent
- `method` (string): HTTP method, default GET
- `url` (string, required): Absolute URL the agent requested from you

### `score_user` (~119 tokens)

Score a whole signup

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.

Input parameters:

- `email` (string)
- `ip` (string)
- `phone` (string)
- `phone_country` (string): ISO 3166-1 alpha-2 for national-format numbers
- `strictness` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-layercall-trust-api/api-mcp#diagnostics

## Score history

- 2026-08-07: 62
- 2026-08-06: 62
- 2026-08-05: 61
- 2026-08-04: 61

## Links

- Remote endpoint: https://www.layercall.com/api/mcp
- Authorisation metadata: https://www.layercall.com/.well-known/oauth-protected-resource/api/mcp
- Repository: https://github.com/LayerCall/layercall-sdk
- Website: https://www.layercall.com/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-layercall-trust-api/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-layercall-trust-api/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-layercall-trust-api/api-mcp