# io.github.CloudCorpRecords/linkledger (npm · @reneturcios/linkledger)

Manage your Linkly short links, domains, webhooks and click analytics.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@reneturcios/linkledger`: 70/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-linkledger/reneturcios-linkledger.md), [page](https://verifymcp.io/servers/cloudcorprecords-linkledger/reneturcios-linkledger)
- oci · `ghcr.io/cloudcorprecords/linkledger`: 41/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-linkledger/ghcr-io-cloudcorprecords-linkledger.md), [page](https://verifymcp.io/servers/cloudcorprecords-linkledger/ghcr-io-cloudcorprecords-linkledger)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/linkledger`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1928 tokens (~77/item across 25 items; 25 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 98% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "batchDeleteLinks" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.CloudCorpRecords/linkledger MCP server?

io.github.CloudCorpRecords/linkledger runs locally as an npm package, launched with npx -y @reneturcios/linkledger mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-linkledger -- npx -y @reneturcios/linkledger mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-linkledger": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/linkledger",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-linkledger": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/linkledger",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-linkledger -- npx -y @reneturcios/linkledger mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-linkledger": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/linkledger",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-linkledger --command npx --arg -y --arg @reneturcios/linkledger --arg mcp
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-linkledger:
    command: "npx"
    args: ["-y", "@reneturcios/linkledger", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-linkledger": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/linkledger",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-linkledger -t stdio -c npx -a -y @reneturcios/linkledger mcp
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-linkledger": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/linkledger",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-16 (score 53)

First indexed and scored.

## MCP tools (25)

### `test_authentication` (~13 tokens)

Test API Authentication

### `list_workspaces` (~15 tokens)

Return details of authenticated workspace

### `batchDeleteLinks` (~27 tokens)

Batch delete multiple links

Input parameters:

- `ids` (array, required): Array of link IDs to delete

### `update_workspace` (~77 tokens)

Update workspace settings. Only the fields provided are changed; omitted fields keep their current values.

Input parameters:

- `name` (string): Workspace name
- `webhooks` (array): REPLACES the workspace's full webhook subscription list. Omit to leave webhooks unchanged; prefer subscribe_webhook / unsubscribe_webhook for adding or removing a single URL.

### `list_links` (~61 tokens)

List links with sorting and search

Input parameters:

- `page` (integer)
- `page_size` (integer)
- `search` (string): Search Query
- `sort_by` (string): Field to sort by
- `sort_dir` (string): Sort direction

### `ping` (~52 tokens)

Health check: sends a message to the hosted Linkly server and returns its reply unchanged, confirming the service is reachable and responding.

Input parameters:

- `message` (string, required): a message to ping , default to Hello From Linkkly

### `create_link` (~434 tokens)

Create short links and URL shorteners. Use this when the user asks to shorten a URL, create a short link, or make a link shorter.

Input parameters:

- `block_bots` (boolean): Block known bots and spiders from following the link
- `cloaking` (boolean): Hide destination URL by opening in an iframe
- `domain` (string): Custom domain for the short link (without trailing /). Must be a domain that already belongs to this workspace — call list_domains to get valid values. Required whenever slug is set.
- `enabled` (boolean): Whether the link is active (default: true)
- `expiry_datetime` (string): ISO 8601 datetime when the link should expire
- `expiry_destination` (string): Fallback URL after expiry (404 if blank)
- `fb_pixel_id` (string): Meta/Facebook Pixel ID for tracking
- `forward_params` (boolean): Forward URL parameters to the destination
- `ga4_tag_id` (string): Google Analytics 4 tag ID
- `gtm_id` (string): Google Tag Manager container ID
- `hide_referrer` (boolean): Hide referrer information when users click
- `name` (string): A nickname for the link to identify it later
- `note` (string): A private note about this link
- `og_description` (string): Open Graph description for social media previews
- `og_image` (string): Open Graph image URL for social media previews
- `og_title` (string): Open Graph title for social media previews
- `slug` (string): Custom slug/suffix for the link (must start with /). Only valid together with domain: setting slug without a workspace-owned domain is rejected by the API.
- `url` (string, required): The destination URL for the link (required)
- `utm_campaign` (string): UTM campaign parameter
- `utm_content` (string): UTM content parameter
- `utm_medium` (string): UTM medium parameter
- `utm_source` (string): UTM source parameter
- `utm_term` (string): UTM term parameter

### `update_link` (~294 tokens)

Update an existing Linkly link by its ID

Input parameters:

- `block_bots` (boolean): Block bots
- `cloaking` (boolean): Enable URL cloaking
- `enabled` (boolean): Whether the link is active
- `expiry_datetime` (string): Expiry datetime (ISO 8601)
- `expiry_destination` (string): Fallback URL after expiry
- `fb_pixel_id` (string): Meta Pixel ID
- `forward_params` (boolean): Forward URL parameters
- `ga4_tag_id` (string): Google Analytics 4 tag ID
- `gtm_id` (string): Google Tag Manager ID
- `hide_referrer` (boolean): Hide referrer
- `link_id` (integer, required): The ID of the link to update (required)
- `name` (string): New nickname for the link
- `note` (string): New private note
- `og_description` (string): Open Graph description
- `og_image` (string): Open Graph image URL
- `og_title` (string): Open Graph title
- `url` (string): New destination URL
- `utm_campaign` (string): UTM campaign parameter
- `utm_content` (string): UTM content parameter
- `utm_medium` (string): UTM medium parameter
- `utm_source` (string): UTM source parameter
- `utm_term` (string): UTM term parameter

### `delete_link` (~32 tokens)

Delete a Linkly link by its ID

Input parameters:

- `link_id` (integer, required): The ID of the link to delete

### `get_link` (~35 tokens)

Get details of a specific Linkly link by its ID

Input parameters:

- `link_id` (integer, required): The ID of the link to retrieve

### `get_clicks` (~32 tokens)

Get recent click data for the workspace

Input parameters:

- `link_id` (integer): Optional: filter clicks by link ID

### `get_analytics` (~182 tokens)

Get time-series click analytics data for charting. Returns click counts over time.

Input parameters:

- `bots` (string): Bot filtering: include (default), exclude, or only
- `browser` (string): Filter by browser name
- `country` (string): Filter by country code (e.g., 'US', 'GB')
- `end` (string): End date in YYYY-MM-DD format (default: today)
- `frequency` (string): Time granularity: 'day' (default) or 'hour'
- `link_id` (integer): Filter by specific link ID
- `platform` (string): Filter by platform (e.g., 'desktop', 'mobile', 'tablet')
- `start` (string): Start date in YYYY-MM-DD format (default: 30 days ago)
- `unique` (boolean): Count unique clicks only (by IP)

### `get_analytics_by` (~142 tokens)

Get click counts grouped by a dimension (country, platform, referrer, etc.). Useful for breakdowns and top-N reports.

Input parameters:

- `bots` (string): Bot filtering
- `counter` (string, required): Dimension to group by (required)
- `country` (string): Filter by country code
- `end` (string): End date in YYYY-MM-DD format (default: today)
- `link_id` (integer): Filter by specific link ID
- `platform` (string): Filter by platform
- `start` (string): Start date in YYYY-MM-DD format (default: 30 days ago)
- `unique` (boolean): Count unique clicks only

### `export_clicks` (~118 tokens)

Export detailed click records with full information (timestamp, browser, country, URL, platform, referer, bot, ISP, params).

Input parameters:

- `bots` (string): Bot filtering
- `country` (string): Filter by country code
- `end` (string): End date in YYYY-MM-DD format (default: yesterday)
- `link_id` (integer): Filter by specific link ID
- `platform` (string): Filter by platform
- `start` (string): Start date in YYYY-MM-DD format (default: 30 days ago)

### `list_domains` (~16 tokens)

List all custom domains in the workspace.

### `create_domain` (~47 tokens)

Add a custom domain to the workspace. The domain must be configured to point to Linkly's servers.

Input parameters:

- `name` (string, required): The domain name (e.g., 'links.example.com')

### `delete_domain` (~31 tokens)

Remove a custom domain from the workspace.

Input parameters:

- `domain_id` (integer, required): The ID of the domain to delete

### `update_domain_favicon` (~47 tokens)

Update the favicon URL for a custom domain.

Input parameters:

- `domain_id` (integer, required): The ID of the domain to update
- `favicon_url` (string, required): URL to the favicon image

### `search_links` (~45 tokens)

Search for links by name, URL, or note. Returns matching links with click statistics.

Input parameters:

- `query` (string, required): Search query to match against link names, URLs, and notes

### `list_webhooks` (~26 tokens)

List all webhook URLs subscribed to the workspace. These receive click events for all links.

### `subscribe_webhook` (~39 tokens)

Subscribe a webhook URL to receive click events for all links in the workspace.

Input parameters:

- `url` (string, required): The webhook URL to receive click event notifications

### `unsubscribe_webhook` (~31 tokens)

Unsubscribe a webhook URL from workspace click events.

Input parameters:

- `url` (string, required): The webhook URL to unsubscribe

### `list_link_webhooks` (~33 tokens)

List all webhook URLs subscribed to a specific link.

Input parameters:

- `link_id` (integer, required): The ID of the link

### `subscribe_link_webhook` (~51 tokens)

Subscribe a webhook URL to receive click events for a specific link.

Input parameters:

- `link_id` (integer, required): The ID of the link
- `url` (string, required): The webhook URL to receive click event notifications

### `unsubscribe_link_webhook` (~48 tokens)

Unsubscribe a webhook URL from a specific link's click events.

Input parameters:

- `link_id` (integer, required): The ID of the link
- `url` (string, required): The webhook URL to unsubscribe

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-linkledger/reneturcios-linkledger#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 70
- 2026-11-19: 69
- 2026-11-18: 69
- 2026-11-17: 68
- 2026-11-16: 53

## Common questions

### What is the io.github.CloudCorpRecords/linkledger MCP server?

io.github.CloudCorpRecords/linkledger is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/linkledger. Manage your Linkly short links, domains, webhooks and click analytics. This page covers its npm package (@reneturcios/linkledger).

### Is the io.github.CloudCorpRecords/linkledger MCP server safe to use?

io.github.CloudCorpRecords/linkledger scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 io.github.CloudCorpRecords/linkledger MCP server expose?

io.github.CloudCorpRecords/linkledger exposes 25 tools: test_authentication, list_workspaces, batchDeleteLinks, update_workspace, list_links, and 20 more. Their descriptions and schemas cost roughly 1,928 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/linkledger MCP server still maintained?

io.github.CloudCorpRecords/linkledger is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.CloudCorpRecords/linkledger MCP server under?

io.github.CloudCorpRecords/linkledger declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.CloudCorpRecords/linkledger MCP server?

VerifyMCP ran 16 checks on io.github.CloudCorpRecords/linkledger, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/linkledger
- Socket report: https://socket.dev/npm/package/@reneturcios/linkledger
- Repository: https://github.com/CloudCorpRecords/linkledger
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-linkledger/reneturcios-linkledger.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-linkledger/reneturcios-linkledger/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-linkledger/reneturcios-linkledger.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-linkledger/reneturcios-linkledger
