Skip to content
MCPSTAMP
MCP server report

Shipshape Data MCP server

com.shipshapedata/shipshape-data

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

Measured facts

Score
82B
Sign-in
OAuth
Tools listed
6
Protocol version
2025-06-18
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), PKCE S256 advertised and Human-readable title on every tool.
ChatGPT app directory Not ready Blocked by Authorization server metadata (RFC 8414 / OIDC), PKCE S256 advertised and Human-readable title on every tool.
Gemini Connected Apps Not ready Blocked by Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields and PKCE S256 advertised.
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

6 checks to fix

  1. Fails

    Authorization server metadata (RFC 8414 / OIDC)

    auth_as_metadata

    Blocks Claude, ChatGPT and Gemini.

    Measured https://shipshapedata.com/.well-known/oauth-authorization-server lacks authorization_endpoint, response_types_supported:["code"]

    Add authorization_endpoint, response_types_supported:["code"] to the authorization server metadata.

  2. Fails

    PKCE S256 advertised

    auth_pkce

    Blocks Claude, ChatGPT and Gemini.

    Measured code_challenge_methods_supported missing

    Support PKCE and advertise "code_challenge_methods_supported": ["S256"] (MCP clients refuse to proceed without it).

  3. Fails

    Human-readable title on every tool

    tool_titles

    Blocks Claude and ChatGPT.

    Measured 6/6 without title: list_services, get_case_studies, search_resources, get_ai_readiness_questions, score_ai_readiness and 1 more

    Add a short human-readable "title" to every tool (shown in store UIs and consent screens).

  4. Fails

    Resource metadata "resource" equals the server URL

    auth_resource

    Blocks Claude.

    Measured resource https://shipshapedata.com/api is not the server URL https://shipshapedata.com/mcp

    Serve metadata whose "resource" is exactly https://shipshapedata.com/mcp (Claude requires an exact match, path included), e.g. at /.well-known/oauth-protected-resource/mcp.

  5. Fails

    First metadata URL Gemini tries answers 200 with the required fields

    auth_gemini_discovery

    Blocks Gemini.

    Measured https://shipshapedata.com/.well-known/oauth-authorization-server (first URL Gemini tries) lacks authorization_endpoint, response_types_supported:["code"]

    Make https://shipshapedata.com/.well-known/oauth-authorization-server answer HTTP 200 with the authorization server metadata (authorization_endpoint, token_endpoint, response_types_supported ["code"], registration_endpoint). Gemini tries ht

  6. Warning

    refresh_token grant advertised

    auth_refresh

    Measured grant_types_supported: ["client_credentials"]

    Issue refresh tokens and list "refresh_token" in grant_types_supported so users are not logged out hourly.

20 checks passed, 1 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, initialize latency, serverInfo name and version, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), Protected resource metadata (RFC 9728), issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), Client registration (DCR or Client ID Metadata Documents), tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT), Tool descriptions.

Not run. 401 carries WWW-Authenticate resource_metadata. These need an OAuth sign-in flow the check could not reach.

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 Shipshape Data

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fshipshapedata.com%2Fmcp)](https://www.mcpstamp.com/r/com-shipshapedata-shipshape-data/)

HTML

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

About this server

Services, case studies, 169 data and AI guides, and AI readiness scoring. Read-only, keyless.
Registry name
com.shipshapedata/shipshape-data
Remote URL
https://shipshapedata.com/mcp
Version
1.0.0
Source
github.com/shipshapedata/agent-tools
Website
shipshapedata.com/developers/
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 B servers

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