Seo Backlinks
Server Details
SEO Backlinks MCP — backlink intelligence via DataForSEO Backlinks API
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 36.8% over 39 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-seo-backlinks
- GitHub Stars
- 0
- Server Listing
- mcp-seo-backlinks
TDQS
Scored across 36 tools
Several tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded and deep_research all do the same routing-style lookups (beta is explicitly 'identical' to stable), and polymarket_edges vs polymarket_arbitrage vs polymarket_edge_tracker vs polymarket_fill_risk blur together. The SEO backlink tools are distinct, but the router and polymarket clusters create real misselection risk.
Nearly everything follows snake_case with predictable prefixes (ask_pipeworx*, seo_backlinks_*, polymarket_*, ask_pipeworx etc.), which is easy to read. Minor deviation: a handful of bare verbs (remember, forget, recall, subscribe, unsubscribe) break the prefix/domain pattern but remain consistent in style.
36 tools is very heavy, and only about 5-7 (seo_backlinks_*, seo_referring_domains, generate_llms_txt) relate to the server's stated SEO backlink purpose. The rest are a general Pipeworx research/market gateway, so the count is far beyond what the named scope justifies.
For a backlink-analysis domain the pack covers summary, list, anchors, referring domains and history, but lacks obvious operations like a competitor backlink gap / link intersect, broken-backlink or domain-overview views. The unrelated meta-tools make total coverage broad but not aligned with the stated purpose.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "will-bitcoin-reach-100k-in-july-2026" - }, - { - "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026" - } -]New value: +[ + { + "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination" + }, + { + "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
1 tool update
- Changed
entity_profile3 fields changed- changed
Input schema / properties / type / descriptionPrevious value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon." - changed
Input schema / properties / type / enumPrevious value: -[ - "company" -]New value: +[ + "company", + "ticker" +] - changed
Input schema / properties / value / descriptionPrevious value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
Related MCP Connectors
SEO SERP MCP — Google organic search results via DataForSEO (dataforseo.com)
GoAnyAPI SEO MCP: traffic, DR, backlinks, keywords, Google/Bing SERP/autocomplete, Ads Transparency.
SEO MCP server — backlinks, domain authority, tech stack, and 18+ tools via Common Crawl.
SEO Keywords MCP — search volume & difficulty via DataForSEO Labs (dataforseo.com)
Related MCP Servers
- AlicenseAqualityDmaintenanceFind backlink opportunities, analyze competitors, discover similar domains with AI embeddings, and manage prospecting projects directly from any MCP client.15MIT
- AlicenseBqualityDmaintenanceA MCP server for retrieving backlink information for any domain(SEO).430 PyPI260MIT
- AlicenseAqualityCmaintenanceSEO MCP over Search Console, GA4, PageSpeed, Cloudflare, IndexNow, CrUX, and 7 technical-SEO HTTP tools.70112 PyPI279MIT
- FlicenseNot gradedqualityBmaintenanceProvides SEO audits, content analysis, and domain overviews through an MCP server, including on-page, technical, and authority metrics with built-in browser rendering and anti-bot handling.-
Glama MCP Gateway
Add one secure layer between your agents and this server.