# INITE Visibility (remote · inite.ai)

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

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `inite.ai`: 80/100 (this document), [markdown](https://verifymcp.io/servers/ai-inite-inite-visibility/api-mcp-analyzer.md), [page](https://verifymcp.io/servers/ai-inite-inite-visibility/api-mcp-analyzer)
- npm · `@inite/visibility`: 95/100, [markdown](https://verifymcp.io/servers/ai-inite-inite-visibility/inite-visibility.md), [page](https://verifymcp.io/servers/ai-inite-inite-visibility/inite-visibility)

## Channel facts

- Endpoint: `https://inite.ai/api/mcp/analyzer`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1223 tokens (~94/item across 13 items; 7 tools + 6 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability check failed: schema churn in the 16 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the INITE Visibility MCP server?

INITE Visibility is a hosted endpoint at https://inite.ai/api/mcp/analyzer, 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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "ai-inite-inite-visibility": {
      "url": "https://inite.ai/api/mcp/analyzer"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-inite-inite-visibility": {
      "type": "http",
      "url": "https://inite.ai/api/mcp/analyzer"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-inite-inite-visibility]
url = "https://inite.ai/api/mcp/analyzer"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-inite-inite-visibility": {
      "type": "remote",
      "url": "https://inite.ai/api/mcp/analyzer",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-inite-inite-visibility --url 'https://inite.ai/api/mcp/analyzer' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-inite-inite-visibility:
    url: "https://inite.ai/api/mcp/analyzer"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-inite-inite-visibility": {
      "Transport": "http",
      "Url": "https://inite.ai/api/mcp/analyzer"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-inite-inite-visibility -t streamable-http -u 'https://inite.ai/api/mcp/analyzer'
```

### Other

```json
{
  "mcpServers": {
    "ai-inite-inite-visibility": {
      "type": "http",
      "url": "https://inite.ai/api/mcp/analyzer"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 80, +1)

- [security] Tool “check_identity” rewrote its description, which is the text the model reads
- [security] Tool “inite_connect” rewrote its description, which is the text the model reads
- [cosmetic] “inite_connect” added an optional parameter “all”
- [cosmetic] “visibility_fixes” added an optional parameter “offset”
- [cosmetic] “inite_connect” reworded the description of “for”
- [cosmetic] “visibility_fixes” reworded the description of “limit”

### 2026-11-02 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 24 to 27.

### 2026-10-30 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 14 to 17.

### 2026-10-28 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 11.

### 2026-10-26 (score 76, +1)

- [security] Tool “inite_connect” rewrote its description, which is the text the model reads

### 2026-10-22 (score 75, −1)

- [security regression] Stability: 0.03 → fail
- [security regression] A breaking change shipped without a version bump: still 2.1.0
- [security regression] Tool “watch_site” was removed
- [security regression] Tool “my_reports” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Resource “visibility-watch” was removed
- [functional] New resource “connect”
- [functional] New tool “inite_connect”

### 2026-10-21 (score 76, +12)

- [security improvement] Authorization: unverified → partial
- [security improvement] HSTS header: unverified → pass
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Schema quality: fail → pass
- [functional] The server now declares the “resources” capability
- [functional] The server now declares the “prompts” capability
- [functional] First check of Capabilities: pass
- [functional] First check of Schema quality: 100
- [functional] New prompt “visibility_check”
- [functional] New resource “visibility-history”
- [functional] New resource “visibility-fixes”
- [functional] New resource “visibility-compare”
- [functional] New resource “visibility-audit”
- [functional] New resource “visibility-watch”
- [functional] New resource “visibility-identity”
- [functional] New tool “watch_site”

### 2026-10-20 (score 64)

First indexed and scored.

## MCP tools (7)

### `check_identity` (~131 tokens)

Check how machines read a site

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.

Input parameters:

- `url` (string, required): A public website, e.g. example.com or https://example.com

Output parameters:

- `files` (array)
- `fixes` (array)
- `fixesTotal` (integer)
- `identityScore` (number)
- `organizationSchema` (boolean)
- `retrieval` (object)
- `training` (object)
- `url` (string)

### `analyze_site` (~130 tokens)

Audit a site for AI visibility

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.

Input parameters:

- `url` (string, required): A public website, e.g. example.com or https://example.com

Output parameters:

- `runId` (string)
- `tier` (string)
- `url` (string)

### `get_analysis` (~69 tokens)

Read an audit

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.

Input parameters:

- `run_id` (string, required): The id analyze_site returned

Output parameters:

- `fixes` (array)
- `fixesTotal` (integer)
- `reportUrl` (string|null)
- `score` (number|null)
- `status` (string)
- `url` (string)

### `visibility_fixes` (~161 tokens)

What to fix, in order

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.

Input parameters:

- `limit` (number): Fixes, most important first, per page, default 12
- `offset` (number): The nextOffset of the previous answer
- `url` (string, required): A public website, e.g. example.com or https://example.com

Output parameters:

- `fixes` (array)
- `limit` (integer)
- `matched` (integer)
- `nextOffset` (integer|null)
- `offset` (integer)
- `source` (string)
- `total` (integer)
- `totalIsAtLeast` (boolean)
- `url` (string)

### `compare_sites` (~116 tokens)

Two sites, read the same way

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.

Input parameters:

- `other` (string, required): The site to compare it with, e.g. competitor.com
- `url` (string, required): Your site, e.g. example.com

Output parameters:

- `ahead` (object)
- `sites` (array)

### `visibility_history` (~108 tokens)

How a site's reading moved

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.

Input parameters:

- `url` (string, required): A public website, e.g. example.com or https://example.com

Output parameters:

- `audits` (array)
- `totals` (object)
- `totalsAtLeast` (array)
- `url` (string)
- `weekly` (array)

### `inite_connect` (~115 tokens)

Connect another INITE server

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.

Input parameters:

- `all` (boolean): true: every server, with install links. Ignored with `for`.
- `for` (string): What the person wants next; returns the server that does it

Output parameters:

- `doors` (array)
- `more` (object)
- `others` (array)
- `total` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-inite-inite-visibility/api-mcp-analyzer#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 77
- 2026-10-28: 77
- 2026-10-27: 76
- 2026-10-26: 76
- 2026-10-25: 75
- 2026-10-24: 75
- 2026-10-23: 75
- 2026-10-22: 75
- 2026-10-21: 76
- 2026-10-20: 64

## Common questions

### What is the INITE Visibility MCP server?

INITE Visibility is an MCP server listed in the public MCP registry as ai.inite/inite-visibility. How ChatGPT, Claude, Gemini and Perplexity read a site: free check, fix plan, compare, history. This page covers its hosted endpoint (https://inite.ai/api/mcp/analyzer).

### Is the INITE Visibility MCP server safe to use?

INITE Visibility scores 80 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 INITE Visibility MCP server expose?

INITE Visibility exposes 7 tools: check_identity, analyze_site, get_analysis, visibility_fixes, compare_sites, and 2 more. Their descriptions and schemas cost roughly 830 tokens of context every time the server is loaded.

### Does the INITE Visibility MCP server require authentication?

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

### Is the INITE Visibility MCP server still maintained?

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

## Links

- Remote endpoint: https://inite.ai/api/mcp/analyzer
- Repository: https://github.com/inite-ai/inite-visibility
- Website: https://inite.ai/en/analyze
- Changelog RSS feed: https://verifymcp.io/servers/ai-inite-inite-visibility/api-mcp-analyzer.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-inite-inite-visibility/api-mcp-analyzer.json
- HTML version of this page: https://verifymcp.io/servers/ai-inite-inite-visibility/api-mcp-analyzer