Skip to content
MCPSTAMP
MCP server report

ENYAL by Greenland AI MCP server

ai.enyal/enyal

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 84 of 100 (grade B), higher than 31.0% 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
84B
Sign-in
OAuth
Tools listed
9
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) 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

5 checks to fix

  1. Fails

    Authorization server metadata (RFC 8414 / OIDC)

    auth_as_metadata

    Blocks Claude, ChatGPT and Gemini.

    Measured Not found: https://mcp.enyal.ai/.well-known/oauth-authorization-server -> 404; https://mcp.enyal.ai/.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

    Human-readable title on every tool

    tool_titles

    Blocks Claude and ChatGPT.

    Measured 9/9 without title: query_memory, get_entity, get_timeline, render, verify_chunk and 4 more

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

  3. Fails

    Resource metadata "resource" equals the server URL

    auth_resource

    Blocks Claude.

    Measured resource https://mcp.enyal.ai/ is not the server URL https://mcp.enyal.ai/mcp

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

  4. Fails

    First metadata URL Gemini tries answers 200 with the required fields

    auth_gemini_discovery

    Blocks Gemini.

    Measured Gemini tries https://mcp.enyal.ai/.well-known/oauth-authorization-server first and gets HTTP 404; it uses that answer and does not try other locations

    Make https://mcp.enyal.ai/.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 https:/

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

18 checks passed, 4 did not run

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, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, 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, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT), Tool descriptions.

Not run. 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 ENYAL by Greenland AI

Markdown

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

HTML

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

About this server

Accounts are powered by ENYAL identity, and records are verifiable without trusting us.
Registry name
ai.enyal/enyal
Remote URL
https://mcp.enyal.ai/mcp
Version
0.1.2
Website
enyal.ai
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