Remote MCP · Endpoint

Trillboards Campaign Planner MCP server

No. Trillboards Campaign Planner answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.trillboards.com/mcp/advertiser

The last check completed an MCP handshake.

Registry name
com.trillboards/planner
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
154 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Plan and book out-of-home, CTV, video, audio and display campaigns, paid through Stripe.
Listing
From the official MCP registry (active).
Recent checks of Trillboards Campaign Planner
CheckedResultHandshake
1 hour agoHandshake completed154 ms
10 days agoHandshake completed103 ms
10 days agoHandshake completed156 ms
11 days agoHandshake completed108 ms
12 days agoHandshake completed101 ms
14 days agoHandshake completed136 ms
14 days agoHandshake completed99 ms
15 days agoHandshake completed97 ms
17 days agoHandshake completed142 ms
19 days agoHandshake completed555 ms
21 days agoHandshake completed158 ms
24 days agoHandshake completed107 ms
26 days agoHandshake completed142 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 Trillboards Campaign Planner and makes no claim about it beyond what these checks measured.