Back to MCP servers

Glintbase

https://glintbase.dev/api/mcp
● healthy

# Glintbase MCP Server (ARS 3.0) **Glintbase** is the open audit and simulation standard for the autonomous AI agent web. It gives AI coding agents (Claude Code, Cursor, Windsurf, Devin, Antigravity) empirical visibility into whether a website, developer portal, or API is truly agent-ready—or full of silent friction, 404 traps, and schema hallucinations. Built on the **Agent Readiness Score (ARS 3.0)** specification, this MCP server provides instant surface discovery, lightweight scorecards, flight simulation with visual SVG telemetry, and 9 bundled remediation playbooks. --- ## ✨ Features - **Empirical ARS 3.0 Scoring**: Evaluates domains across 6 core pillars: *Discovery*, *Access*, *Usability*, *Semantic*, *Architecture*, and *Safety*. - **Machine Surface Discovery**: Automatically detects and validates `robots.txt` AI policies, `/llms.txt`, `/llms-full.txt`, `/.well-known/ard.json`, `/auth.md`, and OpenAPI specifications. - **Visual Flight Simulator**: Simulates synthetic coding personas (Claude Code, Cursor, Perplexity) executing developer journeys, outputting visual SVG journey trees, schema friction metrics, and token-tax telemetry. - **Context-Preserving Scores**: Fetch ultra-compact scorecards in under 200 tokens to preserve agent context windows during automated workflows. - **9 Bundled Playbooks**: Instant access to complete ARS 3.0 remediation manuals (living artifacts, WorkOS auth contracts, streamable MCP servers, and CI gates). --- ## 🛠️ Tools | Tool | Parameters | Description | | :--- | :--- | :--- | | `glintbase_audit` | `target` (string) | Runs a complete 119-check ARS 3.0 audit on any target URL. Returns detailed layer breakdowns, passed/failed checks, and actionable remediation diffs. | | `glintbase_get_score` | `target` (string) | Returns an ultra-compact score card (<200 tokens) with letter grade, archetype classification, and layer scores. Ideal for rapid CI checks. | | `glintbase_discover_surfaces` | `target` (string) | Scans and maps all machine entrypoints (`robots.txt`, `llms.txt`, `ard.json`, `auth.md`, OpenAPI, sitemap). | | `glintbase_simulate_flight` | `target` (string), `persona` (enum: `claude-code`, `cursor`, `perplexity`), `intent` (string) | Runs an autonomous mission simulation. Returns step-by-step navigation telemetry, token consumption, and a visual SVG journey tree graphic. | | `glintbase_get_skill` | `skillName` (string) | Retrieves full, multi-step ARS 3.0 remediation playbooks (e.g. `agent-readiness`, `living-artifacts`, `agent-auth`, `mcp-hardening`). | *Note: All tools support both `glintbase_*` names and canonical short names (`audit`, `get_score`, `discover_surfaces`, `simulate_flight`, `get_skill`).* --- ## 📚 Bundled Prompts & Resources ### Prompts - `optimize_agent-readiness`: Master workflow for elevating a codebase to ARS 3.0 standards. - `optimize_living-artifacts-architect`: Step-by-step guidance for authoring `llms.txt`, `llms-full.txt`, and `ard.json`. - `optimize_agent-auth-handbook`: Blueprint for RFC 9728 machine-to-machine authentication contracts (`auth.md`). - `optimize_streamable-mcp-builder`: Architectural guide for deploying streamable HTTP MCP servers. - `optimize_flight-simulator-replay`: Diagnostic playbook for analyzing agent bottlenecks. ### Resources - `skill://glintbase/agent-readiness`: Master ARS 3.0 Playbook. - `skill://glintbase/living-artifacts`: Living Artifacts Specification. - `skill://glintbase/agent-auth`: Agent Authentication Handbook. - `glintbase://schemas/ars3-spec`: Complete ARS 3.0 evaluation schema. - `glintbase://standards/auth-contract`: RFC 9728 machine auth template. --- ## 🚀 Quick Start ### Option A: Smithery CLI ```bash npx -y @smithery/cli install @glintbase/mcp --client claude

Transport
streamable-http
Auth
—
Cost
—
Protocol revision
2025-11-25
negotiated, not declared

MCP readiness

B · 86/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 66.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 25/25 Endpoint answers the MCP initialize handshake (2012 ms).
Protocol revision 8/10 Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 18/18 probes succeeded over 30 days (100%).
Tool declaration 10/10 Lists 5 tool(s) with descriptions.
Verified identity 5/10 Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags 4/5 seen in a source within 7 days.
Auth declaration 0/5 How to authenticate is not stated.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive (2012 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 80% of peers
This listing 86 · peer median 81
Latency
Faster than 5% of peers
This listing 1,688 ms · peer median 326 ms

Where it loses the most points, and how to win them back

  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
  • Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
    Now: How to authenticate is not stated.
  • Protocol revision −2 — Support the current protocol revision.
    Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

How to connect

MCP endpoint (streamable-http)
https://glintbase.dev/api/mcp
JSON-RPC initialize probe
curl -X POST https://glintbase.dev/api/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://glintbase.dev
Listed at (agenstry)
https://agenstry.com/mcp/victorather81/glintbase