Skip to content

INITE Visibility MCP server

ai.inite/inite-visibilityinite.aistreamable-httpv2.1.0Scanned

How ChatGPT, Claude, Gemini and Perplexity read a site: free check, fix plan, compare, history.

7 tools: 5 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 5 write, 2 read.
  • Reads private data · 2
  • Reads text others write · 4
  • Can send data out · 5
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the INITE Visibility MCP server can do

The INITE Visibility MCP server is published by inite.ai, a domain the MCP Registry verified. It has 7 tools. It can create or change data (5 tools: check_identity, analyze_site, visibility_fixes, visibility_history and 1 more), but cannot delete data. 2 tools only read.

2 tools read private data (analyze_site and compare_sites); 4 tools bring in text other people can write (check_identity, analyze_site, visibility_fixes and 1 more); 5 tools can send data out of your system (check_identity, analyze_site, visibility_fixes and 2 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 2.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 5Claude Code: ask
  • analyze_siteThe AI visibility audit: the identity files, crawler policy, schema graph and page health, then the answer engines asked whether they name the site, scored out of 100.Reads private dataReads text others writeCan send data out1 finding

    Why it is in this group

    • The name "analyze_site" says "analyze": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "analyze_site" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "analyze_site" says "analyze": a word for reading.

      What this check looks for
    Description, as the server wrote it
    The AI visibility audit: the identity files, crawler policy, schema graph and page health, then the answer engines asked whether they name the site, scored out of 100. Starts a run and returns its run_id; it takes about a minute, so call get_analysis with that id. Without an account it runs the survey (the audit without its two paid steps), two a day per address; a free account gets the teaser, a paid plan the whole audit, on the account's own allowance.

    Annotations the server declares

    • title: Audit a site for AI visibility
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • check_identityFree and instant, no account: read a website the way an AI engine does before it answers about it.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Free and instant, no account: read a website the way an AI engine does before it answers about it. Returns which answer-engine crawlers robots.txt lets in (retrieval, which decides whether the site can be cited) and which training crawlers it blocks (which costs nothing), the identity files present, whether the homepage carries Organization schema, an identity score out of 100, and the fixes that reading names. No model is asked; for whether the engines actually name the site, run analyze_site.

    Annotations the server declares

    • title: Check how machines read a site
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • inite_connectHow to add another INITE MCP server to this client, when the person wants something this one does not do.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    How to add another INITE MCP server to this client, when the person wants something this one does not do. With no argument, the server beside this one; `for`, the one that does a job; `all: true`, every server. Returns the URL, the Claude Code command and the custom-connector step.

    Annotations the server declares

    • title: Connect another INITE server
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • visibility_fixesThe fix plan for a site's AI visibility, most important first: what to change, why it matters for being named in AI answers, how many points of the score it should recover, the pag…Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    The fix plan for a site's AI visibility, most important first: what to change, why it matters for being named in AI answers, how many points of the score it should recover, the pages it applies to, and a paste-ready file or snippet when there is one (llms.txt, robots.txt rules, Organization schema). Free from the identity reading, no account; signed in, it is built from your latest finished audit of that site, which covers the answer engines too.

    Annotations the server declares

    • title: What to fix, in order
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • visibility_historyHow a site's AI visibility reading has moved over time: for a site in the INITE Atlas, its weekly readings (identity score, answer-engine crawlers let in, llms.txt, Organization sc…Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    How a site's AI visibility reading has moved over time: for a site in the INITE Atlas, its weekly readings (identity score, answer-engine crawlers let in, llms.txt, Organization schema, the top fix each week); signed in, your own audits of it too, with their scores. Free, no model, and no check is spent: it reads what was already measured.

    Annotations the server declares

    • title: How a site's reading moved
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • compare_sitesYour site against a competitor's, read the way an AI engine reads them before it answers: identity score out of 100, which answer-engine crawlers each lets in, the identity files e…Reads private dataReads text others writeCan send data outNo findings

    Why it is in this group

    • The name "compare_sites" says "compare": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Your site against a competitor's, read the way an AI engine reads them before it answers: identity score out of 100, which answer-engine crawlers each lets in, the identity files each has (llms.txt, ai.json and the rest), Organization schema, and where each one is ahead. Free and instant, no model asked; counts two identity checks.

    Annotations the server declares

    • title: Two sites, read the same way
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_analysisRead an audit started by analyze_site: progress while it runs, then the score out of 100 and what to fix first.No findings

    Why it is in this group

    • The name "get_analysis" says "get": a word for reading.
    Description, as the server wrote it
    Read an audit started by analyze_site: progress while it runs, then the score out of 100 and what to fix first. Only the caller who started the run can read it - the account, or for a guest the same address.

    Annotations the server declares

    • title: Read an audit
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

40 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 private-data tools breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out5
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__inite-visibility__analyze_site",
      "mcp__inite-visibility__compare_sites"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:23 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://inite.ai/.well-known/oauth-protected-resource/api/mcp/analyzer
Authorization servers
https://auth-api.inite.ai
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://inite.ai/api/mcp/analyzer: tools/list returned 7 tools to an anonymous client, including check_identity (write), analyze_site (write), visibility_fixes (write), visibility_history (write), inite_connect (write)

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Client ID metadata documents: no to yes

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "analyze_site" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "analyze_site" says "analyze": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Client ID metadata documents: no -> yes.View diff
    • Client ID metadata documents: no to yes
  2. Tools3 changed.~3 changedView diff

Install

Pinned to version 2.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http inite-visibility https://inite.ai/api/mcp/analyzer
claude mcp add --transport http inite-visibility https://inite.ai/api/mcp/analyzer

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__inite-visibility__get_analysis"
    ],
    "ask": [
      "mcp__inite-visibility__check_identity",
      "mcp__inite-visibility__analyze_site",
      "mcp__inite-visibility__visibility_fixes",
      "mcp__inite-visibility__compare_sites",
      "mcp__inite-visibility__visibility_history",
      "mcp__inite-visibility__inite_connect"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as inite-visibility. Review it before you use it.

Capability tags behind 5 rules
  • mcp__inite-visibility__check_identity untrusted-input, outbound
  • mcp__inite-visibility__analyze_site private-data, untrusted-input, outbound
  • mcp__inite-visibility__visibility_fixes untrusted-input, outbound
  • mcp__inite-visibility__compare_sites private-data, untrusted-input, outbound
  • mcp__inite-visibility__visibility_history outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.inite/inite-visibility/verify?hash=ffeea0f61ebb4d32d8e08eedc4b0d1e526ec9efbd9ba4df04084ea69c8f7fe6f" | jq -e '.changed == false'

Pinned hash ffeea0f61ebb, from Nov 17, 2026, 06:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.inite/inite-visibility/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.inite/inite-visibility
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.inite/inite-visibility.svg)](https://radar.anlyon.com/servers/ai.inite/inite-visibility)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:41 UTC.

INITE Visibility MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the INITE Visibility MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the INITE Visibility MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the INITE Visibility MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the INITE Visibility MCP server have?

7 tools: 5 write, 2 read. check_identity, analyze_site, visibility_fixes, visibility_history, inite_connect, get_analysis and compare_sites.

Does the INITE Visibility MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the INITE Visibility MCP server send data to outside services?

5 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_identity, analyze_site, visibility_fixes, compare_sites and visibility_history.

Has the INITE Visibility MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 3, 2026. Every change is on this page and in its Atom feed.