mcp-registry/com.mentionry/mentionry · v1.1.0
As of 2026-10-26 08:45 UTC, the Mentionry MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 11 outages in 90 days, with a median recovery of 7 minutes.
Find who links to your competitors but not you, judge each opening, and draft the pitch.
Claude Code
claude mcp add --transport http mentionry-mcp-server https://mentionry.com/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"mentionry-mcp-server": {
"type": "http",
"url": "https://mentionry.com/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
43 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
133 parameter(s) across 33 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 →
3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
In the last 30 days: 2 tool(s) removed and 24 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 →
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 →
17 of 43 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 33 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.mentionry%2Fmentionry/fixes
{
"name": "describe_agent",
"description": "What one agent does, step by step, and what it needs: the values you must pass to run_agent, what it hands back, how many of its steps reach a vendor that charges, and anything currently stopping it from running.",
"inputSchema": {
"type": "object",
"required": [
"agent_id"
],
"properties": {
"agent_id": {
"type": "string",
"description": "From list_agents."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Describe an agent"
}{
"name": "find_prospects",
"description": "Search the open web for pages that would plausibly link to this site: resource pages, roundups, listicles and directories in its subject. Returns each with the reason it was kept.",
"inputSchema": {
"type": "object",
"required": [
"domain"
],
"properties": {
"topic": {
"type": "string",
"description": "Optional. Narrows the search to one theme."
},
"domain": {
"type": "string"
},
"audience": {
"type": "string"
},
"keywords": {
"type": "array",
"items": {
"type": "string"
}
},
"description": {
"type": "string",
"description": "What the site does. Use read_site if you do not have one."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Find prospects"
}{
"name": "list_agents",
"description": "The agents on this account: what each is called, how many steps it has, whether it would run as it stands, and when it last changed. Call describe_agent next to learn what one needs before running it.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "List your agents"
}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.mentionry/mentionry"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.mentionry/mentionry"}) over MCP.
write_landing_page ~311 tokensread_live_search_campaign ~305 tokenswrite_email_template ~274 tokensrecord_page_deployment ~271 tokensread_latest_answer_reviews ~265 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.mentionry%2Fmentionry?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.mentionry%2Fmentionry?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.mentionry%2Fmentionry.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.mentionry%2Fmentionry.svg :target: https://glimind.com/server/mcp-registry%2Fcom.mentionry%2Fmentionry?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:5ba82ad6d983ecf8…, first seen 2026-10-24, included at leaf 56315 of 71,748. Version history · verify what your client received.
Compare: most reliable search servers · most reliable other servers · most reliable knowledge servers · most reliable productivity servers · most reliable communication 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-26 08:45 UTC, the Mentionry MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 11 outages in 90 days, with a median recovery of 7 minutes.
Mentionry MCP server advertises 43 tools, including backlink_gap, cancel_preparation_job, describe_agent, discover_competitors, dismiss_preparation_action.
Point your MCP client at this streamable-http endpoint: https://mentionry.com/api/mcp
Glimind scanned all 43 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.