Independent technical audit

xmcp.dev

Overall AI readiness score

A combined result across all audit signals.

Excellent

AI readiness audit: 7/21/2026Public technical data

Overall AI readiness assessment

How ready xmcp.dev is for AI systems

83/100

xmcp was independently audited by llmsmap. xmcp.dev currently scores 83/100 for AI readiness. The result combines AI-specific files, crawler policy, sitemap discovery, structured homepage data, and—when available—the mobile Google Lighthouse technical profile.

Audit context

llms.txt is accessible and contains 1,641 tokens. No accessible llms-full.txt was detected, so deeper context still has to be assembled from regular pages. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.

robots.txt is available. 11 of 11 tracked AI bots are not blocked. Declared sitemaps: 1. The homepage exposes Schema.org types Organization, WebSite, FAQPage; 9 OpenGraph tags were found and markup completeness is 100%.

The mobile Lighthouse profile adds Performance 32/100, Accessibility 85/100, Best Practices 100/100, SEO 100/100, and experimental Agentic Browsing 67/100. These signals have a limited weight: they complement rather than replace llms.txt, robots.txt, and structured-data checks.

Confirmed strengths

Accessible llms.txt
1 sitemap declaration
Schema.org: Organization, WebSite
Complete social metadata

Priority improvements

1Add llms-full.txt for richer first-party context.
2Reduce mobile rendering delay and main-thread work.
3Clarify semantics, labels, and interactive states.

llms.txt tokens1,641

llms-full.txt tokens43,234

ai.txt

sitemap.xml

Google Lighthouse technical profile

A mobile Lighthouse measurement. Google’s experimental Agentic Browsing category is explained separately and does not replace the broader llmsmap AI-readiness score.

Mobile · Lighthouse

Performance

Accessibility

100

Best Practices

100

Technical SEO

Agentic Browsing

What these results mean

Mobile performance is 32/100, with the largest visible content block appearing in 6.5 s and the browser main thread blocked for 26,250 ms. Layout shift was 0. The main thread is where the browser runs JavaScript, calculates layout, and paints the page; long work there delays both user input and browser-agent actions.

Accessibility scored 85/100, Best Practices 100/100, and technical SEO 100/100. The experimental Agentic Browsing category scored 67/100. It measures signals Google currently tests for software agents and is shown separately from the llmsmap AI-readiness score.

Free the main thread and accelerate the first view

Split long JavaScript tasks, defer non-critical scripts and styles, and shorten blocking request chains. This helps the primary content appear sooner and makes controls usable earlier.

Reduce code that loads without helping the page

Remove unused CSS and JavaScript, load heavy widgets on demand, and limit third-party scripts. Less code means less parsing and background work on the device.

Make controls unambiguous

Give buttons and links accessible names, associate labels with fields, and use ordered headings and semantic regions. The same structure helps screen readers and software agents understand actions.

Improve interface contrast and readability

Increase contrast for text, states, and interactive controls so both people and visual agents can distinguish content from actions and supporting labels.

FCP3.3 s

First content

LCP6.5 s

Main content

CLS0

Layout stability

TBT26,250 ms

Blocking time

SI11.6 s

Visual speed

Metric glossary

FCP · First content: When the first text or image appeared on screen.
LCP · Main content: When the largest visible element in the first viewport rendered.
CLS · Layout stability: How much content shifted unexpectedly while loading; lower is better.
TBT · Blocking time: How long the browser main thread could not respond quickly to input.
SI · Visual speed: How quickly the visible viewport filled with content.

7/21/2026Lighthouse 13.4.0Mobile profile

AI readiness checks

Machine-readable files, crawler policy, discovery, and homepage markup.

llms.txt

File found and accessible

https://xmcp.dev/llms.txt

llms-full.txt

Full version was not found

ai.txt

ai.txt file was not found

robots.txt

File found

https://xmcp.dev/robots.txt

