Remote MCP · Endpoint

LeadForm AI MCP server

No. LeadForm AI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://leadform-ai.vercel.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.sarvin-tech/leadform-ai
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
224 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Paid B2B lead scoring and next-action qualification for AI agents.
Listing
From the official MCP registry (active).
Recent checks of LeadForm AI
CheckedResultHandshake
1 hour agoHandshake completed224 ms
2 days agoHandshake completed89 ms
4 days agoHandshake completed746 ms
6 days agoHandshake completed58 ms
8 days agoHandshake completed317 ms
10 days agoHandshake completed64 ms
12 days agoHandshake completed65 ms
14 days agoHandshake completed96 ms
15 days agoHandshake completed96 ms
16 days agoHandshake completed108 ms
17 days agoHandshake completed107 ms
20 days agoHandshake completed59 ms
22 days agoHandshake completed63 ms
23 days agoHandshake completed191 ms

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

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.

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