Skip to content
MCPSTAMP
MCP server report

GISDB MCP server

io.gisdb/gisdb

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 77 of 100 (grade C), higher than 22.5% 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
77C
Sign-in
OAuth
Tools listed
15
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC) and Human-readable title on every tool.
ChatGPT app directory Not ready Blocked by Protected resource metadata (RFC 9728), Authorization server metadata (RFC 8414 / OIDC) and Human-readable title on every tool.
Gemini Connected Apps Not ready Blocked by Authorization server metadata (RFC 8414 / OIDC).
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

    Protected resource metadata (RFC 9728)

    auth_prm

    Blocks Claude and ChatGPT.

    Measured https://gisdb.io/.well-known/oauth-protected-resource/api/v1/mcp has no authorization_servers

    List your issuer URL in "authorization_servers" in the protected resource metadata.

  2. Fails

    Authorization server metadata (RFC 8414 / OIDC)

    auth_as_metadata

    Blocks Claude, ChatGPT and Gemini.

    Measured No authorization server to probe

    Serve RFC 8414 metadata at <issuer>/.well-known/oauth-authorization-server with authorization_endpoint, token_endpoint and response_types_supported ["code"].

  3. Fails

    Human-readable title on every tool

    tool_titles

    Blocks Claude and ChatGPT.

    Measured 15/15 without title: gisdb_search_catalog, gisdb_get_metadata, gisdb_search_records, gisdb_guide_search, gisdb_start_search and 10 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://gisdb.io/mcp is not the server URL https://gisdb.io/api/v1/mcp

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

  5. Fails

    GET answers SSE or 405

    get_stream

    Measured HTTP 200 application/json

    Return HTTP 405 Method Not Allowed on GET (or a text/event-stream), not a page or 404.

  6. Warning

    initialize latency

    latency

    Measured 3100 ms

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

15 checks passed, 6 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, serverInfo name and version, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), 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, 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. 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 GISDB

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fgisdb.io%2Fapi%2Fv1%2Fmcp)](https://www.mcpstamp.com/r/io-gisdb-gisdb/)

HTML

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

About this server

Source-backed county property records, owner-name portfolios and three Hamilton County lead packa...
Registry name
io.gisdb/gisdb
Remote URL
https://gisdb.io/api/v1/mcp
Version
0.4.2
Source
github.com/mooshee/gisdb-mcp
Website
gisdb.io
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 C servers

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