Skip to content
MCPSTAMP
MCP server report

Skimguard MCP server

io.skimguard/skimguard

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

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by Authorization server metadata (RFC 8414 / OIDC).
ChatGPT app directory Not ready Blocked by Authorization server metadata (RFC 8414 / OIDC).
Gemini Connected Apps Not ready Blocked by Authorization server metadata (RFC 8414 / OIDC) and First metadata URL Gemini tries answers 200 with the required fields.
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

    Authorization server metadata (RFC 8414 / OIDC)

    auth_as_metadata

    Blocks Claude, ChatGPT and Gemini.

    Measured Not found: https://auth.skimguard.io/.well-known/oauth-authorization-server -> timeout after 8000 ms; https://auth.skimguard.io/.well-known/openid-configuration

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

  2. Fails

    First metadata URL Gemini tries answers 200 with the required fields

    auth_gemini_discovery

    Blocks Gemini.

    Measured Gemini tries https://auth.skimguard.io/.well-known/openid-configuration first and gets HTTP 404; it uses that answer and does not try other locations

    Make https://auth.skimguard.io/.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

  3. Fails

    Server instructions

    instructions

    Measured No instructions in the initialize result

    Add an "instructions" string to the initialize result: what the server covers, for whom, and its limits.

19 checks passed, 5 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, tools capability declared, Sign-in method the store supports (OAuth or none), Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, 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), Human-readable title on every tool, Tool descriptions.

Not run. 401 carries WWW-Authenticate resource_metadata, 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 Skimguard

Markdown

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

HTML

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

About this server

Ask whether a location has recent credit-card-skimmer detections, from a consumer sensor network.
Registry name
io.skimguard/skimguard
Remote URL
https://mcp.skimguard.io/mcp
Version
2.0.0
Website
skimguard.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 B servers

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