Missinglinkz

What is Missinglinkz?

Missinglinkz is campaign link infrastructure for AI agents and developers. It validates destination URLs and inspects landing pages before publishing, returning a structured go/no-go report from a single mlz_preflight call, preventing ad spend on 404s or broken social previews.

How to use Missinglinkz?

Install globally with npm install -g missinglinkz, then start the MCP server using mlz mcp. The server exposes 13 tools (e.g., mlz_preflight, mlz_build_link, mlz_inspect_destination) that can be invoked from any MCP-compatible client.

Key features of Missinglinkz

• One-command preflight: build + validate + inspect in a single call
• Landing‑page inspection: OG tags, Twitter Cards, viewport, canonical, favicon
• Destination validation: SSL, resolution, redirect chains, response time
• Naming normalization (lowercase, hyphenated, no special characters)
• Shared, server‑enforced UTM taxonomy for team governance (Team plan)
• Free tier: 1,000 links/month, no credit card required

Use cases of Missinglinkz

• Pre‑publish campaign check to avoid wasting ad spend on broken pages
• Enforce consistent UTM naming across a marketing team
• Block broken links from reaching production by integrating into CI/CD
• Inspect landing‑page social sharing readiness before a launch

FAQ from Missinglinkz

Is there a free tier?

Yes, the free tier includes 1,000 links per month with no credit card required.

What dependencies are needed to run Missinglinkz?

The MCP server requires Node.js and is installed via npm (npm install -g missinglinkz).

How do I authenticate with the Missinglinkz API?

Authentication is handled through the mlz_register tool to create an account, after which API keys or workspace seat keys are used. Team plans support minting/revoking workspace seat keys via mlz_manage_seats.

Can Missinglinkz be used in CI/CD pipelines?

Yes. The MCP tools return pass/fail exit codes, allowing broken links to be detected and blocked before a deployment.

What happens when a destination URL is broken?

The validation step checks SSL, resolution, redirect chains, and response time. The inspection step checks social tags. If any check fails, the report flags a no‑go status, and the link is not used.