Remote MCP · Endpoint

com.essentras/placements MCP server

No. com.essentras/placements answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://essentras.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.essentras/placements
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
217 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Buy press coverage in 3,800+ vetted media outlets. Price a basket, get a checkout link.
Listing
From the official MCP registry (active).
Recent checks of com.essentras/placements
CheckedResultHandshake
1 hour agoHandshake completed217 ms
2 days agoHandshake completed106 ms
5 days agoHandshake completed112 ms
7 days agoHandshake completed112 ms
9 days agoHandshake completed198 ms
11 days agoHandshake completed124 ms
13 days agoHandshake completed119 ms
15 days agoHandshake completed286 ms
17 days agoHandshake completed329 ms
19 days agoHandshake completed289 ms
20 days agoHandshake completed292 ms
21 days agoHandshake completed844 ms
22 days agoHandshake completed1.21 s

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