Home / MCP registry index / com.linklyhq/linkly
com.linklyhq/linkly
com.linklyhq/linkly in the official MCP registry.
Endpoint https://mcp.linklyhq.com/. Source: github.com/Linkly-HQ/linkly-mcp-server.
The registry describes it as: Create and manage short links, track clicks, and automate URL management
We read its 25 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
test_authentication list_workspaces batchDeleteLinks update_workspace list_links ping create_link update_link delete_link get_link get_clicks get_analytics get_analytics_by export_clicks list_domains create_domain delete_domain update_domain_favicon search_links list_webhooks subscribe_webhook unsubscribe_webhook list_link_webhooks subscribe_link_webhook unsubscribe_link_webhook
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-linklyhq-linkly)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.