io.github.hellovelop/limelink-mcp-server

Name: io.github.hellovelop/limelink-mcp-server
Rating: 60 (1 reviews)
Author: io.github.hellovelop

MCPcommunity

v0.0.5io.github.hellovelopUnknownUpdated 4mo agonpm GitHub

MCP server for Limelink dynamic links with deep linking, social previews, and UTM tracking

A Model Context Protocol (MCP) server for LimeLink dynamic link management. Create, look up, and manage dynamic links directly from Claude Code, Claude Desktop, or any MCP-compatible client. No API key required to get started! Documentation, SDK setup guides, and prompt templates work without any configuration. Just connect and start exploring LimeLink features with your AI assistant.…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

4mo agoLast update

Package

Authorio.github.hellovelop

LicenseUnknown

Version0.0.5

Sourcemcp-registry

npmlimelink-mcp-server

GitHubhellovelop/limelink-mcp-server

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/10

→ 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>" }

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

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 surface3 tools · none privileged

Security scan✓ Cleanv0.0.5 · 20d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp