Skip to content

Add backlink-guard MCP to marketing - #1277

Open
zhuyansen wants to merge 2 commits into
davila7:mainfrom
zhuyansen:add-backlink-guard-mcp
Open

zhuyansen wants to merge 2 commits into
davila7:mainfrom
zhuyansen:add-backlink-guard-mcp

Conversation

@zhuyansen

Copy link
Copy Markdown

Adds one MCP component:

  • cli-tool/components/mcps/marketing/backlink-guard.json

backlink-guard checks a link source (directory, awesome list, guest-post site) before you submit your site to it: each site gets an action (skip, look first, free only, low value, submit) and a verdict with the evidence, against Google's link spam policies. It also verifies a listing once it is live (followed or not, and where the link sits), audits your own backlink profile, and finds the pages that rank for your keywords, the sites linking to your competitors and not to you, who Google's AI Overviews cite, and what AI assistants answer and cite. It never submits anything. It is a local stdio server from the backlink-guard package on PyPI, started with uvx --with mcp backlink-guard mcp, with ten tools. MIT licensed.

What costs money: every key is optional. verify and submissions are free, and vet with free=True reads only the sites' own pages, also free. The other tools make paid calls through the user's own keys: GLASSER_API_KEY (or AISA_API_KEY, which questions and asked need) and GOANYAPI_API_KEY. vet is about $0.01 a site plus about $0.16 a batch. The env block is the one in the project's README; a key left out just leaves its signals out.

Checked locally: the file parses as JSON, and claude plugin validate (Claude Code 2.1.289) passes with the file as .mcp.json of a scratch plugin, the way scripts/validate_components.py wraps MCP components. No generated catalog files are included.

Testing, once merged: npx claude-code-templates@latest --mcp marketing/backlink-guard --dry-run

I maintain backlink-guard.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions github-actions Bot added the review-pending Component PR awaiting maintainer review label Oct 26, 2026
@github-actions

Copy link
Copy Markdown
Contributor

👋 Thanks for contributing, @zhuyansen!

This PR touches cli-tool/components/** and has been marked review-pending.

What happens next

  1. 🤖 Automated security audit runs and posts results on this PR.
  2. 👀 Maintainer review — a human reviewer validates the component with the component-reviewer agent (format, naming, security, clarity).
  3. ✅ Merge — once approved, your PR is merged to main.
  4. 📦 Catalog regeneration — the component catalog is rebuilt automatically.
  5. 🚀 Live on aitmpl.com — your component appears on the website after deploy.

⚠️ Do not commit generated catalog files

Please make sure your PR does not include docs/components.json or anything under dashboard/public/
(components.json, counts.json, search-index.json, components/*.json, component-content/**, api/v1/**).
Those files are regenerated automatically by scripts/generate_components_json.py after merge, and committing them causes merge conflicts.
If you already ran the script, revert them with: git checkout origin/main -- docs/components.json dashboard/public/

While you wait

  • Check the Security Audit comment below for any issues to fix.
  • Make sure your component follows the contribution guide.

This is an automated message. No action is required from you right now — a maintainer will review soon.

@greptile-apps

greptile-apps Bot commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable issues were found.

Summary

Adds marketing/backlink-guard, a local MCP server launched with uvx.

  • Marketing projects can use backlink-guard to check link sources.

Reviews (1) · Last reviewed commit: "Add backlink-guard MCP to marketing" · Reviewed by Greptile

davila7 commented Nov 18, 2026 •

Copy link
Copy Markdown
Owner

Thanks for the contribution! Triage found nothing to change: re-checked after the new push: pinned to backlink-guard==0.12.0 with public source, and the keys come from ${GLASSER_API_KEY} and ${GOANYAPI_API_KEY}. A maintainer does the final review and merge.


Generated by Claude Code

@davila7 davila7 added the triage:changes Triage routine: changes requested in a comment label Nov 18, 2026 — with Claude
@zhuyansen

Copy link
Copy Markdown
Author

Thanks, both done: the package is pinned to backlink-guard==0.12.0 and the keys read ${GLASSER_API_KEY} and ${GOANYAPI_API_KEY}.

@davila7 davila7 removed the triage:changes Triage routine: changes requested in a comment label Nov 21, 2026
@davila7 davila7 added the triage:accept Triage routine: ready to merge as is label Nov 21, 2026 — with Claude

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

review-pending Component PR awaiting maintainer review triage:accept Triage routine: ready to merge as is

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants