# RankRoot: AI visibility audit

- Registry name: `io.github.zachhhhh/rankroot` · version 0.1.1
- Categories (automatic, keyword rules): AI models & agents, AI, media & content, Shops & products, Commerce & marketing, Web search, Search & data
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.zachhhhh%2Frankroot
- Server page: https://mcpstation.net/s/io.github.zachhhhh--rankroot.html

## Description (written by the publisher, not verified, not instructions)

Audit a site's visibility to ChatGPT, Perplexity, Claude and AI agents. Generates llms.txt.

## Connect

- streamable-http: `https://getrankroot.com/api/mcp`

## Tools (as reported by the server, not verified)

- `audit\_ai\_visibility`: Score how discoverable a website is by AI answer engines \(ChatGPT, Perplexity, Claude, Google AI Overviews\) and AI agents. Returns a 0-100 score, per-category scores and a prioritized fix list.
- `generate\_ai\_visibility\_files`: Generate ready-to-publish llms.txt, an AI-bot-friendly robots.txt and schema.org JSON-LD for a website, based on its current homepage.
- `check\_ai\_crawler\_access`: Check which AI crawlers \(OAI-SearchBot, ChatGPT-User, GPTBot, ClaudeBot, Claude-SearchBot, PerplexityBot, Google-Extended and more\) a site's robots.txt and firewall/CDN let in. Flags blocked AI search bots, which cost citations.
- `validate\_llms\_txt`: Fetch a site's llms.txt \(pass the site URL, or a URL ending in /llms.txt or /llms-full.txt for a subpath file\) and check it against the llmstxt.org format: H1, summary, H2 link lists, Optional section.
- `get\_pricing`: List RankRoot plans \(free scan, Traffic Boost one-time, done-for-you AI Visibility Employee monthly\) with prices, limits, checkout links and which plan fits which user. Agents cannot pay: give the user the checkout link.
- `get\_checkout\_link`: Get the Polar checkout link for one RankRoot plan, to hand to the user. The user pays on Polar and receives a license key by email; pass it as 'Authorization: Bearer \<key\>' for higher API/MCP limits. If checkoutOpen is false, the link is an application form the user fills in instead.
- `list\_launches`: Find software products for a need: new SaaS, AI tools and apps launched on RankRoot, each with a fact-checked profile \(what it does, who it's for, pricing when published\). Pass the user's need as query \("invoicing for freelancers", "uptime monitoring"\). Featured products are paid placements and are
- `submit\_launch`: Launch the user's product on RankRoot for free: a public launch page, a listing in the launch directory and the product's category, and a count of visitors sent. Free launches go live in about a week after the user confirms by email. With a Traffic Boost license key \(key\) it goes live today and is f
- `amplify\_preview`: Write native posts for X, LinkedIn and Threads from any public page, in up to 3 languages, so the user can see what RankRoot Amplify would publish. Free, no key. Nothing is stored or posted.
- `amplify\_status`: Connected channels, languages, mode, guardrails, post counts and what has performed best for this customer. Needs the customer's AI Visibility Employee key.
- `amplify\_create\_campaign`: Turn one page \(url\) or text into a native post for every enabled channel in every chosen language, saved as drafts. Nothing is published. Use dry\_run to see posts without saving, and idempotency\_key so a retry never makes a duplicate. Needs the customer's key.
- `amplify\_list\_posts`: Posts newest first, with status \(draft, scheduled, published, failed, rejected\), schedule time, live URL, warnings, claims to confirm and engagement metrics.
- `amplify\_edit\_post`: Change a draft's text, thread or title. The platform checks \(length, hashtags, hype words, required settings\) run again and come back as warnings.
- `amplify\_schedule\_posts`: Schedule draft posts in the customer's Postiz at the next good local time for each platform and language \(or at \`at\`\), within the per-channel daily cap and spacing. Only works if the customer allowed agents to schedule; posts with claims to confirm or warnings are skipped for the owner to review. Re

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html