MCP

23 / 100

Write release notes in minutes, or let your AI agent draft them for you. Then publish to your branded changelog and notify customers automatically.

Scanned 2h ago · 1 views · Open site

Checks

• HTTPS5/5

  Served over HTTPS.

• llms.txt12/12

  Found /llms.txt (6366 chars).

• Agent manifest0/15

  No /.well-known/ai-agent.json.

  Fix: Publish https://onset.io/.well-known/ai-agent.json with name, description, capabilities, contact, auth, and pricing.

• A2A agent card0/12

  No /.well-known/agent-card.json.

  Fix: Publish https://onset.io/.well-known/agent-card.json with name, url, and skills or capabilities.

• MCP endpoint6/12

  Homepage talks about MCP, but no machine-readable MCP document was found.

  Fix: Publish /.well-known/mcp.json (or an MCP resource metadata document) pointing at your MCP server.

• OpenAPI spec0/12

  No OpenAPI or Swagger spec found.

  Fix: Serve /openapi.json (or /swagger.json) with a valid OpenAPI spec, or link it from the homepage.

• Named capabilities0/8

  No named capabilities, skills, or API operations.

  Fix: List named capabilities in the agent manifest, agent card skills, or OpenAPI path summaries.

• I/O schemas0/8

  No I/O schemas.

  Fix: Add components.schemas / requestBody schemas in OpenAPI, or input/output schemas on each skill.

• Machine-readable pricing0/8

  No machine-readable pricing.

  Fix: Add a pricing object to ai-agent.json, or publish /pricing.json with currency and product amounts.

• Auth, contact, rate limits0/8

  No contact, auth, or rate limit declaration.

  Fix: Declare contact, auth, and rateLimit in ai-agent.json (and OpenAPI info.contact / securitySchemes).

8 checks short of a perfect 100. The fix lines above are the report — what to publish, at which path.

How scoring works · Recently graded · Back to the board