All servers · AI models & agents · Shops & products · Web search
RankRoot: AI visibility audit
io.github.zachhhhh/rankroot · v0.1.1
Tools changed (7 days)
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Can write (some tools are not declared read-only) |
| Capabilities declared | tools |
| Tool definitions | 14 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Audit a site's visibility to ChatGPT, Perplexity, Claude and AI agents. Generates llms.txt.
Connect
streamable-http · https://getrankroot.com/api/mcp
claude mcp add --transport http rankroot https://getrankroot.com/api/mcp{
"mcpServers": {
"rankroot": {
"url": "https://getrankroot.com/api/mcp"
}
}
}Tools as reported by the server
audit_ai_visibilityScore 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_filesGenerate 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_accessCheck 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_txtFetch 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_pricingList 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_linkGet 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_launchesFind 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 aresubmit_launchLaunch 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 famplify_previewWrite 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_statusConnected channels, languages, mode, guardrails, post counts and what has performed best for this customer. Needs the customer's AI Visibility Employee key.amplify_create_campaignTurn 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_postsPosts newest first, with status (draft, scheduled, published, failed, rejected), schedule time, live URL, warnings, claims to confirm and engagement metrics.amplify_edit_postChange 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_postsSchedule 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
Tool changes
- 2026-10-24: audit_ai_visibility, generate_ai_visibility_files, check_ai_crawler_access, validate_llms_txt, get_pricing, get_checkout_link, list_launches, submit_launch, amplify_preview, amplify_status, amplify_create_campaign, amplify_list_posts
- 2026-10-23: audit_ai_visibility, generate_ai_visibility_files, check_ai_crawler_access, validate_llms_txt, get_pricing, get_checkout_link, amplify_preview, amplify_status, amplify_create_campaign, amplify_list_posts, amplify_edit_post, amplify_schedule_posts
- 2026-10-21: audit_ai_visibility, generate_ai_visibility_files, check_ai_crawler_access, validate_llms_txt, get_pricing, get_checkout_link
- 2026-10-16: audit_ai_visibility, generate_ai_visibility_files
Website · JSON · Text for agents · Registry updated 2026-10-07