Skip to content
MCPSTAMP
MCP server report

PeppolStatus MCP server

com.peppolstatus/api

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

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by 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 Authorization server metadata (RFC 8414 / OIDC), Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT) and Human-readable title on every tool.
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

6 checks to fix

  1. Fails

    Authorization server metadata (RFC 8414 / OIDC)

    auth_as_metadata

    Blocks Claude, ChatGPT and Gemini.

    Measured Not found: https://api.peppolstatus.com/.well-known/oauth-authorization-server -> 200; https://api.peppolstatus.com/.well-known/openid-configuration -> 404

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

  2. Fails

    Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)

    tool_open_world

    Blocks ChatGPT.

    Measured 65/65 tools miss an explicit hint: list_hosts, get_host, list_host_incidents, get_host_uptime, list_incidents and 60 more

    Set readOnlyHint, destructiveHint and openWorldHint to explicit true/false on every tool (OpenAI app review requires all three).

  3. Fails

    Human-readable title on every tool

    tool_titles

    Blocks Claude and ChatGPT.

    Measured 65/65 without title: list_hosts, get_host, list_host_incidents, get_host_uptime, list_incidents and 60 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://api.peppolstatus.com is not the server URL https://mcp.peppolstatus.com/

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

  5. Fails

    First metadata URL Gemini tries answers 200 with the required fields

    auth_gemini_discovery

    Blocks Gemini.

    Measured Gemini tries https://api.peppolstatus.com/.well-known/oauth-authorization-server first and gets HTTP 200 without authorization server metadata; it uses that ans

    Make https://api.peppolstatus.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

  6. Warning

    Tool descriptions

    tool_descriptions

    Measured 3 over 2000 chars: get_access_point_churn, list_cohort_moves, get_provider_moves

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

16 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, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), Protected resource metadata (RFC 9728), tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool.

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 PeppolStatus

Markdown

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

HTML

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

About this server

Peppol market intelligence and network monitoring: migrations, provider churn, leads, and uptime.
Registry name
com.peppolstatus/api
Remote URL
https://mcp.peppolstatus.com/
Version
1.0.0
Website
peppolstatus.com/mcp
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