Marketing

linkpulse.dev

Tracks affiliate revenue, identifies at-risk and broken links, and suggests replacement products for dead URLs.

1 endpoint5 known toolsFirst detected August 28, 2026Last detected August 28, 2026

ENDPOINT 1

https://api.linkpulse.dev/mcp

No auth detected

MCP server metadata

Name: linkpulse
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

LinkPulse exposes affiliate revenue and broken-link intelligence for a single WordPress site. Use revenue_summary + top_articles for "how much am I earning" questions, at_risk_articles for "where am I losing money" questions, broken_links for the full scanner state, and suggest_replacement when you have a specific dead affiliate URL and want an alternative to propose. All data is scoped to the current license holder — you cannot see other users' sites.

Known tools 5

revenue_summary

Total affiliate commissions for the current site over a window (default 30 days), with transaction count, average commission, and delta vs.

Inferred read-only

top_articles

Articles on the current site that generated the most commission over a window.

Inferred read-only

at_risk_articles

Articles that are earning affiliate commissions AND have broken affiliate links on the page — the revenue currently leaking each month.

Inferred read-only

broken_links

All broken affiliate links currently flagged by the LinkPulse scanner on this site.

Inferred read-only

suggest_replacement

Given a broken or dead affiliate URL plus the article it sits on, ask Claude (with web search) to find the closest-available alternative product on the same retailer or network.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.linkpulse]
url = "https://api.linkpulse.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "linkpulse": {
      "type": "http",
      "url": "https://api.linkpulse.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: linkpulse
Remote MCP URL: https://api.linkpulse.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "linkpulse": {
      "url": "https://api.linkpulse.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "linkpulse": {
      "type": "http",
      "url": "https://api.linkpulse.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "linkpulse",
  "transport": "streamable-http",
  "url": "https://api.linkpulse.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.