com.linklyhq/linkly

MCPcommunitylive
v2.0.0com.linklyhqUnknownUpdated 3mo agoGitHub

Create and manage short links, track clicks, and automate URL management

Endpoint healthlive
checked 10 days ago · 158ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3mo agoLast update
Package
Authorcom.linklyhq
LicenseUnknown
Version2.0.0
Sourcemcp-registry
GitHubLinkly-HQ/linkly-mcp-server
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface20 tools · 2 privileged
Security scan✓ Cleanv1.4.0 · 3mo agoHow well does this scan work?
PROMPTdescriptionLinks to undeclared domain: mcp.linklyhq.com
EvalsNone
IndexedJun 22, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

20 tools · 2 privileged
Statically extracted from the published packagev1.4.0 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

create_linkNo description published

This tool published no description. Forge does not invent one.

update_linkNo description published

This tool published no description. Forge does not invent one.

delete_linkprivilegedNo description published

This tool published no description. Forge does not invent one.

get_linkNo description published

This tool published no description. Forge does not invent one.

list_linksNo description published

This tool published no description. Forge does not invent one.

get_clicksNo description published

This tool published no description. Forge does not invent one.

get_analyticsNo description published

This tool published no description. Forge does not invent one.

get_analytics_byNo description published

This tool published no description. Forge does not invent one.

export_clicksNo description published

This tool published no description. Forge does not invent one.

list_domainsNo description published

This tool published no description. Forge does not invent one.

create_domainNo description published

This tool published no description. Forge does not invent one.

delete_domainprivilegedNo description published

This tool published no description. Forge does not invent one.

update_domain_faviconNo description published

This tool published no description. Forge does not invent one.

search_linksNo description published

This tool published no description. Forge does not invent one.

list_webhooksNo description published

This tool published no description. Forge does not invent one.

subscribe_webhookNo description published

This tool published no description. Forge does not invent one.

unsubscribe_webhookNo description published

This tool published no description. Forge does not invent one.

list_link_webhooksNo description published

This tool published no description. Forge does not invent one.

subscribe_link_webhookNo description published

This tool published no description. Forge does not invent one.

unsubscribe_link_webhookNo description published

This tool published no description. Forge does not invent one.

0 of 20 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Create and manage short links, track clicks, and automate URL management

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

20 tools · 2 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.