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
224 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 completed224 ms
4 days agoHandshake completed652 ms
14 days agoHandshake completed193 ms
15 days agoHandshake completed211 ms
15 days agoHandshake completed132 ms
17 days agoHandshake completed60 ms
18 days agoHandshake completed81 ms
19 days agoHandshake completed226 ms
20 days agoHandshake completed71 ms
21 days agoHandshake completed80 ms
23 days agoHandshake completed217 ms
25 days agoHandshake completed106 ms
28 days agoHandshake completed112 ms

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