Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MentionedOn Visibility and Website Fixes

REMOTE · MENTIONED-ON.COM

Review supplied AI evidence or OAuth-linked visibility history; prepare and verify website fixes.

Available components

0 this week 88 Trust /100

Last scanned (12 hours ago)

Scores higher than 95% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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 Security83
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1844 tokens (~141/item across 13 items; 13 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 Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 12 Nov 26 +1
    • DNSSEC: fail → pass ▲ security
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “analyze_discovery_readiness” rewrote its description, which is the text the model reads security
    • Tool “build_visibility_action_plan” rewrote its description, which is the text the model reads security
    • Tool “draft_website_fixes” rewrote its description, which is the text the model reads security
    • Tool “get_ai_referrals” rewrote its description, which is the text the model reads security
    • Tool “get_improvement_results” rewrote its description, which is the text the model reads security
    • Tool “get_share_of_voice” rewrote its description, which is the text the model reads security
    • Tool “get_visibility_report” rewrote its description, which is the text the model reads security
    • Tool “get_website_fixes” rewrote its description, which is the text the model reads security
    • Tool “inspect_business_website” rewrote its description, which is the text the model reads security
    • Tool “list_articles” rewrote its description, which is the text the model reads security
    • Tool “list_monitored_businesses” rewrote its description, which is the text the model reads security
    • Tool “summarize_scan_evidence” rewrote its description, which is the text the model reads security
    • Tool “verify_website_fixes” rewrote its description, which is the text the model reads security
    • Schema quality: 109 → 141 ▼ functional
    • Tool coverage: 64% → 93% ▲ functional
    • Schema quality: good → excellent functional
    • Stability: pass → 0.97 functional
    • “draft_website_fixes” reworded the description of “businessType” cosmetic
    • “draft_website_fixes” reworded the description of “confirmed” cosmetic
    • “draft_website_fixes” reworded the description of “facts” cosmetic
    • “draft_website_fixes” reworded the description of “revision” cosmetic
    • “get_visibility_report” reworded the description of “limit” cosmetic
    • “inspect_business_website” reworded the description of “authorizationAcknowledged” cosmetic
    • “inspect_business_website” reworded the description of “revision” cosmetic
    • “verify_website_fixes” reworded the description of “authorizationAcknowledged” cosmetic
    • “verify_website_fixes” reworded the description of “revision” cosmetic
    • “verify_website_fixes” reworded the description of “url” cosmetic
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Stability: 0.97 → pass security
  • 6 Nov 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
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 21 Nov 2026 · Probed https://mentioned-on.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mentioned-on.com CN=WE1,O=Google Trust Services,C=US 8 Oct 2026 6 Jan 2027 ECDSA 256 ECDSA-SHA256 efb285654eb8cc6913a7f083b3ef84ec
SANs: mentioned-on.com, www.mentioned-on.com, *.www.mentioned-on.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 secure

Validation of mentioned-on.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
mentioned-on.com. DS published 2371 13 Verified
mentioned-on.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000
content-security-policy default-src 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy browsing-topics=(), camera=(), geolocation=(), microphone=(), payment=(), usb=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mentioned-on.com/mcp Verified 200
http (plaintext) http://mentioned-on.com/mcp HTTPS enforced 301 https://mentioned-on.com/mcp
MCP tools · 13 exposed · ~1,637 tokens

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 →

Tool Tokens
analyze_discovery_readiness ~143

Use when the user has no account: scores signals you collect yourself (schema present, name/address/phone consistency, profiles, reviews) for AI discovery readiness. Returns a score, the gaps in priority order and what still needs verifying. Free; it does not fetch the website, run a scan, store anything or confirm inclusion in any AI product.

NameTypeReqDescription
businessNamestringyesThe business name used only to label this assessment.
signalsarrayyesCaller-supplied signal observations. Omitted signals are treated as unknown.
websiteUrlstring–Optional page URL used only as a label. The tool will not fetch this URL.
NameTypeReqDescription
assessmentstringyes–
businessNamestringyes–
evaluatedSignalsarrayyes–
evidenceCoveragePercentnumberyes–
limitationsarrayyes–
minimumCoveragePercentnumberyes–
prioritiesarrayyes–
readinessScore–yesWeighted score over observed signals only. Null when no signal was observed or evidence coverage is below minimumCoveragePercent.
scopestringyes–
scoreBasisstringyes–
scoreStatusstringyes–
verificationNeededarrayyes–
websiteUrl–yes–

No examples provided.

build_visibility_action_plan ~137

Use after analyze_discovery_readiness, or with findings you already have: turns them into a short ordered list of fixes for one goal and effort budget, with the reason and a check for each. Free; it does not edit a website, contact anyone, store data or promise rankings or mentions.

NameTypeReqDescription
businessNamestringyes–
effortBudgetstringyesControls how many actions are returned and how they are phased.
findingsarrayyesCaller-supplied findings. Present findings are acknowledged but do not create actions.
goalstringyesThe outcome used to break ties in the deterministic priority rubric.
NameTypeReqDescription
actionsarrayyes–
businessNamestringyes–
effortBudgetstringyes–
excludedPresentSignalsarrayyes–
goalstringyes–
goalLabelstringyes–
limitationsarrayyes–
omittedActionCountintegeryes–
scopestringyes–

No examples provided.

draft_website_fixes ~189

Needs a connected MentionedOn account with a paid or 7-day trial monitoring slot (Local is $99/month). Use after the user confirms the facts from inspect_business_website: generates and saves business schema, website copy and a business-profile description from those facts only. Pass the current revision and confirmed: true; never invent missing facts. Saves a new revision; no AI model cost, nothing is published or sent.

NameTypeReqDescription
businessIdstringyesBusiness id returned by list_monitored_businesses.
businessTypestringyesschema.org business type for the generated schema.
confirmedbooleanyestrue once the user has reviewed and confirmed these facts.
factsobjectyesBusiness facts the user confirmed, from the inspection.
revisionintegeryesInteger from get_website_fixes (the current saved revision); use 0 when no record exists.
NameTypeReqDescription
businessIdstringyes–
limitationsarrayyes–
nextStepstringyes–
record–yes–

No examples provided.

get_ai_referrals ~96

Needs a connected MentionedOn account. Use for 'are people arriving from ChatGPT?': returns the last 30 days of website visits that came from AI assistants, by assistant and landing page, and the install snippet when one has been issued. Needs businessId. Read-only. Counts are a floor: some assistants send no referrer.

NameTypeReqDescription
businessIdstringyesBusiness id returned by list_monitored_businesses.
NameTypeReqDescription
businessIdstringyes–
installedbooleanyes–
limitationsarrayyes–
nextStepstringyes–
snippet–yes–
summaryobjectyes–

No examples provided.

get_improvement_results ~117

Needs a connected MentionedOn account. Use for 'did my new page work?': returns the question being improved, the page published for it, and before/after evidence: saved assistant answers in equal windows either side of publication (same settings only), any Google AI Overview follow-up, and AI-referred visits to that page. Needs businessId. Read-only; runs no scan. A change after publication does not prove the page caused it.

NameTypeReqDescription
businessIdstringyesBusiness id returned by list_monitored_businesses.
NameTypeReqDescription
aiVisitors–yes–
assistants–yes–
businessIdstringyes–
googleAiOverview–yes–
improvement–yes–
limitationsarrayyes–
nextStepstringyes–
reportUrlstringyes–

No examples provided.

get_share_of_voice ~101

Needs a connected MentionedOn account. Use for 'who does AI recommend instead of us?': returns how often saved answers name this business versus every other business they name, its rank over saved checks, and the kinds of sites cited (own site, directories, community, press, competitors). Needs businessId. Read-only; built from saved checks, no scan.

NameTypeReqDescription
businessIdstringyesBusiness id returned by list_monitored_businesses.
NameTypeReqDescription
businessIdstringyes–
capturedAt–yes–
citationMixobjectyes–
limitationsarrayyes–
reportUrlstringyes–
shareOfVoiceobjectyes–

No examples provided.

get_visibility_report ~140

Needs a connected MentionedOn account. Use when the user asks how their business shows up in AI answers: returns the latest saved check (score, mention and citation rates, answer excerpts per assistant, competitors, cited sources) and up to 30 earlier checks, with dates, provider gaps and a score change only when checks are comparable. Needs businessId from list_monitored_businesses. Read-only; runs no new scan, so results are dated, not live.

NameTypeReqDescription
businessIdstringyesBusiness id returned by list_monitored_businesses.
limitinteger–How many saved checks to return, newest first (default 30).
NameTypeReqDescription
baseline–yes–
businessobjectyes–
byModelarrayyes–
competitorsarrayyes–
evidencearrayyes–
evidenceTruncatedbooleanyes–
historyarrayyes–
improvement–yes–
improvementHistoryarrayyes–
latest–yes–
limitationsarrayyes–
nextStepstringyes–
recommendationsarrayyes–
reportUrlstringyes–
scoreChange–yes–
statusstringyes–

No examples provided.

get_website_fixes ~102

Needs a connected MentionedOn account. Use after inspect_business_website to see the current revision of saved facts, schema and copy, and whether each fix is installed. Needs businessId from list_monitored_businesses. Read-only; returns the revision number you must pass to draft_website_fixes (and to inspect_business_website and verify_website_fixes).

NameTypeReqDescription
businessIdstringyesBusiness id returned by list_monitored_businesses.
NameTypeReqDescription
businessIdstringyes–
limitationsarrayyes–
nextStepstringyes–
record–yes–

No examples provided.

inspect_business_website ~182

Needs a connected MentionedOn account with a paid or 7-day trial monitoring slot (Local is $99/month). Use first when fixing business information: fetches a few public pages of the saved business website and saves candidate facts with where each was found. Pass revision from get_website_fixes (0 if none) and authorizationAcknowledged: true once the user confirms they own the site. Saves a new revision; refused once drafts exist; up to 20 website checks a day. Runs no AI scan and publishes nothing.

NameTypeReqDescription
authorizationAcknowledgedbooleanyestrue once the user confirms they own or may inspect this website.
businessIdstringyesBusiness id returned by list_monitored_businesses.
revisionintegeryesInteger from get_website_fixes (the current saved revision); use 0 when no record exists.
NameTypeReqDescription
businessIdstringyes–
limitationsarrayyes–
nextStepstringyes–
record–yes–

No examples provided.

list_articles ~98

Needs a connected MentionedOn account. Use to fetch drafted articles: returns up to 20 recent drafts with the questions each targets, the buyer it was written for and the Markdown (first 4,000 characters), plus this month's usage. Needs businessId. Read-only; new drafts are made in MentionedOn and count against the plan's monthly allowance.

NameTypeReqDescription
businessIdstringyesBusiness id returned by list_monitored_businesses.
NameTypeReqDescription
articlesarrayyes–
businessIdstringyes–
limitationsarrayyes–
reportUrlstringyes–
usedThisMonthnumberyes–

No examples provided.

list_monitored_businesses ~67

Needs a connected MentionedOn account. Start here: lists the businesses in the account with each one's id and monitoring status, or a setup link when there are none. Pass the id as businessId to the other tools. Read-only; starts no scan, trial or charge.

Input schema present but exposes no named parameters.

NameTypeReqDescription
businessesarrayyes–
nextStepstringyes–
setupUrlstringyes–

No examples provided.

summarize_scan_evidence ~102

Use when you captured AI answers yourself: calculates how often the business is mentioned and how often its own site is cited, overall and per assistant, with the statements that support each number. Free; it does not call AI providers, fetch URLs or store anything, and it says nothing beyond the answers supplied.

NameTypeReqDescription
businessNamestringyes–
observationsarrayyesPoint-in-time captures supplied by the caller. The tool will not obtain new captures.
NameTypeReqDescription
businessCitationCountintegeryes–
businessCitationRatePercent–yes–
businessNamestringyes–
bySourcearrayyes–
completedCountintegeryes–
establishesLiveInclusionbooleanyes–
evidenceStatementsarrayyes–
limitationsarrayyes–
mentionCountintegeryes–
mentionRatePercent–yes–
observationCountintegeryes–
observedAtRange–yes–
scopestringyes–
sentimentBreakdownobjectyes–
unavailablearrayyes–
unavailableCountintegeryes–
uniqueBusinessCitationHostsarrayyes–

No examples provided.

verify_website_fixes ~163

Needs a connected MentionedOn account with a paid or 7-day trial monitoring slot (Local is $99/month). Use after the user installs the fixes: fetches one page on the business's own website and checks it for the saved schema and text, saving found, not-found or unknown results against that revision. Up to 20 website checks a day. A found fix does not prove better AI visibility.

NameTypeReqDescription
authorizationAcknowledgedbooleanyestrue once the user confirms they own or may check this website.
businessIdstringyesBusiness id returned by list_monitored_businesses.
revisionintegeryesInteger from get_website_fixes.
urlstringyesPage on the owned domain where the fixes are installed.
NameTypeReqDescription
businessIdstringyes–
limitationsarrayyes–
nextStepstringyes–
record–yes–

No examples provided.

Install

How do I install the MentionedOn Visibility and Website Fixes MCP server?

MentionedOn Visibility and Website Fixes is a hosted endpoint at https://mentioned-on.com/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 · mentioned-on.com

# add to Claude Code
claude mcp add --transport http com-mentioned-on-ai-discovery-readiness 'https://mentioned-on.com/mcp'
Common questions

What is the MentionedOn Visibility and Website Fixes MCP server?

MentionedOn Visibility and Website Fixes is an MCP server listed in the public MCP registry as com.mentioned-on/ai-discovery-readiness. Review supplied AI evidence or OAuth-linked visibility history; prepare and verify website fixes. This page covers its hosted endpoint (https://mentioned-on.com/mcp).

Is the MentionedOn Visibility and Website Fixes MCP server safe to use?

MentionedOn Visibility and Website Fixes scores 88 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 MentionedOn Visibility and Website Fixes MCP server expose?

MentionedOn Visibility and Website Fixes exposes 13 tools: analyze_discovery_readiness, build_visibility_action_plan, summarize_scan_evidence, list_monitored_businesses, get_visibility_report, and 8 more. Their descriptions and schemas cost roughly 1,637 tokens of context every time the server is loaded.

Does the MentionedOn Visibility and Website Fixes MCP server require authentication?

No. We connected to MentionedOn Visibility and Website Fixes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the MentionedOn Visibility and Website Fixes MCP server still maintained?

MentionedOn Visibility and Website Fixes is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the MentionedOn Visibility and Website Fixes MCP server?

VerifyMCP ran 13 checks on MentionedOn Visibility and Website Fixes, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.