24Readiness score / 100
L1 Agent-readableBeats 23% of 1,846 companies
Access16/20
Context0/20
Interfaces8/32
Onboarding0/19
Trust0/9
Biggest gains
- +12 Remote MCP server for the product. Host a remote MCP server (e.g. mcp.<domain>/mcp, Streamable HTTP) for your core actions.
- +8 llms.txt exists. Publish /llms.txt: a markdown index of your docs at the root or docs host.
- +6 Docs available as markdown. Serve every docs page as .md, or honour Accept: text/markdown.
All 20 checks
- PASSAgents get the real page, not a bot wall10
- PASSrobots.txt lets user-triggered agents in6
- FAILContent is server-rendered4
- FAILllms.txt exists8
- FAILllms-full.txt exists3
- FAILDocs available as markdown6
- FAILSitemap2
- FAILStructured metadata1
- FAILPublic developer docs4
- PASSMachine-readable API spec8
- FAILRemote MCP server for the product12
- FAILDocs MCP or searchable docs4
- FAILSDKs and a CLI4
- FAILOAuth discovery metadata5
- FAILAgents can self-register OAuth clients6
- FAILSelf-serve API keys5
- FAILFree tier or test mode3
- FAILAgent manifests4
- FAILsecurity.txt2
- FAILPublic status page3
Your fix pack: 18 changes, up to +76 points
Each change is ready to paste, filled in for i-cue.solutions, with a command to check it worked. Or hand the whole list to your coding agent.
We didn't find developer docs, an API spec or an MCP server for i-cue.solutions. If you don't offer an API, the Access and Context fixes still help AI assistants read and recommend your site; you can skip the API and sign-in ones.
Want the full treatment, not just these fixes? Get the prompt that takes your coding agent through every phase.
Add the badge to your README
[](https://agentsready.dev/c/i-cue.solutions)