Skip to main content
Glama
README.md
# AnswerRail MCP Server (`answerrail-mcp`)

[![npm version](https://img.shields.io/npm/v/answerrail-mcp.svg)](https://www.npmjs.com/package/answerrail-mcp)
[![Glama MCP Score](https://glama.ai/mcp/servers/quitegoodproject/answerrail-mcp/badges/score.svg)](https://glama.ai/mcp/servers/quitegoodproject/answerrail-mcp)
[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)

Official Model Context Protocol (MCP) server for **AnswerRail** ([https://answerrail.com](https://answerrail.com)) — available both as a **local stdio server** (`npx -y answerrail-mcp`) and a **zero-install Remote Streamable HTTP server** (`https://answerrail.com/mcp`).

Audit any domain or URL directly inside Claude Desktop, Claude Code, Cursor, Windsurf, or any MCP client for:
- **AI Crawler Readiness** (`PerplexityBot`, `OAI-SearchBot`, `GPTBot`, `ClaudeBot`, `Google-Extended`)
- **25,000-Token RAG Truncation Cliff** detection & dropped pricing token diagnostics
- **`/llms.txt` & `/llms-full.txt` Documentation Index** verification & compilation
- **Google Lighthouse 13.5 `agentic-browsing`** (`/.well-known/ai-catalog.json` ARD 1.0 schema & `robots.txt` `Agentmap:` directive)
- **Byte-0 AST De-bloating** (converting heavy React/Next.js/Shopify DOM bloat into clean GitHub-Flavored Markdown)

---

## Tools Included (v1.0.2)

### 1. `audit_ai_readiness`
Perform a live, read-only diagnostic audit of a website URL or domain for AI search readiness, measuring HTML token weight against the 25,000-token RAG truncation limit, `/llms.txt` manifest availability, Google Lighthouse 13.5 `/.well-known/ai-catalog.json` (ARD 1.0) conformance, `robots.txt` `Agentmap:` directives, and Schema.org JSON-LD entities.
- **Input:** `url` (string, e.g. `https://stripe.com/pricing` or `example.com`)

### 2. `generate_ai_manifests`
Generate ready-to-deploy `/llms.txt` Markdown and Google Lighthouse 13.5 `/.well-known/ai-catalog.json` (ARD 1.0) JSON manifests for a target domain, plus `robots.txt` `Agentmap:` and HTML `<head>` discovery `<link>` tags.
- **Input:** `domain` (string, e.g. `example.com`)

### 3. `extract_byte0_markdown`
Fetch a live web page, strip React/Next.js hydration chunks, Shopify Liquid DOM bloat, scripts, and navigation cruft, and return clean Byte-0 GitHub-Flavored Markdown (GFM) alongside before/after token telemetry.
- **Input:** `url` (string, e.g. `https://example.com/pricing`)

### 4. `query_truncation_benchmark`
Query empirical data from the 2026 50-Site B2B SaaS Pricing Page Truncation Benchmark (`87%` publish `/llms.txt`, yet `74%` still truncate `/pricing` HTML past 25,000 tokens).
- **Input:** `domain` (optional string, e.g. `vercel.com`, `supabase.com`, or omit for full cohort summary)

---

## Quickstart & Installation

### Option A: Zero-Install Remote HTTP Server (`https://answerrail.com/mcp`)

**Claude Code CLI:**
```bash
claude mcp add --transport http answerrail https://answerrail.com/mcp
```

**Cursor / Windsurf / Remote HTTP Clients:**
```json
{
  "mcpServers": {
    "answerrail": {
      "url": "https://answerrail.com/mcp"
    }
  }
}
```

### Option B: Local Stdio Server (`npx -y answerrail-mcp`)

**Claude Desktop (`claude_desktop_config.json`) / Cursor / Windsurf:**
```json
{
  "mcpServers": {
    "answerrail": {
      "command": "npx",
      "args": ["-y", "answerrail-mcp"]
    }
  }
}
```

---

## Links
- **Official Website:** [https://answerrail.com](https://answerrail.com)
- **Remote MCP Endpoint:** [https://answerrail.com/mcp](https://answerrail.com/mcp)
- **Glama Registry:** [https://glama.ai/mcp/servers/quitegoodproject/answerrail-mcp](https://glama.ai/mcp/servers/quitegoodproject/answerrail-mcp)
- **50-Site Empirical Benchmark:** [https://answerrail.com/research/2026-saas-50-truncation-benchmark](https://answerrail.com/research/2026-saas-50-truncation-benchmark)

License: MIT

TDQS

A4.4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct action (audit, generate, extract, query) and the descriptions explicitly cross-reference when to use alternatives, e.g. 'do not use this tool... use extract_byte0_markdown instead.' An agent can unambiguously select the right tool.

Naming Consistency5/5

All four names follow a consistent snake_case verb_noun pattern: audit_ai_readiness, generate_ai_manifests, extract_byte0_markdown, query_truncation_benchmark. The branded 'byte0' infix is a minor quirk but the pattern holds throughout.

Tool Count4/5

Four tools is on the lean side but each is clearly scoped and earns its place: diagnostic, synthesis, extraction, and benchmark lookup. Reasonable for the narrow AI-readiness domain, though slightly thin.

Completeness4/5

The surface covers the core lifecycle: audit readiness, generate remediation manifests, extract content, and compare against benchmarks. Minor gaps exist (e.g. validating post-remediation or re-running checks), but core workflows are covered without dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues