Skip to content
MCPSTAMP
MCP server report

Frisian MCP (Django) MCP server

com.frisian-mcp/django

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

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by readOnlyHint or destructiveHint on every tool and Human-readable title on every tool.
ChatGPT app directory Not ready Blocked by readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (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

7 checks to fix

  1. Fails

    readOnlyHint or destructiveHint on every tool

    tool_annotations

    Blocks Claude and ChatGPT.

    Measured 4/4 tools set neither readOnlyHint nor destructiveHint: docs, demo, install, troubleshooting

    Set annotations.readOnlyHint: true on read-only tools and destructiveHint: true on tools that modify or delete data (Claude needs one of them on every tool; ChatGPT needs all three hints, see tool_open_world).

  2. Fails

    Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)

    tool_open_world

    Blocks ChatGPT.

    Measured 4/4 tools miss an explicit hint: docs, demo, install, troubleshooting

    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 4/4 without title: docs, demo, install, troubleshooting

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

  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

    Client registration (DCR or Client ID Metadata Documents)

    auth_registration

    Measured No registration_endpoint and no client_id_metadata_document_supported

    Add a Dynamic Client Registration endpoint (RFC 7591) or set client_id_metadata_document_supported: true; otherwise every store needs a manually issued client id.

  6. Warning

    initialize latency

    latency

    Measured 2118 ms

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

  7. Warning

    refresh_token grant advertised

    auth_refresh

    Measured grant_types_supported: ["client_credentials","authorization_code"]

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

19 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, 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, Authorization server metadata (RFC 8414 / OIDC), 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, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, 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 Frisian MCP (Django)

Markdown

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

HTML

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

About this server

Your DRF API as MCP tools - 1,800 endpoints become 16 dispatchers, permissioned by Django.
Registry name
com.frisian-mcp/django
Remote URL
https://mcp.frisian-mcp.com/mcp/
Version
1.0.12
Source
github.com/Frisian-MCP/frisian-mcp
Website
frisian-mcp.com
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