Cygnix SEO
NPM · CYGNIX-SEO-MCP
No-API-key SEO tools: keyword clustering, search intent, cannibalization, meta checks, briefs.
Available components
Last scanned (6 hours ago)
Scores higher than 38% of npm servers
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 295 tokens (~59/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage77
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 30% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Oct 26 +28
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Destructive annotations: pass functional
- First check of Tool coverage: 30 functional
- First check of Schema quality: pass functional
- 14 Oct 26 38
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Analysed npm/cygnix-seo-mcp@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_title_meta ~45
Check title tags and meta descriptions for length/pixel truncation, keyword placement and CTR hooks. Returns a 0-100 score with fixes.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
classify_search_intent ~41
Classify keywords as informational, commercial, transactional or navigational using modifier rules.
| Name | Type | Req | Description |
|---|---|---|---|
| keywords | string | yes | Keywords, one per line or comma separated |
No output schema declared.
No examples provided.
cluster_keywords ~62
Group a pasted keyword list (newline/comma separated) into topical clusters with a suggested pillar keyword per cluster. Deterministic; no search volumes.
| Name | Type | Req | Description |
|---|---|---|---|
| keywords | string | yes | Keywords, one per line or comma separated |
| min_shared_terms | integer | – | – |
No output schema declared.
No examples provided.
content_brief_outline ~72
Generate a content brief (intent, title options, meta draft, H2 outline, questions, on-page checklist) for a target keyword plus optional related keywords.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | – |
| keyword | string | yes | – |
| related_keywords | string | – | – |
| word_count | integer | – | – |
No output schema declared.
No examples provided.
find_keyword_cannibalization ~75
Find queries where 2+ of your pages compete, from a Google Search Console export (CSV/TSV text with Query and Page columns; clicks, impressions, position optional).
| Name | Type | Req | Description |
|---|---|---|---|
| gsc_csv | string | yes | Pasted GSC CSV text including header row |
| min_impressions | integer | – | – |
No output schema declared.
No examples provided.
How do I install the Cygnix SEO MCP server?
Cygnix SEO runs locally as an npm package, launched with npx -y cygnix-seo-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · cygnix-seo-mcp
claude mcp add cygnixlabs-cmd-cygnix-seo-mcp -- npx -y cygnix-seo-mcp
What is the Cygnix SEO MCP server?
Cygnix SEO is an MCP server listed in the public MCP registry as io.github.cygnixlabs-cmd/cygnix-seo-mcp. No-API-key SEO tools: keyword clustering, search intent, cannibalization, meta checks, briefs. This page covers its npm package (cygnix-seo-mcp).
Is the Cygnix SEO MCP server safe to use?
Cygnix SEO scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Cygnix SEO MCP server expose?
Cygnix SEO exposes 5 tools: cluster_keywords, classify_search_intent, find_keyword_cannibalization, check_title_meta, content_brief_outline. Their descriptions and schemas cost roughly 295 tokens of context every time the server is loaded.
Is the Cygnix SEO MCP server still maintained?
Cygnix SEO is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Cygnix SEO MCP server under?
Cygnix SEO declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.