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.

INITE AI Visibility

NPM · @INITE/VISIBILITY · 2 COMPONENTS · SCANNED SEP 20

See how ChatGPT, Claude, Gemini and Perplexity read any website. Scored out of 100.

+3 this week 77 Trust /100
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
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 236 tokens (~78/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
Install

How do I install the INITE AI Visibility MCP server?

INITE AI Visibility runs locally as an npm package, launched with npx -y @inite/visibility. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @inite/visibility

# add to Claude Code
claude mcp add ai-inite-inite-visibility -- npx -y @inite/visibility
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-inite-inite-visibility": {
      "command": "npx",
      "args": [
        "-y",
        "@inite/visibility"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-inite-inite-visibility": {
      "command": "npx",
      "args": [
        "-y",
        "@inite/visibility"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add ai-inite-inite-visibility -- npx -y @inite/visibility
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-inite-inite-visibility": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@inite/visibility"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-inite-inite-visibility --command npx --arg -y --arg @inite/visibility
# ~/.hermes/config.yaml
mcp_servers:
  ai-inite-inite-visibility:
    command: "npx"
    args: ["-y", "@inite/visibility"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-inite-inite-visibility": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@inite/visibility"
      ]
    }
  }
}
# add to Vellum
assistant mcp add ai-inite-inite-visibility -t stdio -c npx -a -y @inite/visibility
// mcp.json
{
  "mcpServers": {
    "ai-inite-inite-visibility": {
      "command": "npx",
      "args": [
        "-y",
        "@inite/visibility"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +4
    • Stability: unverified → 0.23 functional
  • 7 Sept 26 +15
    • Malware scan: unverified → pass security
  • 6 Sept 26 55

    First indexed and scored.

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 20 Sept 2026 · Analysed npm/@inite/visibility@1.1.2

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 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~236 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_ai_access ~91

Read a site's robots.txt and say which AI crawlers may fetch it, separating the ones that retrieve pages to answer live questions from the ones that only collect training data. Blocking the first kind is what makes a site invisible in AI answers; blocking the second costs nothing. Runs locally, no account needed.

NameTypeReqDescription
urlstringyesA public site, e.g. example.com or https://example.com

No output schema declared.

No examples provided.

check_identity_files ~69

Probe a site for the identity files an AI engine may look for — llms.txt, ai.json, identity.json and the rest — and report which exist. Runs locally, no account needed.

NameTypeReqDescription
urlstringyesA public site, e.g. example.com or https://example.com

No output schema declared.

No examples provided.

check_page_signals ~76

Read a site's homepage and report the signals an engine uses to work out what it is: title, description, canonical, hreflang and the Schema.org types in its JSON-LD. Runs locally, no account needed.

NameTypeReqDescription
urlstringyesA public site, e.g. example.com or https://example.com

No output schema declared.

No examples provided.

Common questions

What is the INITE AI Visibility MCP server?

INITE AI Visibility is an MCP server listed in the public MCP registry as ai.inite/inite-visibility. See how ChatGPT, Claude, Gemini and Perplexity read any website. Scored out of 100. This page covers its npm package (@inite/visibility).

Is the INITE AI Visibility MCP server safe to use?

INITE AI Visibility scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 INITE AI Visibility MCP server expose?

INITE AI Visibility exposes 3 tools: check_ai_access, check_identity_files, check_page_signals. Their descriptions and schemas cost roughly 236 tokens of context every time the server is loaded.

Is the INITE AI Visibility MCP server still maintained?

INITE AI Visibility is still listed as active in the MCP registry. We last reached this channel on 20 September 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 INITE AI Visibility MCP server under?

INITE 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.