Sitemap in robots.txt1

1 sitemap found

Schema.org (JSON-LD)

Types: Organization, WebSite, FAQPage

OpenGraph100%

9 OG tags found

AI bot access

Based on robots.txt analysis

GPTBotNot mentioned

OAI-SearchBotNot mentioned

ChatGPT-UserNot mentioned

Google-ExtendedNot mentioned

ClaudeBotNot mentioned

Claude-SearchBotNot mentioned

Claude-UserNot mentioned

BytespiderNot mentioned

CCBotNot mentioned

PerplexityBotNot mentioned

Perplexity-UserNot mentioned

Sitemaps

Declared discovery routes for crawlers and agents.

https://xmcp.dev/sitemap.xml

OpenGraph tags

Social preview metadata found on the homepage.

Markup completeness: 100%

og:titlexmcp — The TypeScript MCP framework

og:descriptionxmcp is the TypeScript framework for building, shipping, and scaling Model Context Protocol servers — tools, prompts, resources, auth, transports, and monetization out of the box.

og:urlhttps://xmcp.dev

og:site_namexmcp

og:localeen_US

og:imagehttps://xmcp.dev/xmcp-og.png

og:image:width1200

og:image:height630

og:typewebsite

Schema.org markup

Structured entities and properties exposed on the homepage.

Types found: 3 · Properties: 5

OrganizationWebSiteFAQPage

namexmcp

urlhttps://xmcp.dev

logohttps://xmcp.dev/favicon.svg

sameAshttps://github.com/basementstudio/xmcp, https://x.com/xmcp_dev

publisherhttps://xmcp.dev

# xmcp

> xmcp is a framework for building and shipping MCP servers with TypeScript. Designed with DX in mind, it simplifies setup and removes friction in just one command — making it easy to build & deploy AI tools on top of the Model Context Protocol ecosystem.

## Docs

- [Introduction](/docs): xmcp is a framework for building and shipping MCP servers with TypeScript. Designed with DX in mind, it simplifies setup and removes friction in just one command — making it easy to build & deploy AI tools on top of the Model Context Protocol ecosystem.

## adapters

- [Express](/docs/adapters/express): Plug xmcp into your existing Express application.
- [Fastify](/docs/adapters/fastify): Run an xmcp MCP server on Fastify. Works on any Node.js deployment target including AWS Lambda.
- [NestJS](/docs/adapters/nestjs): Plug xmcp into your existing NestJS application with automatic tool discovery and customizable module configuration.
- [Next.js](/docs/adapters/nextjs): Plug xmcp into your existing Next.js application.

## authentication

- [API Key](/docs/authentication/api-key): Secure access and protect your MCP server using API keys.
- [JSON Web Token](/docs/authentication/jwt): Secure access and protect your MCP server using JSON Web Tokens.
- [OAuth](/docs/authentication/oauth): Production-ready OAuth implementations with authentication plugins.

## configuration

- [Bundler](/docs/configuration/bundler): Extend the bundler configuration for your MCP server.
- [Custom Directories](/docs/configuration/custom-directories): Customize where xmcp looks for tools, prompts, and resources.
- [Server Info](/docs/configuration/server-info): Customize the name, description, instructions, icons, and home page of your MCP server.
- [Telemetry](/docs/configuration/telemetry): A condensed version of the telemetry policy with actionable opt-out instructions.
- [Transports](/docs/configuration/transports): Customize the transport types for your MCP server.

## core-concepts

