io.github.juanisidoro/securecode
NPM · @SECURECODE/MCP-SERVER
Secrets vault for Claude Code with audit logs, access rules, and AES-256 encryption.
Available components
Last scanned (19 hours ago)
Scores higher than 58% of npm servers
Category Security
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 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 187 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1370 tokens (~80/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete-secret" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 17 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
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.
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 14 Oct 26 −2
- Stability: pass → 0.80 functional
- 13 Oct 26 0
- Stability: 0.97 → pass security
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 4 Nov 2026 · Analysed npm/@securecode/mcp-server@0.15.2
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
byebye ~40
End your work session. Locks the session, cleans up all injected secrets from disk, and says goodbye. Use this when you finish working for the day.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create-secret ~148
Create a new secret. Secrets with the same name can coexist if they have different env tags.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Human-readable description of what this secret is for |
| domain | string | – | Associated domain for browser extension, e.g. "api.stripe.com" |
| name | string | yes | Name for the secret (e.g. STRIPE_SECRET_KEY) |
| tags | object | – | Tags as key:value pairs, e.g. { "env": "production", "project": "acme" } |
| ttlHours | number | – | Time-to-live in hours. Omit for permanent (no expiry) |
| value | string | yes | The secret value to encrypt and store |
No output schema declared.
No examples provided.
delete-secret ~49
Delete a secret (soft delete, can be recovered)
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name of the secret to delete |
| tags | object | – | Filter tags to disambiguate same-name secrets |
No output schema declared.
No examples provided.
export-env ~66
Export all secrets as .env or CSV format. Returns the full content with decrypted values.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Export format: "env" (default) or "csv" |
| tags | object | – | Filter by tags, e.g. { "env": "production" } |
No output schema declared.
No examples provided.
get-active-rules ~42
List active MCP access rules. Read-only — rules can only be created or modified from the dashboard. Use this to understand why access to a secret was blocked.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-secret ~170
Get a secret by name. By default, injects the value into a local file so it never appears in the AI conversation. Use reveal:true to see the raw value (audited as conscious action). Use cleanup:true to remove all injected secrets from disk.
| Name | Type | Req | Description |
|---|---|---|---|
| cleanup | boolean | – | If true, removes all injected secret files from disk |
| name | string | – | The exact name of the secret (e.g. STRIPE_SECRET_KEY) |
| reveal | boolean | – | If true, returns the raw value in the conversation (audited as reveal). Default: false (inject mode — value written to local file, never shown) |
| tags | object | – | Filter tags to disambiguate same-name secrets, e.g. { "env": "production", "project": "acme" } |
No output schema declared.
No examples provided.
get-status ~43
Get your SecureCodeHQ account status: plan, usage limits, secrets count, and MCP server version. Useful to check remaining capacity and verify the server is up to date.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
help ~52
Get SecureCode documentation: available tools, usage patterns, SDK setup, and common workflows. Use this to understand how to help the user with SecureCode.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Documentation topic. Default: "all" |
No output schema declared.
No examples provided.
import-env ~52
Import secrets from .env files into SecureCode. For security, .env import must be done through the web interface — the AI agent never sees secret values during import. This tool provides the link to the import page.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list-secrets ~56
List all available secrets with their tags and expiration status. Returns names and metadata, never values.
| Name | Type | Req | Description |
|---|---|---|---|
| tags | object | – | Filter by tags, e.g. { "env": "production", "project": "acme" } |
No output schema declared.
No examples provided.
onboard ~265
Start or continue the SecureCode onboarding. Guides the user through signup, .env import, API key creation, MCP configuration, and optional SDK setup — all from Claude Code. Call this tool multiple times to progress through the steps.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Action to perform. "start" (default) progresses through signup/import steps. "configure-auto" lets the agent write the API key to the MCP config file automatically. "configure-manual" shows the API k… |
| configPath | string | – | Path to the MCP config file (.mcp.json or claude.json). Only needed for configure-auto if auto-detection fails. |
| selectedEnv | string | – | Environment tag selected by user (from select-secrets action). Used to configure .securecoderc. |
| selectedProject | string | – | Project tag selected by user (from select-secrets action). Used to configure .securecoderc. |
No output schema declared.
No examples provided.
renew-secret ~79
Renew an expired secret or change its TTL. Use this to reactivate expired secrets or extend expiration.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name of the secret to renew |
| tags | object | – | Filter tags to disambiguate same-name secrets |
| ttlHours | number | – | New TTL in hours. Omit to make permanent (no expiry) |
No output schema declared.
No examples provided.
security-check ~38
Analyze the project for security issues after SecureCode setup. Returns a list of actions the agent MUST execute to protect secrets. Call this after SDK installation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
session-status ~29
Check the current session status: active or sleeping, scope restrictions, and time remaining before auto-sleep.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sleep-session ~32
Lock the session immediately. All secret access will be blocked until you wake it again. Use this when you finish working.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
update-secret ~120
Update an existing secret's value, description, tags, or domain. Only provided fields are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | New description |
| domain | string | – | New domain |
| filterTags | object | – | Filter tags to disambiguate same-name secrets (different from the "tags" field which sets new tags) |
| name | string | yes | The name of the secret to update |
| tags | object | – | New tags (replaces ALL existing tags) |
| value | string | – | New secret value (omit to keep current value) |
No output schema declared.
No examples provided.
wake-session ~89
Wake (unlock) the session to start accessing secrets. Optionally restrict access to specific tag scope and set auto-sleep timer.
| Name | Type | Req | Description |
|---|---|---|---|
| autoSleepMinutes | integer | – | Minutes of inactivity before auto-sleep. Default: 120 (2 hours). |
| scope | array | – | Tag filters to restrict which secrets are accessible. E.g. [{project:"acme"}]. Omit for all secrets. |
No output schema declared.
No examples provided.
How do I install the io.github.juanisidoro/securecode MCP server?
io.github.juanisidoro/securecode runs locally as an npm package, launched with npx -y @securecode/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @securecode/mcp-server
claude mcp add juanisidoro-securecode -- npx -y @securecode/mcp-server
What is the io.github.juanisidoro/securecode MCP server?
io.github.juanisidoro/securecode is an MCP server listed in the public MCP registry as io.github.juanisidoro/securecode. Secrets vault for Claude Code with audit logs, access rules, and AES-256 encryption. This page covers its npm package (@securecode/mcp-server).
Is the io.github.juanisidoro/securecode MCP server safe to use?
io.github.juanisidoro/securecode scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 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 io.github.juanisidoro/securecode MCP server expose?
io.github.juanisidoro/securecode exposes 17 tools: get-secret, list-secrets, create-secret, renew-secret, delete-secret, and 12 more. Their descriptions and schemas cost roughly 1,370 tokens of context every time the server is loaded.
Is the io.github.juanisidoro/securecode MCP server still maintained?
io.github.juanisidoro/securecode is still listed as active in the MCP registry. We last reached this channel on 4 November 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.juanisidoro/securecode MCP server under?
io.github.juanisidoro/securecode declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.