Remote MCP · Endpoint

uk.co.googleadsagencybirmingham/site MCP server

No. uk.co.googleadsagencybirmingham/site answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://googleadsagencybirmingham.co.uk/mcp

The last check completed an MCP handshake.

Registry name
uk.co.googleadsagencybirmingham/site
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
344 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Google Ads agency Birmingham: the site's own MCP server — enquiry (enquiry = a human handoff,...
Listing
From the official MCP registry (active).
Recent checks of uk.co.googleadsagencybirmingham/site
CheckedResultHandshake
4 hours agoHandshake completed344 ms
2 days agoHandshake completed702 ms
5 days agoHandshake completed811 ms
7 days agoHandshake completed733 ms
9 days agoHandshake completed1.01 s
11 days agoHandshake completed630 ms
13 days agoHandshake completed1.39 s
15 days agoHandshake completed948 ms
17 days agoHandshake completed714 ms
18 days agoHandshake completed830 ms
20 days agoHandshake completed1.34 s
21 days agoHandshake completed589 ms
23 days agoHandshake completed896 ms

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

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