# Latitude 10 Agent Readiness (remote · latitude10.tech)

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

- Trust score: 82/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `latitude10.tech`: 82/100 (this document), [markdown](https://verifymcp.io/servers/tech-latitude10-agent-readiness/mcp-readiness.md), [page](https://verifymcp.io/servers/tech-latitude10-agent-readiness/mcp-readiness)

## Channel facts

- Endpoint: `https://latitude10.tech/mcp/readiness`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 359 tokens (~359/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Latitude 10 Agent Readiness MCP server?

Latitude 10 Agent Readiness is a hosted endpoint at https://latitude10.tech/mcp/readiness, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "tech-latitude10-agent-readiness": {
      "url": "https://latitude10.tech/mcp/readiness"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tech-latitude10-agent-readiness": {
      "type": "http",
      "url": "https://latitude10.tech/mcp/readiness"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tech-latitude10-agent-readiness]
url = "https://latitude10.tech/mcp/readiness"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-latitude10-agent-readiness": {
      "type": "remote",
      "url": "https://latitude10.tech/mcp/readiness",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tech-latitude10-agent-readiness --url 'https://latitude10.tech/mcp/readiness' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-latitude10-agent-readiness:
    url: "https://latitude10.tech/mcp/readiness"
```

### Netclaw

```json
{
  "McpServers": {
    "tech-latitude10-agent-readiness": {
      "Transport": "http",
      "Url": "https://latitude10.tech/mcp/readiness"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tech-latitude10-agent-readiness -t streamable-http -u 'https://latitude10.tech/mcp/readiness'
```

### Other

```json
{
  "mcpServers": {
    "tech-latitude10-agent-readiness": {
      "type": "http",
      "url": "https://latitude10.tech/mcp/readiness"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-02 (score 82, 0)

- [security] Stability: 0.97 → pass

### 2026-11-01 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 78, +3)

- [security improvement] HSTS header: fail → pass

### 2026-10-23 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 74, 0)

- [functional] MCP protocol: Implements a current MCP spec version (2026-07-28).
- [functional] MCP protocol version: 2025-11-25 → 2026-07-28

## MCP tools (1)

### `check_agent_readiness` (~195 tokens)

Check agent readiness

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.

Input parameters:

- `spec` (string): The OpenAPI document itself, as JSON or YAML text (up to 2 MB). Send url or spec, not both.
- `url` (string): https URL of the OpenAPI document (JSON or YAML), e.g. https://api.example.com/openapi.json

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tech-latitude10-agent-readiness/mcp-readiness#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 80
- 2026-10-28: 80
- 2026-10-27: 79
- 2026-10-26: 79
- 2026-10-25: 78
- 2026-10-24: 78
- 2026-10-23: 75
- 2026-10-22: 74
- 2026-10-21: 74
- 2026-10-20: 74
- 2026-10-19: 73
- 2026-10-18: 73
- 2026-10-17: 72
- 2026-10-16: 72
- 2026-10-15: 71
- 2026-10-14: 71
- 2026-10-13: 70
- 2026-10-12: 70
- 2026-10-10: 69
- 2026-10-07: 67
- 2026-10-04: 66
- 2026-10-03: 66

## Common questions

### What is the Latitude 10 Agent Readiness MCP server?

Latitude 10 Agent Readiness is an MCP server listed in the public MCP registry as tech.latitude10/agent-readiness. Scores how well AI agents will use your API, 0-100, from its OpenAPI spec. Free and read-only. This page covers its hosted endpoint (https://latitude10.tech/mcp/readiness).

### Is the Latitude 10 Agent Readiness MCP server safe to use?

Latitude 10 Agent Readiness scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Latitude 10 Agent Readiness MCP server expose?

Latitude 10 Agent Readiness exposes 1 tool: check_agent_readiness. Their descriptions and schemas cost roughly 195 tokens of context every time the server is loaded.

### Does the Latitude 10 Agent Readiness MCP server require authentication?

No. We connected to Latitude 10 Agent Readiness without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Latitude 10 Agent Readiness MCP server still maintained?

Latitude 10 Agent Readiness is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Latitude 10 Agent Readiness MCP server?

VerifyMCP ran 13 checks on Latitude 10 Agent Readiness, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://latitude10.tech/mcp/readiness
- Website: https://latitude10.tech/agent-readiness
- Changelog RSS feed: https://verifymcp.io/servers/tech-latitude10-agent-readiness/mcp-readiness.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-latitude10-agent-readiness/mcp-readiness/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/tech-latitude10-agent-readiness/mcp-readiness.json
- HTML version of this page: https://verifymcp.io/servers/tech-latitude10-agent-readiness/mcp-readiness