MCP App Store
by KeenEthics
Nordprix MCP Readiness Check icon

Nordprix MCP Readiness Check

By Nordprix

Get New App Alerts

Overview

Nordprix MCP Readiness Check tests a remote MCP server against the requirements Anthropic publishes for the Connectors Directory, before you submit it. Give Claude your server's https:// URL and the check_mcp_server tool reports, check by check, whether the server answers MCP over Streamable HTTP (the 2026-07-28 protocol and the earlier initialize handshake), which authentication type it uses, whether its OAuth discovery is complete (401 challenge, protected resource metadata, authorization server metadata, issuer, DCR or CIMD, PKCE S256, response times), and whether its tools follow the directory's tool rules: titles, readOnlyHint or destructiveHint annotations, name length, descriptions, no mixed read/write HTTP tools, API references on free-form query tools, and prompt-injection patterns. Each failed or warning check comes with the evidence, a fix and a documentation link. If your tools are behind sign-in, paste a signed-in tools/list result and check_tools_list runs the tool rules on it without contacting any server. What is sent to your server: the MCP handshake, tools/list (at most 5 pages) and GET requests for OAuth discovery documents. It never calls your tools, never registers an OAuth client, never requests a token and sends no credentials. Only public https:// addresses are checked, and nothing you submit is stored. The check covers what can be tested from outside a server. It is not a review decision by Anthropic, and Nordprix is not affiliated with Anthropic.

Tools

check_mcp_server

Claude
Checks a remote MCP server against the published requirements for Claude’s Connectors Directory: HTTPS, Streamable HTTP transport, the authentication type and OAuth discovery metadata, and the tool rules (titles, readOnlyHint or destructiveHint annotations, names, descriptions). Returns pass, warn, fail or skip for each check, with a fix for each problem. Use it when the user gives the URL of an MCP server and asks whether it is ready for the directory or why it does not connect. What is sent to that server: the MCP handshake (server/discover, or initialize and notifications/initialized for older servers, plus a DELETE to close a session if the server opened one), tools/list (at most 5 pages), and GET requests for OAuth discovery documents. It never calls a tool, never registers an OAuth client, never requests a token and sends no credentials or cookies. Only public https:// URLs are accepted, and a check takes at most 20 seconds.

check_tools_list

Claude
Checks tool definitions from a pasted tools/list result against the tool rules for Claude’s Connectors Directory: a title on every tool, readOnlyHint or destructiveHint annotations, names of 64 characters or fewer, descriptions, no single tool that mixes safe and unsafe HTTP methods, API references on free-form query tools, prompt-injection patterns, and MCP Apps UI metadata. Use it when the user pastes tools/list JSON, for example from MCP Inspector or a signed-in session, rather than giving a server URL. It only reads the pasted text and makes no network requests.

Similar Apps