Remote MCP · Endpoint

LayerCall MCP server

No. LayerCall answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
com.layercall/trust-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
86 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Score an IP, email, phone, domain or device for fraud in one call, with the signals behind it.
Website
https://www.layercall.com/docs/mcp
Repository
https://github.com/LayerCall/layercall-sdk
Listing
From the official MCP registry (active).
Recent checks of LayerCall
CheckedResultHandshake
2 hours agoHandshake completed86 ms
19 hours agoHandshake completed165 ms
2 days agoHandshake completed83 ms
3 days agoHandshake completed139 ms
4 days agoHandshake completed171 ms
5 days agoHandshake completed113 ms
6 days agoHandshake completed90 ms
7 days agoHandshake completed127 ms
10 days agoHandshake completed138 ms
13 days agoHandshake completed108 ms
15 days agoHandshake completed137 ms
17 days agoHandshake completed139 ms
19 days agoHandshake completed82 ms
21 days agoHandshake completed131 ms
23 days agoHandshake completed132 ms
25 days agoHandshake completed104 ms
27 days agoHandshake completed141 ms
28 days agoHandshake completed129 ms
29 days agoHandshake completed87 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with LayerCall and makes no claim about it beyond what these checks measured.