Skip to content
MCPSTAMP
MCP server report

Linkly MCP server

com.linklyhq/linkly

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

Measured facts

Score
95A
Sign-in
OAuth
Tools listed
25
Protocol version
2025-06-18
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Ready No blocking check failed.
ChatGPT app directory Ready No blocking check failed.
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

2 checks to fix

  1. Fails

    Tool descriptions

    tool_descriptions

    Measured 1/25 missing or under 20 chars: ping

    Write a 1-3 sentence description for every tool: when to use it and what it returns.

  2. Warning

    refresh_token grant advertised

    auth_refresh

    Measured grant_types_supported: ["authorization_code"]

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

24 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, 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), 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, Client registration (DCR or Client ID Metadata Documents), 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.

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 Linkly

Markdown

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

HTML

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

About this server

Create and manage short links, track clicks, and automate URL management
Registry name
com.linklyhq/linkly
Remote URL
https://mcp.linklyhq.com/
Version
2.0.0
Source
github.com/Linkly-HQ/linkly-mcp-server
Website
linklyhq.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 A servers

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