io.github.armin5872/optiqra-mcp
NPM · OPTIQRA-MCP · SCANNED SEP 20
MCP server exposing OptiQra's website audit tools: SEO, GEO, AEO, and AI-generated fixes.
Available components
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 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to armin5872/optiqra-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 34 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 517 tokens (~129/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the io.github.armin5872/optiqra-mcp server?
io.github.armin5872/optiqra-mcp runs locally as an npm package, launched with npx -y optiqra-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 · optiqra-mcp
claude mcp add armin5872-optiqra-mcp -- npx -y optiqra-mcp
{
"mcpServers": {
"armin5872-optiqra-mcp": {
"command": "npx",
"args": [
"-y",
"optiqra-mcp"
]
}
}
} {
"servers": {
"armin5872-optiqra-mcp": {
"command": "npx",
"args": [
"-y",
"optiqra-mcp"
]
}
}
} codex mcp add armin5872-optiqra-mcp -- npx -y optiqra-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"armin5872-optiqra-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"optiqra-mcp"
],
"enabled": true
}
}
} openclaw mcp add armin5872-optiqra-mcp --command npx --arg -y --arg optiqra-mcp
mcp_servers:
armin5872-optiqra-mcp:
command: "npx"
args: ["-y", "optiqra-mcp"] {
"McpServers": {
"armin5872-optiqra-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"optiqra-mcp"
]
}
}
} assistant mcp add armin5872-optiqra-mcp -t stdio -c npx -a -y optiqra-mcp
{
"mcpServers": {
"armin5872-optiqra-mcp": {
"command": "npx",
"args": [
"-y",
"optiqra-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/optiqra-mcp@1.0.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | armin5872/optiqra-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/armin5872/optiqra-mcp/.github/workflows/publish.yml@refs/tags/v1.0.4 |
| Rekor log index | 2491822541 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:cea0c0eadb4d3924deb28729284f71ab3c12c7cd3ae8e8a74709edf5f148791cb6fd9ec299c0d66bffc0af469d7a7b1b4aca9690e1d2daefda90a784f |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| 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 →
optiqra_ai_fix Generate an AI fix for an OptiQra issue ~153
Given a single issue from an OptiQra report (as produced by optiqra_analyze), asks an AI provider to generate a suggested fix. Requires an API key for the chosen provider — OptiQra forwards it directly to that provider and never stores it server-side.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | API key for the chosen provider. Optional if OPTIQRA_PROVIDER_API_KEY is set in this server's environment. |
| issue | object | yes | The issue object (from an optiqra_analyze report) to generate a fix for. |
| model | string | – | Optional specific model name to use for that provider. |
| provider | string | yes | AI provider to use for this request. |
No output schema declared.
No examples provided.
optiqra_ai_insights Generate AI insights for an OptiQra report ~154
Given a full OptiQra report (as produced by optiqra_analyze), asks an AI provider to generate a strategic, site-wide summary reasoning across all audit categories and pages. Requires an API key for the chosen provider — OptiQra forwards it directly to that provider and never stores it server-side.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | API key for the chosen provider. Optional if OPTIQRA_PROVIDER_API_KEY is set in this server's environment. |
| model | string | – | Optional specific model name to use for that provider. |
| provider | string | yes | AI provider to use for this request. |
| report | object | yes | The full report object returned by optiqra_analyze. |
No output schema declared.
No examples provided.
optiqra_ai_test Test an OptiQra AI provider key ~101
Verifies that a given AI provider + API key + model combination is reachable and working, before using optiqra_ai_fix or optiqra_ai_insights.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | API key for the chosen provider. Optional if OPTIQRA_PROVIDER_API_KEY is set in this server's environment. |
| model | string | – | Optional specific model name to test. |
| provider | string | yes | AI provider to use for this request. |
No output schema declared.
No examples provided.
optiqra_analyze Analyze a website with OptiQra ~109
Crawls a website and runs OptiQra's full audit: SEO, GEO (generative engine optimization), AEO (answer engine optimization), performance, accessibility, security headers, structured data, links, images, and duplicate-content detection. Returns a report with per-category scores and issue details. This can take a while for larger sites since it crawls the whole site.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL of the website to analyze, e.g. https://example.com |
No output schema declared.
No examples provided.
What is the io.github.armin5872/optiqra-mcp server?
io.github.armin5872/optiqra-mcp is listed in the public MCP registry as io.github.armin5872/optiqra-mcp. MCP server exposing OptiQra's website audit tools: SEO, GEO, AEO, and AI-generated fixes. This page covers its npm package (optiqra-mcp).
Is the io.github.armin5872/optiqra-mcp server safe to use?
io.github.armin5872/optiqra-mcp scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.armin5872/optiqra-mcp server expose?
io.github.armin5872/optiqra-mcp exposes 4 tools: optiqra_analyze, optiqra_ai_fix, optiqra_ai_insights, optiqra_ai_test. Their descriptions and schemas cost roughly 517 tokens of context every time the server is loaded.
Is the io.github.armin5872/optiqra-mcp server still maintained?
io.github.armin5872/optiqra-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.armin5872/optiqra-mcp server under?
io.github.armin5872/optiqra-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.