Skip to content
MCPSTAMP
MCP server report

Ready APIs MCP server

com.readyapis/api

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 90 of 100 (grade A), higher than 61.4% of the 33,003 registry servers that responded over HTTPS that day. Ready for Claude, ChatGPT, Gemini and MCP Registry.

Measured facts

Score
90A
Sign-in
No sign-in
Tools listed
135
Protocol version
2025-06-18
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Ready No blocking check failed.
ChatGPT app directory Ready No blocking check failed.
Gemini Connected Apps Ready No blocking check failed.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

3 checks to fix

  1. Fails

    Tool names are valid and portable

    tool_names

    Measured duplicates: jobs_skill_trends, jobs_related_skills, jobs_role_skills, jobs_remote_trends, jobs_companies_hiring and 1 more

    Use unique tool names of 1-64 characters from A-Z a-z 0-9 _ - (start with a letter).

  2. Warning

    Tool descriptions

    tool_descriptions

    Measured 3 under 60 chars: company_ticker, company_nonprofit_ein, jobs_related_skills

    Keep each tool description between 60 and 2000 characters: when to use it, what it returns, key limits.

  3. Warning

    initialize latency

    latency

    Measured 1623 ms

    Bring initialize under 1.5 s: avoid cold starts and upstream calls in the handshake.

14 checks passed, 10 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, JSON-RPC error for unknown method, GET answers SSE or 405, serverInfo name and version, Server instructions, tools capability declared, tools/list returns tools, inputSchema is an object schema, readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT), Human-readable title on every tool.

Not run. Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised. The server asks for no sign-in, so the OAuth checks do not apply.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for Ready APIs

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Freadyapis.com%2Fmcp)](https://www.mcpstamp.com/r/com-readyapis-api/)

HTML

<a href="https://www.mcpstamp.com/r/com-readyapis-api/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Freadyapis.com%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

135 MCP tools: geo, email, phone, company, DNS, FX, equities, weather, tax, econ, intel - one key.
Registry name
com.readyapis/api
Remote URL
https://readyapis.com/mcp
Version
1.2.0
Source
github.com/ReadyAPIs-com/readyapis
Website
readyapis.com
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade A servers

All grade A servers · All server reports · State of MCP readiness, November 2026