SEO Tools: A-Parser bridge
SEO Tools: A-Parser bridge is an MCP server published by antohins, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does SEO Tools: A-Parser bridge support the current MCP specification (2026-07-28)?
Not yet confirmed. SEO Tools: A-Parser bridge is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is SEO Tools: A-Parser bridge a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for SEO Tools: A-Parser bridge (as of 2026-08-20).
How do I connect to SEO Tools: A-Parser bridge?
SEO Tools: A-Parser bridge is available via the package npm:seo-tools-mcp-aparser, the official MCP Registry under io.github.antohins/seo-tools-mcp-aparser, the source repository at https://github.com/antohins/seo-tools-mcp. Authentication: unknown. Transports: stdio.
Does SEO Tools: A-Parser bridge support MCP revision 2025-11-25?
Yes. SEO Tools: A-Parser bridge supports MCP revision 2025-11-25 (checked 2026-08-20).
Does SEO Tools: A-Parser bridge support MCP revision 2026-07-28?
No. SEO Tools: A-Parser bridge was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were SEO Tools: A-Parser bridge's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Bridge to a self-hosted A-Parser: SERP, suggests and 150+ parsers via its API (read-only).
Which MCP spec revisions does SEO Tools: A-Parser bridge support?
SEO Tools: A-Parser bridge has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is SEO Tools: A-Parser bridge?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for SEO Tools: A-Parser bridge
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Stars
- 3
- Forks
- 0
- Last pushed
- (38 days ago)
- Created
- Open issues
- 2
- Primary language
- TypeScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- Present
Declared topics: claude, mcp, model-context-protocol, search-console, seo, yandex — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
1.8.0- Last published
- First published
- Releases
- 6
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 2
- Unpacked size
- 70 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.antohins/seo-tools-mcp-aparser at version 1.7.0 - lists package npm:seo-tools-mcp-aparser and repository https://github.com/antohins/seo-tools-mcp - accessed
- npm registry metadata for seo-tools-mcp-aparser at published version 1.7.0, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed