Remote MCP · Endpoint

uk.co.ppclawfirms/site MCP server

No. uk.co.ppclawfirms/site answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://ppclawfirms.co.uk/mcp

The last check completed an MCP handshake.

Registry name
uk.co.ppclawfirms/site
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
582 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
PPC for law firms: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
Listing
From the official MCP registry (active).
Recent checks of uk.co.ppclawfirms/site
CheckedResultHandshake
44 minutes agoHandshake completed582 ms
3 days agoHandshake completed709 ms
13 days agoHandshake completed754 ms
13 days agoHandshake completed779 ms
15 days agoHandshake completed950 ms
15 days agoHandshake completed998 ms
17 days agoHandshake completed1.32 s
18 days agoHandshake completed567 ms
18 days agoHandshake completed791 ms
20 days agoHandshake completed839 ms
22 days agoHandshake completed1.19 s
25 days agoHandshake completed714 ms
27 days agoHandshake completed756 ms
29 days agoHandshake completed1.04 s

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

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 uk.co.ppclawfirms/site and makes no claim about it beyond what these checks measured.