Remote MCP · Endpoint

LicenseGround MCP server

No. LicenseGround answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://licenseground.com/mcp

The last check completed an MCP handshake.

Registry name
com.licenseground/licenseground
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
581 ms
Tools exposed
6 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Deterministic trade contractor license verification & compliance gating for autonomous AI agents.
Listing
From the official MCP registry (active).
Recent checks of LicenseGround
CheckedResultHandshake
3 hours agoHandshake completed581 ms
2 days agoHandshake completed3.38 s
4 days agoHandshake completed526 ms
6 days agoFailed - the request timed out—
8 days agoHandshake completed533 ms
10 days agoHandshake completed612 ms
13 days agoHandshake completed601 ms
14 days agoHandshake completed430 ms
16 days agoHandshake completed488 ms
17 days agoHandshake completed582 ms
18 days agoHandshake completed415 ms
21 days agoHandshake completed697 ms
22 days agoHandshake completed414 ms
24 days agoHandshake completed429 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 LicenseGround and makes no claim about it beyond what these checks measured.