Skip to content

Latitude 10 Agent Readiness

by latitude10.tech · remote · no sign-in to list tools · v1.0.1 · published by tech.latitude10

Scores how well AI agents will use your API, 0-100, from its OpenAPI spec. Free and read-only.

Changes · 1
CompareRegistry entry

1 tool: 1 change things.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http agent-readiness https://latitude10.tech/mcp/readiness

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

1 tool

Changes things 1Claude Code: ask
  • check_agent_readinessScores an API 0-100 for how well AI agents will use it as tools, from its OpenAPI 3.0 or 3.1 spec: operationIds, summaries, descriptions, parameter descriptions, enums, examples, J…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Scores an API 0-100 for how well AI agents will use it as tools, from its OpenAPI 3.0 or 3.1 spec: operationIds, summaries, descriptions, parameter descriptions, enums, examples, JSON bodies, response and error schemas, pagination, auth, idempotency and tool count (the Agentify API kit's rules). Give the spec's https URL or the spec itself. Free; returns the score, each rule's result with how to fix it, and the most costly findings. Use it before turning an API into an MCP server or listing it for agents.

    Annotations the server declares

    • title: Check agent readiness
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http agent-readiness https://latitude10.tech/mcp/readiness

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__agent-readiness__check_agent_readiness"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as agent-readiness. Review it before you use it.