- [CSS](/docs/core-concepts/css): Style your xmcp MCP tools with Tailwind CSS, CSS Modules, or plain CSS, including class management and theming for tool-rendered UI components.
- [External Clients](/docs/core-concepts/external-clients): Learn how to connect to external MCP servers via HTTP or STDIO and generate fully typed TypeScript clients with autocomplete support.
- [Middlewares](/docs/core-concepts/middlewares): undefined
- [Prompts](/docs/core-concepts/prompts): Prompts are user-controlled instruction templates that enable structured, consistent interactions through parameterized workflows.
- [Resources](/docs/core-concepts/resources): Resources are application-driven, read-only data sources that provide context to AI models from files, APIs, databases, and other sources.
- [Tools](/docs/core-concepts/tools): Tools are functions that your LLM can actively call and decides when to use based on user requests. They enable AI models to perform actions such as writing to databases, calling external APIs, modifying files, or triggering other logic.

## deployment

- [Alpic](/docs/deployment/alpic): Alpic is a MCP-first cloud platform with one-click deployment for xmcp servers. Deploy your xmcp server to Alpic with zero-configuration.
- [Cloudflare](/docs/deployment/cloudflare): Cloudflare Workers support in xmcp uses a Cloudflare-native bundle and Wrangler for local dev and deploy.
- [Replit](/docs/deployment/replit): Deploy your xmcp application to Replit with a single click.
- [Vercel](/docs/deployment/vercel): Vercel supports xmcp with zero-configuration.

## discoverability

- [MCP Server Card](/docs/discoverability/mcp-server-card): Serve an MCP Server Card for automatic agent discovery.
- [Smithery](/docs/discoverability/smithery): Publish your xmcp server to Smithery for distribution and observability.

## getting-started

- [Connecting to your server](/docs/getting-started/connecting): Configure HTTP and STDIO transport connections for local development and production environments
- [Installation](/docs/getting-started/installation): Set up your MCP server using automated scaffolding or manual installation, configure build scripts, and troubleshoot transport configurations
- [Project structure](/docs/getting-started/project-structure): Explore the file-system based architecture with auto-discovery for tools, prompts, and resources, plus configuration options for custom directory layouts

## guides

- [Authentication](/docs/guides/authentication): Secure your MCP server with OAuth 2.1, API keys, or JWT tokens. Understand authentication vs authorization, PKCE, scopes, and token-based access control. Integrate with Better Auth, Clerk, Auth0, or WorkOS.
- [Monetization](/docs/guides/monetization): Charge for your MCP tools using license keys or crypto micropayments. Understand human vs agent monetization models, and integrate with Polar or x402.
- [Roll out to a team](/docs/guides/roll-out-to-a-team): Roll out secure team access to your xmcp server using Scalekit OAuth 2.1. Understand the team-notes pattern, wire it into your project, and verify per-user isolation.
- [xmcp MCP server](/docs/guides/xmcp-mcp-server): Connect coding agents to xmcp's documentation MCP server to get real-time answers about xmcp features, configuration, and best practices.

## integrations

- [Auth0](/docs/integrations/auth0): The Auth0 plugin provides authentication for your MCP server using Auth0 with scope-based authorization.
- [Better Auth](/docs/integrations/better-auth): Add secure authentication to your MCP server using Better Auth and PostgreSQL
- [Clerk](/docs/integrations/clerk): The Clerk plugin provides authentication for your MCP server using Clerk's OAuth system.
- [Commet](/docs/integrations/commet): Add subscription-aware billing, feature gating, and usage tracking to your xmcp server with Commet
- [Descope](/docs/integrations/descope): The Descope plugin provides authentication for your MCP server using Descope's OAuth 2.1 agentic identity system with Dynamic Client Registration.
- [Polar](/docs/integrations/polar): Add paywalls and track tool usage with license keys using Polar
- [Scalekit](/docs/integrations/scalekit): The Scalekit plugin provides OAuth 2.1 authentication for your MCP server using Scalekit as the authorization server.
- [WorkOS](/docs/integrations/workos): The WorkOS plugin provides authentication for your mcp server using WorkOS AuthKit.
- [x402](/docs/integrations/x402): The x402 plugin enables tool monetization through the HTTP 402 payment protocol using USDC on Base.

Share or continue the analysis

Share this audit

Discuss with AI

Added 7/19/2026