Skip to content
MCPSTAMP
MCP server report

sota.io MCP server

io.sota/mcp

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

Measured facts

Score
86B
Sign-in
OAuth
Tools listed
14
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by Resource metadata "resource" equals the server URL and Human-readable title on every tool.
ChatGPT app directory Not ready Blocked by issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT) and Human-readable title on every tool.
Gemini Connected Apps Ready No blocking check failed.
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

    Human-readable title on every tool

    tool_titles

    Blocks Claude and ChatGPT.

    Measured 14/14 without title: create_account, list-projects, create-project, delete-project, deploy and 9 more

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

  2. Fails

    Resource metadata "resource" equals the server URL

    auth_resource

    Blocks Claude.

    Measured resource https://mcp.sota.io is not the server URL https://mcp.sota.io/mcp

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

  3. Fails

    issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT)

    auth_chatgpt_metadata

    Blocks ChatGPT.

    Measured issuer "https://wnwsdtqhywfxxlnyqafk.supabase.co/auth/v1" is not exactly the authorization_servers entry "https://mcp.sota.io/auth/v1"

    Use the exact metadata "issuer" string in the protected resource metadata authorization_servers list (no trailing-slash or case differences), and list token_endpoint_auth_methods_supported (for example ["none"] for public clients) in the au

  4. 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.

  5. Warning

    Tool descriptions

    tool_descriptions

    Measured 1 over 2000 chars: deploy

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

  6. Warning

    JSON-RPC error for unknown method

    jsonrpc_errors

    Measured HTTP 401 instead of a JSON-RPC error

    Route the method first and answer unknown methods with JSON-RPC error -32601 before the auth check, or return a JSON-RPC error body with the 401.

21 checks passed

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, GET answers SSE or 405, initialize latency, serverInfo name and version, tools capability declared, Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Protected resource metadata (RFC 9728), Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised, 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).

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 sota.io

Markdown

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

HTML

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

About this server

EU-native PaaS for AI agents - deploy web apps with one sentence, managed Postgres, GDPR by default.
Registry name
io.sota/mcp
Remote URL
https://mcp.sota.io/mcp
Version
1.5.0
Source
github.com/sota-deploy/mcp-server
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