Mentionry
REMOTE · MENTIONRY.COM
Find who links to your competitors but not you, judge each opening, and draft the pitch.
Available components
Last scanned (2 hours ago)
Scores higher than 97% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2171 tokens (~114/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Sept 26 +1
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 −5
- Stability: pass → 0.67 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://mentionry.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mentionry.com | CN=WE1,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ace470037904c62313c11e64e4dfccdf |
| SANs: mentionry.com, *.mentionry.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mentionry.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| mentionry.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'; object-src 'none'; img-src 'self' data: blob: https:; font-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://va.vercel-scripts.com; connect-src 'self' https: wss: |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mentionry.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://mentionry.com/api/mcp | HTTPS enforced | 308 | https://mentionry.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
backlink_gap Backlink gap ~69
Find pages that link to the named competitors but not to you, classified by whether a link is realistically winnable and why. Competitors are excluded from their own results: a competitor is never a prospect.
| Name | Type | Req | Description |
|---|---|---|---|
| competitors | array | – | Up to five competitor domains. |
| domain | string | yes | – |
No output schema declared.
No examples provided.
describe_agent Describe an agent ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | From list_agents. |
No output schema declared.
No examples provided.
discover_competitors Discover competitors ~68
Find the domains competing with this one, from both search results and link profile overlap. Returns each candidate with the evidence for it, so a wrong suggestion can be recognised rather than trusted.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| keywords | array | – | Optional. Sharpens the search half. |
No output schema declared.
No examples provided.
draft_pitch Draft a pitch ~127
Write one outreach email for one prospect, in your own words, using the reason that prospect would link to you. It returns the subject and body and sends nothing: sending happens from your own mailbox, after you have read it. Requires a paid Mentionry plan.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | What your site does. |
| hook | string | yes | Why this page would link to you. |
| page_title | string | – | – |
| prospect_url | string | yes | The page you want the link on. |
| sender_name | string | – | – |
| sender_site | string | yes | Your domain. |
No output schema declared.
No examples provided.
find_prospects Find prospects ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | – |
| description | string | – | What the site does. Use read_site if you do not have one. |
| domain | string | yes | – |
| keywords | array | – | – |
| topic | string | – | Optional. Narrows the search to one theme. |
No output schema declared.
No examples provided.
generate_image Generate an image ~183
Make one picture from a description: a product shot, a social visual, hero art, an ad creative, an illustration for a page or an email. Returns its public address, which write_landing_page and write_email_template accept and which you link to in your reply; the product draws it under this tool's row. Spends one image allowance (quality 'best' costs about five times more; use it only when asked).
| Name | Type | Req | Description |
|---|---|---|---|
| aspect_ratio | string | – | Default 1:1. 16:9 for a hero, 9:16 for a story, 4:3 for a card. |
| prompt | string | yes | What to draw, specifically: subject, setting, style, lighting, colours, mood. Name the brand's colours when you know them. No text inside the image unless asked. |
| quality | string | – | Default fast. |
No output schema declared.
No examples provided.
generate_video Generate a video ~200
Make one short clip (three to eight seconds; 480p by default, 720p with quality 'best' at several times the cost) from a description, optionally animating a picture generate_image already made by passing its address as first_frame_url. Renders in one to two minutes and returns its public address; the product plays it under this tool's row. Spends one video allowance, the dearest single action here, so confirm the description with the customer before calling it. Requires a paid Mentionry plan.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect_ratio | string | – | Default 16:9. 9:16 for a story or a reel. |
| first_frame_url | string | – | Optional. The /m/... address of a generated picture to animate. |
| prompt | string | yes | The motion and the scene: what moves, camera, pace, mood. |
| quality | string | – | Default fast. |
| seconds | integer | – | Default 5. |
No output schema declared.
No examples provided.
list_agents List your agents ~52
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_connections What is connected ~50
Which outside tools this account has connected, and what each one is allowed to do here. Call it before offering to file, post or draft anything, so you can say what is actually available instead of guessing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_documents List what your agents wrote ~46
The documents your agents have produced: what each is called, which agent wrote it, how long it is and how many versions it has. Pass an id to read_document for the text.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_media List generated media ~27
The pictures and clips already generated on this account, newest first, with their addresses. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
qualify_domain Qualify a domain ~87
Judge whether a domain is worth running link building for at all, from live search data. Returns a verdict, the measured signals behind it, and the honest case against. This is the same free diagnostic the dashboard runs, and for a large share of sites the answer is that the niche has nothing to mine.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to judge, for example mentionry.com |
No output schema declared.
No examples provided.
read_document Read a document ~72
The text of one document your agent wrote, with the agent, the step and the values that run was given. Returns the newest version unless an older one is asked for.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | From list_documents. |
| version | number | – | 1 is the newest. Omit for the newest. |
No output schema declared.
No examples provided.
read_site Read a site ~65
Read a domain and return what we think it is about: a description, its audience, and the keywords it should be found for. This is the brief every other tool takes as input, so call it first when you do not already have one.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
read_visibility Read your visibility ~129
The account's own answer-engine measurements over a window: how often each tracked brand appears in recorded answers (visibility), its share of all mentions (share of voice), its mean position, and the ranking against named competitors. Group by day for a trend, or by model, region, persona, prompt or topic to find where a brand is weak. This is the data behind the dashboard's Answer Engine Insights.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Window length in days. Default 30. |
| dimension | string | yes | How to group. `day` for a trend over time; the others compare buckets. |
No output schema declared.
No examples provided.
run_agent Run an agent ~101
Run one of your agents once and return what every step did, in order, with what it returned and how long it took. Pass its declared inputs as an object keyed by their `key` from describe_agent. Steps that reach a paid vendor are counted against your live-sweep allowance, one each.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | From list_agents. |
| inputs | object | – | The agent's declared inputs, keyed by `key`. Values are strings. |
No output schema declared.
No examples provided.
verify_links Check whether links landed ~79
Check a list of domains against your live backlink profile and report which of them now link to you, when the link first appeared, and whether it is still there. A link that was removed shows as a change rather than staying on the scoreboard.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Your domain. |
| pitched | array | yes | The domains or URLs you pitched. |
No output schema declared.
No examples provided.
write_email_template Write an email template ~183
Write a complete HTML marketing email (tables and inline styles, so it renders in Outlook and Gmail) from a brief and file it in Documents for preview. Grounded in the brand kit when one exists. The result can go into the customer's Gmail drafts with create_email_draft or be sent through an app action, both of which ask first. Spends one draft allowance.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | – |
| cta_text | string | – | – |
| cta_url | string | – | – |
| goal | string | yes | – |
| images | array | – | /m/... addresses from generate_image. |
| notes | string | – | – |
| offer | string | – | – |
| preheader | string | – | – |
| sections | array | – | – |
| title | string | yes | The template's name in Documents and the subject line. |
| tone | string | – | – |
No output schema declared.
No examples provided.
write_landing_page Write a landing page ~204
Write a complete, responsive landing page as HTML from a brief and file it in Documents, where the customer previews it. Grounded in the brand kit when one exists. Pass the addresses of pictures you generated so the page uses them. It is private until publish_page. Spends one draft allowance.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | – |
| cta_text | string | – | – |
| cta_url | string | – | – |
| goal | string | yes | What the page must make the reader do, in one sentence. |
| images | array | – | /m/... addresses from generate_image, in the order to use them. |
| notes | string | – | Anything else to honour: colours, length, what to avoid. |
| offer | string | – | – |
| sections | array | – | The sections wanted, in order, each in a few words. |
| title | string | yes | The page's name in Documents and its <title>. |
| tone | string | – | – |
No output schema declared.
No examples provided.
How do I install the Mentionry MCP server?
Mentionry is a hosted endpoint at https://mentionry.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mentionry.com
claude mcp add --transport http com-mentionry-mentionry 'https://mentionry.com/api/mcp'
What is the Mentionry MCP server?
Mentionry is an MCP server listed in the public MCP registry as com.mentionry/mentionry. Find who links to your competitors but not you, judge each opening, and draft the pitch. This page covers its hosted endpoint (https://mentionry.com/api/mcp).
Is the Mentionry MCP server safe to use?
Mentionry scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Mentionry MCP server expose?
Mentionry exposes 19 tools: qualify_domain, read_site, discover_competitors, backlink_gap, find_prospects, and 14 more. Their descriptions and schemas cost roughly 1,914 tokens of context every time the server is loaded.
Does the Mentionry MCP server require authentication?
Yes. Mentionry asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Mentionry MCP server still maintained?
Mentionry is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.