MissingLinkz
NPM · MISSINGLINKZ
Campaign link infrastructure for AI agents — validate, build, and inspect UTM-tracked links.
Available components
Last scanned (21 hours ago)
Scores higher than 51% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 151 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1491 tokens (~93/item across 16 items; 16 tools + 0 resources), lean.Pass
- 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 16 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 18 Nov 26 +1
- Stability: 0.97 → pass security
- 17 Nov 26 −1
- Stability: pass → 0.97 functional
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 9 Nov 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.
- 7 Nov 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.
- 5 Nov 26 −3
- Stability: pass → 0.80 functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.93 functional
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 Nov 2026 · Analysed npm/missinglinkz@1.1.7
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| 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 →
mlz_build_link ~139
Generate a UTM-tagged campaign link with enforced naming conventions. Calls POST /v1/links to store the link. Falls back to local generation if unauthenticated.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign | string | yes | Campaign name (will be auto-sanitized) |
| content | string | – | Content variant for A/B testing (optional) |
| medium | string | yes | Marketing medium, e.g. social, cpc, email |
| source | string | yes | Traffic source, e.g. linkedin, google, newsletter |
| term | string | – | Paid keyword (optional) |
| url | string | yes | Destination URL (must be a valid URL) |
No output schema declared.
No examples provided.
mlz_check_usage ~31
Check current API usage, plan tier, and remaining link quota. Calls GET /v1/auth/status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mlz_get_taxonomy ~48
Get the account's strict taxonomy state and allowed source/medium dictionary. Calls GET /v1/taxonomy. Returns plan, whether enforcement is available/on, and the allowed values.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mlz_inspect_destination ~80
Inspect a destination URL for social sharing readiness. Checks Open Graph tags, Twitter Card tags, viewport, canonical URL, favicon, existing UTM parameters, and page load time. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| timeout_ms | number | – | Request timeout in milliseconds (default: 15000) |
| url | string | yes | The URL to inspect |
No output schema declared.
No examples provided.
mlz_inspect_url ~79
Inspect a destination URL to extract metadata: Open Graph tags, Twitter Card meta, favicon presence, and page load time. Useful for verifying social sharing previews before publishing.
| Name | Type | Req | Description |
|---|---|---|---|
| timeout_ms | number | – | Request timeout in milliseconds (default: 15000) |
| url | string | yes | Destination URL to inspect (must be a valid URL) |
No output schema declared.
No examples provided.
mlz_list_campaigns ~33
List all campaigns for this account. Calls GET /v1/campaigns. Requires MLZ_API_KEY.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mlz_list_links ~59
List recently generated links, optionally filtered by campaign name. Calls GET /v1/links.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign | string | – | Filter links by campaign name |
| limit | number | – | Maximum number of links to return (default: 20) |
No output schema declared.
No examples provided.
mlz_list_seats ~53
List the workspace's seats (API keys), the plan's seat limit, and usage. Calls GET /v1/seats. Each active key is a seat sharing the same campaigns, links, and taxonomy.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mlz_manage_seats ~115
Manage workspace seats (Team plan, owner key required). action='create' mints a new seat API key (returned once; optional label). action='revoke' revokes a seat by id. Useful for an orchestrator agent provisioning keys for its sub-agents.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Mint a new seat or revoke one |
| id | string | – | Seat id to revoke (required for action='revoke') |
| label | string | – | Optional label for the new seat (action='create') |
No output schema declared.
No examples provided.
mlz_preflight ~185
Pre-publish campaign link check. Builds a UTM-tagged link, validates the destination URL, and inspects the page for social sharing readiness (Open Graph tags, Twitter Cards, viewport, canonical URL, favicon, UTM conflicts). Returns a go/no-go report with recommendations. Use this before publishing any campaign link.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign | string | yes | Campaign name (will be auto-sanitized) |
| content | string | – | Content variant for A/B testing (optional) |
| medium | string | yes | Marketing medium, e.g. social, cpc, email |
| share | boolean | – | Publish a shareable report URL (Team plan) |
| source | string | yes | Traffic source, e.g. linkedin, google, newsletter |
| term | string | – | Paid keyword (optional) |
| url | string | yes | Destination URL (must be a valid URL) |
No output schema declared.
No examples provided.
mlz_publish_check ~206
Full pre-publish checklist. Builds a UTM-tagged link and runs all validations: URL resolution, SSL, redirects, Open Graph, Twitter Card, favicon, load time, character count, hashtags, image dimensions, and CTA detection. Returns a tracked link + comprehensive validation report. Supported platforms: x, linkedin, facebook, instagram, threads.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign | string | yes | Campaign name |
| content | string | – | Content variant for A/B testing (optional) |
| copy | string | yes | Post copy text |
| image_height | number | – | Image height in pixels (optional) |
| image_width | number | – | Image width in pixels (optional) |
| medium | string | yes | Marketing medium, e.g. social, cpc, email |
| platform | string | yes | Target platform |
| source | string | yes | Traffic source, e.g. linkedin, google |
| term | string | – | Paid keyword (optional) |
| url | string | yes | Destination URL |
No output schema declared.
No examples provided.
mlz_register ~57
Register a new MissingLinkz account. Returns an API key that should be set as the MLZ_API_KEY environment variable. Free tier includes 1,000 links/month.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address for the new account |
No output schema declared.
No examples provided.
mlz_set_taxonomy ~165
Configure strict UTM taxonomy (Team plan). action='allow' adds allowed values (needs field + values), action='disallow' removes one (needs field + value), action='strict' turns enforcement on/off (needs strict=true|false). Once strict is on, building a link with an off-dictionary source/medium is rejected. Requires a Team/Enterprise plan.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What to do |
| field | string | – | Which UTM field (required for allow/disallow) |
| strict | boolean | – | Turn enforcement on/off (required for action='strict') |
| value | string | – | Value to remove (required for action='disallow') |
| values | array | – | Allowed values to add (required for action='allow') |
No output schema declared.
No examples provided.
mlz_suggest_naming ~73
Suggest consistent naming for sources or mediums based on campaign history. Calls GET /v1/campaigns/suggest. Helps prevent inconsistencies like 'facebook' vs 'fb'.
| Name | Type | Req | Description |
|---|---|---|---|
| medium | string | – | Medium to get naming suggestions for |
| source | string | – | Source to get naming suggestions for |
No output schema declared.
No examples provided.
mlz_validate_content ~97
Validate social media post content against platform-specific rules. Checks character count, hashtag count, image dimensions, and CTA presence. Supported platforms: x, linkedin, facebook, instagram, threads.
| Name | Type | Req | Description |
|---|---|---|---|
| copy | string | yes | The post copy text to validate |
| image_height | number | – | Image height in pixels (optional) |
| image_width | number | – | Image width in pixels (optional) |
| platform | string | yes | Target platform |
No output schema declared.
No examples provided.
mlz_validate_url ~71
Validate a destination URL before using it in a campaign link. Checks URL format, SSL, resolution, redirect chain, and response time. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| timeout_ms | number | – | Request timeout in milliseconds (default: 10000) |
| url | string | yes | The URL to validate |
No output schema declared.
No examples provided.
How do I install the MissingLinkz MCP server?
MissingLinkz runs locally as an npm package, launched with npx -y missinglinkz 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 · missinglinkz
claude mcp add andrewlamamills-tech-missinglinkz -- npx -y missinglinkz mcp
What is the MissingLinkz MCP server?
MissingLinkz is an MCP server listed in the public MCP registry as io.github.andrewlamamills-tech/missinglinkz. Campaign link infrastructure for AI agents, validate, build, and inspect UTM-tracked links. This page covers its npm package (missinglinkz).
Is the MissingLinkz MCP server safe to use?
MissingLinkz scores 75 out of 100 on VerifyMCP. We recorded 1 known advisory against 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 MissingLinkz MCP server expose?
MissingLinkz exposes 16 tools: mlz_build_link, mlz_list_campaigns, mlz_suggest_naming, mlz_get_taxonomy, mlz_set_taxonomy, and 11 more. Their descriptions and schemas cost roughly 1,491 tokens of context every time the server is loaded.
Is the MissingLinkz MCP server still maintained?
MissingLinkz 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 MissingLinkz MCP server under?
MissingLinkz 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 MissingLinkz MCP server?
VerifyMCP ran 15 checks on MissingLinkz, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about MissingLinkz: Security disclosure. 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.