Is the Layercall Trust Api MCP server down?

mcp-registry/com.layercall/trust-api · v1.0.0

As of 2026-10-25 09:23 UTC, the Layercall Trust Api MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

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

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

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (77/100)

What to fix (3)

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.layercall%2Ftrust-api/fixes

{
  "name": "lookup_phone",
  "description": "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.",
  "inputSchema": {
    "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
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Validate a phone number"
}

{
  "name": "score_ip",
  "description": "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.",
  "inputSchema": {
    "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."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Score an IP address"
}

{
  "name": "verify_email",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "email"
    ],
    "properties": {
      "email": {
        "type": "string",
        "description": "Full email address"
      },
      "strictness": {
        "type": "integer",
        "maximum": 3,
        "minimum": 0
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Verify an email address"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.layercall/trust-api"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.layercall/trust-api"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~1,208 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• verify_agent ~246 tokens
• score_user ~220 tokens
• score_ip ~173 tokens
• score_device ~170 tokens
• lookup_phone ~161 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.layercall%2Ftrust-api.svg)](https://glimind.com/server/mcp-registry%2Fcom.layercall%2Ftrust-api?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcom.layercall%2Ftrust-api?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.layercall%2Ftrust-api.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.layercall%2Ftrust-api.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.layercall%2Ftrust-api?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:2d4ce6471a83db9e…, first seen 2026-10-17, included at leaf 9368 of 65,111. Version history · verify what your client received.

Tools (7)

• lookup_phone
• score_device
• score_domain
• score_ip
• score_user
• verify_agent
• verify_email

Compare: most reliable other servers · most reliable security servers · most reliable email servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Layercall Trust Api MCP server down right now?

As of 2026-10-25 09:23 UTC, the Layercall Trust Api MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Layercall Trust Api MCP server provide?

Layercall Trust Api MCP server advertises 7 tools, including lookup_phone, score_device, score_domain, score_ip, score_user.

How do I install Layercall Trust Api MCP server?

Point your MCP client at this streamable-http endpoint: https://www.layercall.com/api/mcp

Is the Layercall Trust Api MCP server safe to connect to an AI agent?

Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Layercall Trust Api MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.