io.github.n0zer0d4y/mercury-spec-ops
NPM · @N0ZER0D4Y/MERCURY-SPEC-OPS · SCANNED AUG 6
Modular MCP server for dynamic prompt generation and software development analysis tools
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 94 of 98 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 94 of 98 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency44
- 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 264 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 264 tokens (~44/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @n0zer0d4y/mercury-spec-ops
claude mcp add n0zer0d4y-mercury-spec-ops -- npx -y @n0zer0d4y/mercury-spec-ops
codex mcp add n0zer0d4y-mercury-spec-ops -- npx -y @n0zer0d4y/mercury-spec-ops
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"n0zer0d4y-mercury-spec-ops": {
"type": "local",
"command": [
"npx",
"-y",
"@n0zer0d4y/mercury-spec-ops"
],
"enabled": true
}
}
} openclaw mcp add n0zer0d4y-mercury-spec-ops --command npx --arg -y --arg @n0zer0d4y/mercury-spec-ops
mcp_servers:
n0zer0d4y-mercury-spec-ops:
command: "npx"
args: ["-y", "@n0zer0d4y/mercury-spec-ops"] {
"mcpServers": {
"n0zer0d4y-mercury-spec-ops": {
"command": "npx",
"args": [
"-y",
"@n0zer0d4y/mercury-spec-ops"
]
}
}
} 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.
- 6 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Aug 26 +1
- CVE-2026-69207 no longer affects this package ▲ security
- Known CVEs: fail → partial ▲ security
- 4 Aug 26 0
- CVE-2026-69207 affects this package: medium ▼ security
- Known CVEs: partial → fail ▼ security
- 2 Aug 26 +40
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.20 ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
- 1 Aug 26 +5
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- 31 Jul 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
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 6 Aug 2026 · Analysed npm/@n0zer0d4y/[email protected]
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Deprecated | 94 |
| Stale | 29 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
generate_bug_analysis_prompt ~61
Generate an assembled bug analysis prompt with specified technology stacks and severity level
| Name | Type | Req | Description |
|---|---|---|---|
| bug_context | string | — | Optional bug description or context |
| severity | string | yes | Bug severity level |
| technology_stack | array | yes | Technology stacks involved in the bug |
No output schema declared.
No examples provided.
generate_codebase_analysis_prompt ~52
Generate an assembled codebase analysis prompt with specified technology stacks and analysis focus areas
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_focus | array | yes | Areas to focus analysis on |
| technology_stack | array | yes | Technology stacks to analyze |
No output schema declared.
No examples provided.
generate_prd_prompt ~70
Generate an assembled Product Requirements Document prompt with specified technology stacks and analysis focus areas
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_focus | array | — | Analysis focus areas for the PRD |
| project_context | string | — | Optional project context or background information |
| technology_stack | array | yes | Technology stacks to include in prompt assembly |
No output schema declared.
No examples provided.
get_bug_analysis_template ~26
Fetch a comprehensive bug analysis markdown template with all standard sections (8 sections total)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_codebase_analysis_template ~28
Fetch a comprehensive codebase analysis markdown template with all standard sections (12 sections total)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_prd_template ~27
Fetch a comprehensive Product Requirements Document markdown template with all standard sections (14 sections total)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.