io.github.hellovelop/limelink-mcp-server
NPM · LIMELINK-MCP-SERVER · SCANNED SEP 21
MCP server for Limelink dynamic links with deep linking, social previews, and UTM tracking
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 30 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 556 tokens (~29/item across 19 items; 3 tools + 16 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.hellovelop/limelink-mcp-server server?
io.github.hellovelop/limelink-mcp-server runs locally as an npm package, launched with npx -y limelink-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · limelink-mcp-server
claude mcp add hellovelop-limelink-mcp-server -- npx -y limelink-mcp-server
{
"mcpServers": {
"hellovelop-limelink-mcp-server": {
"command": "npx",
"args": [
"-y",
"limelink-mcp-server"
]
}
}
} {
"servers": {
"hellovelop-limelink-mcp-server": {
"command": "npx",
"args": [
"-y",
"limelink-mcp-server"
]
}
}
} codex mcp add hellovelop-limelink-mcp-server -- npx -y limelink-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hellovelop-limelink-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"limelink-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add hellovelop-limelink-mcp-server --command npx --arg -y --arg limelink-mcp-server
mcp_servers:
hellovelop-limelink-mcp-server:
command: "npx"
args: ["-y", "limelink-mcp-server"] {
"McpServers": {
"hellovelop-limelink-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"limelink-mcp-server"
]
}
}
} assistant mcp add hellovelop-limelink-mcp-server -t stdio -c npx -a -y limelink-mcp-server
{
"mcpServers": {
"hellovelop-limelink-mcp-server": {
"command": "npx",
"args": [
"-y",
"limelink-mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/limelink-mcp-server@0.0.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create-link ~153
Create a Limelink dynamic link with platform-specific deep linking, social previews, and UTM tracking
| Name | Type | Req | Description |
|---|---|---|---|
| additional_options | object | – | Social preview and UTM tracking options |
| android_options | object | – | Android-specific deep linking options |
| apple_options | object | – | iOS-specific deep linking options |
| dynamic_link_name | string | yes | Link name for management and identification |
| dynamic_link_suffix | string | yes | Unique identifier for the short URL path |
| dynamic_link_url | string | yes | Target URL for desktop or fallback |
| project_id | string | – | Project ID the link belongs to. Uses LIMELINK_PROJECT_ID env if not provided. |
| stats_flag | boolean | – | Enable analytics tracking |
No output schema declared.
No examples provided.
get-link-by-suffix ~57
Look up a Limelink dynamic link by its suffix
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Project ID. Uses LIMELINK_PROJECT_ID env if not provided. |
| suffix | string | yes | Dynamic link suffix to look up |
No output schema declared.
No examples provided.
get-link-by-url ~86
Look up a Limelink dynamic link by its full URL. Supports both Free (deep.limelink.org) and Pro ({project}.limelink.org/link/) URL formats.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | – | Project ID. Uses LIMELINK_PROJECT_ID env if not provided. |
| url | string | yes | Full Limelink dynamic link URL to look up |
No output schema declared.
No examples provided.
What is the io.github.hellovelop/limelink-mcp-server server?
io.github.hellovelop/limelink-mcp-server is listed in the public MCP registry as io.github.hellovelop/limelink-mcp-server. MCP server for Limelink dynamic links with deep linking, social previews, and UTM tracking. This page covers its npm package (limelink-mcp-server).
Is the io.github.hellovelop/limelink-mcp-server server safe to use?
io.github.hellovelop/limelink-mcp-server scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.hellovelop/limelink-mcp-server server expose?
io.github.hellovelop/limelink-mcp-server exposes 3 tools: create-link, get-link-by-suffix, get-link-by-url. Their descriptions and schemas cost roughly 296 tokens of context every time the server is loaded.
Is the io.github.hellovelop/limelink-mcp-server server still maintained?
io.github.hellovelop/limelink-mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.hellovelop/limelink-mcp-server server under?
io.github.hellovelop/limelink-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.