Skip to content
MCPSTAMP
MCP server report

Quriov MCP server

com.quriovai/quriov

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

Measured facts

Score
47F
Sign-in
API key or other
Tools listed
Behind sign-in
Protocol version
None returned
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Unverified Nothing failed, but initialize over Streamable HTTP, tools/list returns tools, inputSchema is an object schema, readOnlyHint or destructiveHint on every tool and Human-readable title on every tool could not run in a check without credentials.
ChatGPT app directory Not ready Blocked by Sign-in method the store supports (OAuth or none), Protected resource metadata (RFC 9728) and Authorization server metadata (RFC 8414 / OIDC).
Gemini Connected Apps Not ready Blocked by Sign-in method the store supports (OAuth or none) and Authorization server metadata (RFC 8414 / OIDC).
Official MCP Registry Unverified Nothing failed, but initialize over Streamable HTTP could not run in a check without credentials.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

4 checks to fix

  1. Fails

    Protected resource metadata (RFC 9728)

    auth_prm

    Blocks ChatGPT.

    Measured Not found: https://quriovai.com/.well-known/oauth-protected-resource/mcp/v1 -> 404; https://quriovai.com/.well-known/oauth-protected-resource -> 404

    Serve RFC 9728 metadata at /.well-known/oauth-protected-resource (plus the path-suffixed form) with "resource" and "authorization_servers".

  2. Fails

    Authorization server metadata (RFC 8414 / OIDC)

    auth_as_metadata

    Blocks ChatGPT and Gemini.

    Measured Not found: https://quriovai.com/.well-known/oauth-authorization-server -> 404; https://quriovai.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"].

  3. Fails

    Sign-in method the store supports (OAuth or none)

    auth_method

    Blocks ChatGPT and Gemini.

    Measured initialize: HTTP 401 and no working OAuth discovery: the server asks for a Bearer token but its OAuth metadata could not be found

    ChatGPT and Gemini cannot send a static API key or token: add MCP OAuth (protected resource metadata and authorization server metadata), or serve the tools without auth. Claude accepts a static credential in a request header only in a beta

  4. Warning

    initialize latency

    latency

    Measured 3401 ms

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

3 checks passed, 20 did not run

Passed. Served over HTTPS, GET answers SSE or 405, 401 carries WWW-Authenticate resource_metadata.

Not run. Resource metadata "resource" equals the server URL, 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.

Not run. 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, 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. The tools sit behind sign-in, and the check runs without credentials.

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 Quriov

Markdown

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

HTML

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

About this server

Create and manage AI image and video generations through Quriov's fixed public MCP tools.
Registry name
com.quriovai/quriov
Remote URL
https://quriovai.com/mcp/v1
Version
1.0.0
Source
github.com/Quriov/Quriov-AI-Video
Website
quriovai.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 F servers

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