INITE Atlas Owners — Claude Code MCP server: what it does

What INITE Atlas Owners does

The server answers a plain question: can an assistant actually find this site? Three tools run on your own machine. check_ai_access reads robots.txt and separates crawlers that fetch a page to answer a live question from those that only gather training data. check_identity_files looks for ten identity files such as llms.txt and ai.json. check_page_signals pulls the title, canonical, hreflang and Schema.org types out of the page's JSON-LD.

The rest lives on inite.ai and answers signed out too. check_identity returns an identity score out of 100 without asking any model. visibility_fixes orders the fixes by importance and shows how many points each should recover. compare_sites reads your site and a competitor's the same way, and visibility_history shows how the reading moved. The audit analyze_site is asynchronous: it hands back a run_id, and get_analysis collects progress and the final score. Two tools instead of one exist because most clients kill a call that blocks too long.

Signed out, the open tools answer under a per-address allowance and the audit runs as a survey, two a day. Signing in ties the audit to your plan: a teaser on free, the full run across four answer engines on paid. The token sits in ~/.config/inite/mcp.json with owner-only permissions, and INITE_TOKEN overrides that file, which is what you want in CI or a container. If your client speaks remote MCP, skip the package and point it at the endpoint directly.