Overall AI readiness score
A combined result across all audit signals.
Excellent
AI readiness audit: 8/5/2026Public technical data
Overall AI readiness assessment
How ready sfcc-mcp-dev.rhino-inquisitor.com is for AI systems
SFCC Development MCP Server (sfcc-mcp-dev.rhino-inquisitor.com) received an AI-readiness score of 87/100 in an automated technical audit. llms.txt was accessible, llms-full.txt was not found, and ai.txt was not found. The robots.txt analysis found 0 explicitly allowed and 0 blocked AI crawlers, with 1 declared sitemap. Homepage markup completeness was 100%; Schema.org types included WebSite, SoftwareApplication, WebPage and 7 OpenGraph tags were detected. Results reflect the public site response observed on 2026-08-05T00:06:14.504Z.
Audit context
llms.txt is accessible and contains 810 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 WebSite, SoftwareApplication, WebPage; 7 OpenGraph tags were found and markup completeness is 100%.
The mobile Lighthouse profile adds Performance 92/100, Accessibility 92/100, Best Practices 100/100, SEO 100/100, and experimental Agentic Browsing 100/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: WebSite, SoftwareApplication
- Complete social metadata
- Strong Google agentic signals
Priority improvements
- 1Add llms-full.txt for richer first-party context.
llms.txt tokens810
llms-full.txt tokens—
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.
92
Performance
92
Accessibility
100
Best Practices
100
Technical SEO
100
Agentic Browsing
What these results mean
The mobile page renders efficiently; its largest visible content block appeared in 2.6 s.
Accessibility scored 92/100, Best Practices 100/100, and technical SEO 100/100. The experimental Agentic Browsing category scored 100/100. It measures signals Google currently tests for software agents and is shown separately from the llmsmap AI-readiness score.
1
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.
2
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.
3
Optimise images and their loading order
Serve correctly sized modern formats, prioritise the primary visual, and lazy-load content below the first viewport.
4
Reduce network delay
Improve server response time, remove unnecessary redirects and repeat downloads, and use compression, caching, and selective preconnect hints.
FCP2.3 s
First content
LCP2.6 s
Main content
CLS0
Layout stability
TBT10 ms
Blocking time
SI4.3 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.
8/5/2026Lighthouse 13.4.1Mobile profile
AI readiness checks
Machine-readable files, crawler policy, discovery, and homepage markup.
llms-full.txt
Full version was not found
ai.txt
ai.txt file was not found
Sitemap in robots.txt1
1 sitemap found
Schema.org (JSON-LD)
Types: WebSite, SoftwareApplication, WebPage
OpenGraph100%
7 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.
OpenGraph tags
Social preview metadata found on the homepage.
og:typewebsiteog:site_nameSFCC Dev MCPog:titleSFCC Development MCP Serverog:descriptionLocal MCP server for SFCC development with documentation search, log analysis, cartridge scaffolding, and debugging tools.og:urlhttps://sfcc-mcp-dev.rhino-inquisitor.com/og:image:altSFCC Development MCP ServerSchema.org markup
Structured entities and properties exposed on the homepage.
WebSiteSoftwareApplicationWebPage
nameSFCC Dev MCPurlhttps://sfcc-mcp-dev.rhino-inquisitor.comdescriptionMCP server for Salesforce B2C Commerce Cloud development with docs, logs, and toolingsameAshttps://github.com/taurgis/sfcc-dev-mcp, https://www.npmjs.com/package/sfcc-dev-mcpimagehttps://sfcc-mcp-dev.rhino-inquisitor.com/explain-product-pricing-methods.png# SFCC Development MCP Server > A comprehensive Model Context Protocol (MCP) server that provides AI assistants with direct access to Salesforce B2C Commerce Cloud development tools, documentation, curated agent skills, and real-time debugging capabilities. This server bridges the gap between AI assistants and SFCC development workflows, offering both documentation-only mode (no credentials required) and full mode (with live SFCC instance access). It provides a broad tool surface across documentation, log analysis, system objects, cartridge generation, and script debugging. Key architectural principles: - **Capability-gated**: Tools requiring SFCC credentials are only exposed when valid configuration is provided - **Modular handlers**: Clean separation between tool routing and domain logic - **Dependency injection**: Testable architecture with service abstractions - **Performance optimized**: Efficient caching and range request optimization for log analysis ## Core Documentation - [Getting Started](https://sfcc-mcp-dev.rhino-inquisitor.com/guide/): Introduction and modes - [AI Interface Setup](https://sfcc-mcp-dev.rhino-inquisitor.com/guide/ai-interfaces/): Platform-specific setup for Copilot, Claude, and Cursor - [Configuration Guide](https://sfcc-mcp-dev.rhino-inquisitor.com/guide/configuration/): dw.json, environment variables, and auto-discovery - [Features Overview](https://sfcc-mcp-dev.rhino-inquisitor.com/features/): Complete feature breakdown - [Tools Catalog](https://sfcc-mcp-dev.rhino-inquisitor.com/tools/): All tools organized by category with examples - [Examples](https://sfcc-mcp-dev.rhino-inquisitor.com/examples/): Practical prompts and workflows - [Script Debugger](https://sfcc-mcp-dev.rhino-inquisitor.com/script-debugger/): Sandbox evaluation via debugger API - [Skills](https://sfcc-mcp-dev.rhino-inquisitor.com/skills/): Bundled skills and instruction packs - [Security](https://sfcc-mcp-dev.rhino-inquisitor.com/security/): Credential and data handling guidance - [Development Guide](https://sfcc-mcp-dev.rhino-inquisitor.com/development/): Architecture, testing, and contribution workflow - [Troubleshooting](https://sfcc-mcp-dev.rhino-inquisitor.com/troubleshooting/): Common issues and fixes ## Tool Categories - **SFCC Documentation Tools**: Class information, method search, and namespace exploration - **SFRA Documentation Tools**: Enhanced Storefront Reference Architecture docs - **ISML Documentation Tools**: ISML element reference and search - **Agent Instruction Tools**: Sync AGENTS.md + bundled skills into a workspace - **Log & Job Log Tools**: Log search, summaries, and job execution debugging - **System Object Tools**: Attribute discovery and site preference management - **Cartridge Generation Tools**: Cartridge and project scaffolding - **Code Version Tools**: Listing and activation - **Script Debugger Tools**: Execute JavaScript on sandbox instances ## Optional - [GitHub Repository](https://github.com/taurgis/sfcc-dev-mcp) - [NPM Package](https://www.npmjs.com/package/sfcc-dev-mcp) - [CHANGELOG](https://github.com/taurgis/sfcc-dev-mcp/blob/main/CHANGELOG.md) - [Contributing Guidelines](https://github.com/taurgis/sfcc-dev-mcp/blob/main/CONTRIBUTING.md)
Share or continue the analysis
Share this audit
Discuss with AI
Added 8/5/2026