mcp-registry/com.essentras/placements · v1.3.0
Also listed as github/ltv-so/essentras-mcp
As of 2026-10-22 11:20 UTC, the Essentras Placements MCP server is up with a Glimind reliability score of 71/100 (grade C). Over the last 30 days it answered 98.6% of Glimind's liveness checks. It had 23 outages in 90 days, with a median recovery of 7 minutes.
Buy press coverage in 3,800+ vetted media outlets. Price a basket, get a checkout link.
Claude Code
claude mcp add --transport http essentras-placements-mcp-server https://essentras.com/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"essentras-placements-mcp-server": {
"type": "http",
"url": "https://essentras.com/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
2 tool definition(s) exceed ~1,200 tokens each (largest: check_review_removability, ~1,568).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~1,832 tokens every session. How to fix →
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Reachable 98.6% of the time over the last 30 days; median recovery 7 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 3 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.essentras/placements"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.essentras/placements"}) over MCP.
check_review_removability ~1,568 tokenscheck_wikipedia_notability ~1,464 tokenscheck_knowledge_panel_readiness ~1,005 tokensfind_removal_route ~819 tokenssearch_outlets ~555 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.essentras%2Fplacements?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.essentras%2Fplacements?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.essentras%2Fplacements.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.essentras%2Fplacements.svg :target: https://glimind.com/server/mcp-registry%2Fcom.essentras%2Fplacements?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:617c232cc0649fd8…, first seen 2026-10-19, included at leaf 26825 of 45,622. Version history · verify what your client received.
Compare: most reliable other servers · most reliable knowledge servers · most reliable search servers · most reliable retrieval servers · most reliable finance servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 11:20 UTC, the Essentras Placements MCP server is up with a Glimind reliability score of 71/100 (grade C). Over the last 30 days it answered 98.6% of Glimind's liveness checks. It had 23 outages in 90 days, with a median recovery of 7 minutes.
Essentras Placements MCP server advertises 10 tools, including check_instagram_recovery_path, check_knowledge_panel_readiness, check_review_removability, check_wikipedia_notability, find_removal_route.
Point your MCP client at this streamable-http endpoint: https://essentras.com/api/mcp
Glimind scanned all 10 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.