# io.github.juanisidoro/securecode (npm · @securecode/mcp-server)

Secrets vault for Claude Code with audit logs, access rules, and AES-256 encryption.

- Trust score: 69/100 (medium)
- Change this week: +23
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@securecode/mcp-server`: 69/100 (this document), [markdown](https://verifymcp.io/servers/juanisidoro-securecode/securecode-mcp-server.md), [page](https://verifymcp.io/servers/juanisidoro-securecode/securecode-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@securecode/mcp-server`
- Version: `0.15.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 94 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1370 tokens (~80/item across 17 items; 17 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add juanisidoro-securecode -- npx -y @securecode/mcp-server
```

### Codex

```bash
codex mcp add juanisidoro-securecode -- npx -y @securecode/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "juanisidoro-securecode": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@securecode/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add juanisidoro-securecode --command npx --arg -y --arg @securecode/mcp-server
```

### Hermes

```yaml
mcp_servers:
  juanisidoro-securecode:
    command: "npx"
    args: ["-y", "@securecode/mcp-server"]
```

### Other

```json
{
  "mcpServers": {
    "juanisidoro-securecode": {
      "command": "npx",
      "args": [
        "-y",
        "@securecode/mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 69, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-08-02 (score 66, +45)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional] Licence: MIT

### 2026-07-31 (score 21, −25)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 46, +19)

- [functional regression] Dependency health: partial → unverified
- [functional improvement] Tool coverage: unverified → 100

### 2026-07-28 (score 27, −19)

- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Dependency health: unverified → partial
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (17)

### `get-secret` (~170 tokens)

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.

Input parameters:

- `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" }

### `list-secrets` (~56 tokens)

List all available secrets with their tags and expiration status. Returns names and metadata, never values.

Input parameters:

- `tags` (object): Filter by tags, e.g. { "env": "production", "project": "acme" }

### `create-secret` (~148 tokens)

Create a new secret. Secrets with the same name can coexist if they have different env tags.

Input parameters:

- `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, required): 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, required): The secret value to encrypt and store

### `renew-secret` (~79 tokens)

Renew an expired secret or change its TTL. Use this to reactivate expired secrets or extend expiration.

Input parameters:

- `name` (string, required): 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)

### `delete-secret` (~49 tokens)

Delete a secret (soft delete, can be recovered)

Input parameters:

- `name` (string, required): The name of the secret to delete
- `tags` (object): Filter tags to disambiguate same-name secrets

### `update-secret` (~120 tokens)

Update an existing secret's value, description, tags, or domain. Only provided fields are changed.

Input parameters:

- `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, required): 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)

### `import-env` (~52 tokens)

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.

### `export-env` (~66 tokens)

Export all secrets as .env or CSV format. Returns the full content with decrypted values.

Input parameters:

- `format` (string): Export format: "env" (default) or "csv"
- `tags` (object): Filter by tags, e.g. { "env": "production" }

### `get-status` (~43 tokens)

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.

### `wake-session` (~89 tokens)

Wake (unlock) the session to start accessing secrets. Optionally restrict access to specific tag scope and set auto-sleep timer.

Input parameters:

- `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.

### `sleep-session` (~32 tokens)

Lock the session immediately. All secret access will be blocked until you wake it again. Use this when you finish working.

### `session-status` (~29 tokens)

Check the current session status: active or sleeping, scope restrictions, and time remaining before auto-sleep.

### `byebye` (~40 tokens)

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.

### `get-active-rules` (~42 tokens)

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.

### `onboard` (~265 tokens)

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.

Input parameters:

- `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.

### `security-check` (~38 tokens)

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.

### `help` (~52 tokens)

Get SecureCode documentation: available tools, usage patterns, SDK setup, and common workflows. Use this to understand how to help the user with SecureCode.

Input parameters:

- `topic` (string): Documentation topic. Default: "all"

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/juanisidoro-securecode/securecode-mcp-server#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 66
- 2026-08-01: 21
- 2026-07-31: 21
- 2026-07-30: 46
- 2026-07-28: 27
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/@securecode/mcp-server
- Socket report: https://socket.dev/npm/package/@securecode/mcp-server
- Repository: https://github.com/juanisidoro/securecode-mcp
- Changelog RSS feed: https://verifymcp.io/servers/juanisidoro-securecode/securecode-mcp-server/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/juanisidoro-securecode/securecode-mcp-server/changelog.json
- HTML version of this page: https://verifymcp.io/servers/juanisidoro-securecode/securecode-mcp-server