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.

io.github.sharozdawa/ai-visibility

NPM · AI-VISIBILITY-MCP

Track brand visibility across ChatGPT, Perplexity, Claude, and Gemini.

Available components

0 this week 85 Trust /100

Last scanned (22 hours ago)

Scores higher than 87% of npm servers

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 415 tokens (~69/item across 6 items; 6 tools + 0 resources), lean.Pass
  • 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
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.

  • 4 Nov 26 +1
    • Stability: 0.97 → pass security
  • 3 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
  • 26 Oct 26 −1
    • Stability: pass → 0.93 functional
  • 20 Oct 26 +1
    • Stability: 0.97 → pass security
  • 19 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.87 → pass security
  • 16 Oct 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.

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 4 Nov 2026 · Analysed npm/ai-visibility-mcp@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~415 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
check_brand_visibility ~106

Check a brand's visibility across AI platforms (ChatGPT, Perplexity, Claude, Gemini). Simulates realistic queries and analyzes mention rates, positions, sentiment, and competitor landscape.

NameTypeReqDescription
brandstringyesThe brand name to check visibility for
keywordsarray–Industry keywords related to the brand (e.g., ['SEO', 'analytics']). Used to generate relevant queries.
platformsarray–Which AI platforms to check. Defaults to all four platforms.

No output schema declared.

No examples provided.

check_single_query ~89

Check if a brand is mentioned for a specific query on a specific AI platform. Returns mention status, position, context snippet, sentiment, and competitor mentions.

NameTypeReqDescription
brandstringyesThe brand name to check
platformstringyesThe AI platform to check on
querystringyesThe exact query to check (e.g., 'What are the best SEO tools?')

No output schema declared.

No examples provided.

compare_brands ~69

Compare the AI visibility of multiple brands side by side. Shows per-platform scores, overall rankings, and relative strengths.

NameTypeReqDescription
brandsarrayyesList of brand names to compare (2-10 brands)
keywordstring–Optional industry keyword for context (e.g., 'project management')

No output schema declared.

No examples provided.

get_recommendations ~76

Get actionable recommendations to improve a brand's AI visibility. Prioritized suggestions based on current score and industry best practices.

NameTypeReqDescription
brandstringyesThe brand name to get recommendations for
current_scorenumber–Current visibility score (0-100) if known. If not provided, a quick check will be performed.

No output schema declared.

No examples provided.

get_visibility_score ~50

Calculate an overall AI visibility score (0-100) for a brand across all four AI platforms. Includes per-platform breakdowns and improvement recommendations.

NameTypeReqDescription
brandstringyesThe brand name to score

No output schema declared.

No examples provided.

list_platforms ~25

List all supported AI platforms with details about how each sources and presents brand information.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.sharozdawa/ai-visibility MCP server?

io.github.sharozdawa/ai-visibility runs locally as an npm package, launched with npx -y ai-visibility-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · ai-visibility-mcp

# add to Claude Code
claude mcp add sharozdawa-ai-visibility -- npx -y ai-visibility-mcp
Common questions

What is the io.github.sharozdawa/ai-visibility MCP server?

io.github.sharozdawa/ai-visibility is an MCP server listed in the public MCP registry as io.github.sharozdawa/ai-visibility. Track brand visibility across ChatGPT, Perplexity, Claude, and Gemini. This page covers its npm package (ai-visibility-mcp).

Is the io.github.sharozdawa/ai-visibility MCP server safe to use?

io.github.sharozdawa/ai-visibility scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. 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 io.github.sharozdawa/ai-visibility MCP server expose?

io.github.sharozdawa/ai-visibility exposes 6 tools: check_brand_visibility, check_single_query, get_visibility_score, compare_brands, get_recommendations, list_platforms. Their descriptions and schemas cost roughly 415 tokens of context every time the server is loaded.

Is the io.github.sharozdawa/ai-visibility MCP server still maintained?

io.github.sharozdawa/ai-visibility is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.sharozdawa/ai-visibility MCP server under?

io.github.sharozdawa/ai-visibility declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.