Linkonda
NPM · @VERANOAPP/LINKONDA-MCP
Create and manage Linkonda short links from an AI assistant, with no per-visitor tracking.
Available components
Last scanned (10 hours ago)
Scores higher than 81% of npm servers
Category Marketing and SEO
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
- 30 of 92 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 19 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 854 tokens (~122/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 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
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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 16 Oct 26 +1
- Stability: 0.83 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.83 → pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: pass → fail ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.3 → 0.1.5 functional
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed npm/@veranoapp/linkonda-mcp@0.1.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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
check_quota Check remaining link allowance ~44
Report how many links are live and how many the current plan allows. Without an API key this reports the anonymous allowance. Use it before a bulk create to check for room.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
delete_link Delete a short link ~153
Delete a short link. This can't be undone: the short URL stops working immediately, anyone who already has it gets a 404, and the link leaves the account's list. Its short URL is never given to another link. Prefer update_link with paused:true if the link might be needed again. Requires an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| linkId | string | – | Optional. Needed only when more than one of your links uses this short code, on different hosts: the call then fails with SLUG_AMBIGUOUS and lists each link's linkId. Call again with the same slug an… |
| slug | string | yes | The link's short code (the part after the domain). |
No output schema declared.
No examples provided.
get_link_stats Get a short link's click count ~177
Return the total number of times a short link has been followed. Linkonda stores no per-visitor information, so there is no geographic, device or referrer breakdown to report. For an A/B split link it also returns each variant's count, but only to the link's owner, through that account's API key (paid plans). Without host it looks the short code up on Linkonda's own short-link host; set host for a link on a custom domain. No API key needed for the total.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | Optional. The hostname of the custom domain the link is on, such as links.example.com, without https:// or a path. Omit it for a link on Linkonda's own short-link host. |
| slug | string | yes | The link's short code (the part after the domain). |
No output schema declared.
No examples provided.
list_links List my short links ~45
List the 100 most recently created short links on the authenticated account (paused and expired ones included, deleted ones not), with their destinations and total redirect counts. Requires an API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
shorten_link Shorten a URL ~228
Create a short link for a URL. Works without an API key (anonymous links expire and are not saved to an account). When a short link is followed, Linkonda counts the click and records nothing about the visitor: no IP address, location, device data or referrer. Use when the user wants a short or shareable URL, or a link for a QR code.
| Name | Type | Req | Description |
|---|---|---|---|
| expiresInDays | integer | – | Optional. The link stops redirecting after this many days: it then answers 410 Gone, stays on the account, and its short URL is never reused. Requires a Pro or Enterprise plan. Omit it on other plans… |
| slug | string | – | Don't set this. Custom short codes are not available on any plan, and the API refuses a request that sets slug. Omit it to get a generated short code. |
| url | string | yes | The destination URL to shorten. Must be absolute, e.g. https://example.com/page |
No output schema declared.
No examples provided.
shorten_links_bulk Shorten many URLs at once ~53
Create up to 100 short links in a single request. Requires an API key. Use this instead of calling shorten_link repeatedly when shortening several URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| links | array | yes | Up to 100 links to create. |
No output schema declared.
No examples provided.
update_link Update or pause a short link ~154
Change a short link's destination, or pause/resume it. A paused link stops redirecting but is not deleted. Requires an API key. Changing the destination requires a paid plan.
| Name | Type | Req | Description |
|---|---|---|---|
| linkId | string | – | Optional. Needed only when more than one of your links uses this short code, on different hosts: the call then fails with SLUG_AMBIGUOUS and lists each link's linkId. Call again with the same slug an… |
| paused | boolean | – | true to stop the link redirecting, false to resume it. |
| slug | string | yes | The link's short code (the part after the domain). |
| url | string | – | New destination URL. |
No output schema declared.
No examples provided.
How do I install the Linkonda MCP server?
Linkonda runs locally as an npm package, launched with npx -y @veranoapp/linkonda-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @veranoapp/linkonda-mcp
claude mcp add com-linkonda-mcp -- npx -y @veranoapp/linkonda-mcp
What is the Linkonda MCP server?
Linkonda is an MCP server listed in the public MCP registry as com.linkonda/mcp. Create and manage Linkonda short links from an AI assistant, with no per-visitor tracking. This page covers its npm package (@veranoapp/linkonda-mcp).
Is the Linkonda MCP server safe to use?
Linkonda scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 Linkonda MCP server expose?
Linkonda exposes 7 tools: shorten_link, shorten_links_bulk, list_links, update_link, delete_link, and 2 more. Their descriptions and schemas cost roughly 854 tokens of context every time the server is loaded.
Is the Linkonda MCP server still maintained?
Linkonda is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Linkonda MCP server under?
Linkonda declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.