INITE Visibility
REMOTE · INITE.AI · 2 COMPONENTS
How ChatGPT, Claude, Gemini and Perplexity read a site: free check, fix plan, compare, history.
Available components
Last scanned (23 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Marketing and SEO
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 Security80
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1223 tokens (~94/item across 13 items; 7 tools + 6 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management34
- Stability check failed: schema churn in the 15 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
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
- 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
- Supports UI / widget rendering.Pass
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
- 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 security
- “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” cosmetic
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 24 to 27.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 14 to 17.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 11.
- 26 Oct 26 +1
- Tool “inite_connect” rewrote its description, which is the text the model reads security
- 22 Oct 26 −1
- Stability: 0.03 → fail ▼ security
- A breaking change shipped without a version bump: still 2.1.0 ▼ security
- Tool “watch_site” was removed ▼ security
- Tool “my_reports” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Resource “visibility-watch” was removed ▼ functional
- New resource “connect” functional
- New tool “inite_connect” functional
- 21 Oct 26 +12
- Authorization: unverified → partial ▲ security
- HSTS header: unverified → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- 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” functional
- 20 Oct 26 64
First indexed and scored.
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 · Probed https://inite.ai/api/mcp/analyzer
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=inite.ai | CN=WE1,O=Google Trust Services,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 694fd3441fc3275b137bd2f396b00a74 |
| SANs: inite.ai, *.inite.ai | ||||||
| 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 insecure
Validation of inite.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| inite.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://inite.ai/api/mcp/analyzer | Verified | 200 | |
| http (plaintext) | http://inite.ai/api/mcp/analyzer | HTTPS enforced | 301 | https://inite.ai/api/mcp/analyzer |
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 →
analyze_site Audit a site for AI visibility ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | A public website, e.g. example.com or https://example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | – |
| tier | string | yes | – |
| url | string | – | – |
No examples provided.
check_identity Check how machines read a site ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | A public website, e.g. example.com or https://example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | – | – |
| fixes | array | – | – |
| fixesTotal | integer | – | – |
| identityScore | number | yes | – |
| organizationSchema | boolean | – | – |
| retrieval | object | – | – |
| training | object | – | – |
| url | string | yes | – |
No examples provided.
compare_sites Two sites, read the same way ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| other | string | yes | The site to compare it with, e.g. competitor.com |
| url | string | yes | Your site, e.g. example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| ahead | object | – | – |
| sites | array | yes | – |
No examples provided.
get_analysis Read an audit ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | The id analyze_site returned |
| Name | Type | Req | Description |
|---|---|---|---|
| fixes | array | – | – |
| fixesTotal | integer | – | – |
| reportUrl | string|null | – | – |
| score | number|null | – | – |
| status | string | yes | – |
| url | string | – | – |
No examples provided.
inite_connect Connect another INITE server ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | true: every server, with install links. Ignored with `for`. |
| for | string | – | What the person wants next; returns the server that does it |
| Name | Type | Req | Description |
|---|---|---|---|
| doors | array | yes | – |
| more | object | – | – |
| others | array | – | – |
| total | integer | yes | – |
No examples provided.
visibility_fixes What to fix, in order ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Fixes, most important first, per page, default 12 |
| offset | number | – | The nextOffset of the previous answer |
| url | string | yes | A public website, e.g. example.com or https://example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| fixes | array | yes | – |
| limit | integer | – | – |
| matched | integer | – | – |
| nextOffset | integer|null | – | – |
| offset | integer | – | – |
| source | string | yes | – |
| total | integer | yes | – |
| totalIsAtLeast | boolean | – | – |
| url | string | yes | – |
No examples provided.
visibility_history How a site's reading moved ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | A public website, e.g. example.com or https://example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| audits | array | yes | – |
| totals | object | yes | – |
| totalsAtLeast | array | – | – |
| url | string | yes | – |
| weekly | array | yes | – |
No examples provided.
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.
remote · inite.ai
claude mcp add --transport http ai-inite-inite-visibility 'https://inite.ai/api/mcp/analyzer'
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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.