MCP.Market

SEO Tools: A-Parser bridge MCP server

by antohins·io.github.antohins/seo-tools-mcp-aparser·v1.8.0·8 stars
No reviews yet

Bridge to a self-hosted A-Parser: SERP, suggests and 150+ parsers via its API (read-only).

B83/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

8 stars76 downloads/wk

Reviews

Write one

Nobody has reviewed SEO Tools: A-Parser bridge yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

SEO Tools: A-Parser bridge tools (11)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • aparser_bulk_request
  • aparser_get_preset
  • aparser_parser_fields
  • aparser_parsers

    \u0421\u043F\u0438\u0441\u043E\u043A \u043F\u0430\u0440\u0441\u0435\u0440\u043E\u0432, \u0443\u0441\u0442\u0430\u043D\u043E\u0432\u043B\u0435\u043D\u043D\u044B\u0445 \u043D\u0430 \u0438\u043D\u0441\u0442\u0430\u043D\u0441\u0435 A-Parser (\u0438\u0437 \u043C\u0435\u0442\u043E\u0434\u0430 info). \u041F\u043E\u043B\u0435\u0437\u043D\u043E \u043F\u0435\u0440\u0435\u0434 aparser_request/aparser_parser_

  • aparser_ping

    \u041F\u0440\u043E\u0432\u0435\u0440\u043A\u0430 \u0441\u0432\u044F\u0437\u0438 \u0441 A-Parser \u0438 \u043F\u0430\u0440\u043E\u043B\u044F API (\u043C\u0435\u0442\u043E\u0434 ping). \u0411\u044B\u0441\u0442\u0440\u044B\u0439 \u0441\u043F\u043E\u0441\u043E\u0431 \u0443\u0431\u0435\u0434\u0438\u0442\u044C\u0441\u044F, \u0447\u0442\u043E \u0438\u043D\u0441\u0442\u0430\u043D\u0441 \u0434\u043E\u0441\

  • aparser_proxies
  • aparser_request
  • aparser_serp_google
  • aparser_serp_yandex
  • aparser_status
  • aparser_suggest

Public scan report

scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it

no findings
  • Code scan2 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 8 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How SEO Tools: A-Parser bridge compares

Against every graded SEO MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 70% of 769 SEO servers
Tools
11
the typical SEO server has 6
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
8
more than 89% of 406 SEO servers
Downloads a week
76
more than 53% of 172 SEO servers with a package

What its tools let an agent do: 11 read

Install SEO Tools: A-Parser bridge in Claude Code, Cursor or VS Code

Runs npx -y seo-tools-mcp-aparser on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add seo-tools-mcp-aparser -- npx -y seo-tools-mcp-aparser
Add to Cursor

What the publisher says

From the SEO Tools: A-Parser bridge repository's README, as published. We do not edit it. Read it on GitHub

seo-tools-mcp

Русский | English

Восемь универсальных stdio MCP-серверов для SEO: доступ к SERP, Wordstat, Google Search Console, Google Analytics 4, Яндекс.Вебмастеру, Яндекс.Метрике и self-hosted A-Parser прямо из Claude Code (и любого MCP-клиента). Все инструменты read-only — ничего не публикуют и не меняют в твоих аккаунтах, вывод — строгий JSON. Машиночитаемо это заявлено аннотацией readOnlyHint; её намеренно нет у двадцати инструментов, каждый вызов которых тратит платный ресурс (запрос к XMLStock/XMLRiver, прокси-трафик A-Parser) — иначе клиент счёл бы их безобидными и перестал спрашивать подтверждение перед прогоном по большому пулу. К конкретному сайту не привязаны: дефолты (свойство GSC, свойство GA4, хост Вебмастера, счётчик Метрики) настраиваются на лету.

🛰 Эти серверы мы используем в продакшене в PBN Workers — инфраструктура поискового топа: семантика, PBN и сателлиты, автоматизация SEO. Нужен стабильный органический трафик — приходите.

Где опубликовано: npm (восемь пакетов), официальный MCP Registry, GitHub MCP Registry (все восемь серверов), маркетплейс плагинов Claude Code (см. ниже) и .mcpb-бандлы в релизах.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

SEO Tools: A-Parser bridge: common questions

Is SEO Tools: A-Parser bridge MCP server safe?
Mostly: it is graded B (83/100). Read the SEO Tools: A-Parser bridge safety report
How do I install SEO Tools: A-Parser bridge?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does SEO Tools: A-Parser bridge need an API key?
Yes. The registry entry asks for APARSER_PASSWORD.
Is SEO Tools: A-Parser bridge maintained?
The last commit was 13 days ago (2026-10-23). The latest release is v1.8.0.
What can I use instead of SEO Tools: A-Parser bridge?
Servers from other publishers that do the same job: Open SEO Crawler MCP server, Librecrawl — Technical SEO Audit MCP Server and Notipo MCP server. Compare all SEO Tools: A-Parser bridge alternatives.
How does SEO Tools: A-Parser bridge compare with other SEO MCP servers?
safety score 83/100 (higher than 70% of 769 SEO servers); tools 11 (the typical SEO server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to SEO Tools: A-Parser bridge

Same job from other publishers: the closest match first, then the best rated.

All SEO Tools: A-Parser bridge alternatives →
  • Open SEO Crawler
    Self-hosted SEO crawler: run site audits and AI crawler checks, then read the issues and pages.
    A
  • Librecrawl — Technical SEO Audit MCP Server
    Self-hosted technical SEO audit MCP. 50+ checks, WAF detection, ephemeral. Built on LibreCrawl.
    B
  • Notipo
    Publish to self-hosted WordPress from AI agents: markdown, images, SEO, and Notion sync.
    A
  • Crawlie
    Technical SEO + GEO (AI-search) site audits: hosted crawls, prioritized fixes, report diffs.
    A
  • webfetch
    Self-hosted web search for LLM agents: search -> fetch -> rank pipeline with semantic caching
    B

More from antohins →