# ai.wild-card/deepcontext (npm · @wildcard-ai/deepcontext)

Advanced codebase indexing and semantic search MCP server

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

## Components

- npm · `@wildcard-ai/deepcontext`: 51/100 (this document), [markdown](https://verifymcp.io/servers/ai-wild-card-deepcontext/wildcard-ai-deepcontext.md), [page](https://verifymcp.io/servers/ai-wild-card-deepcontext/wildcard-ai-deepcontext)

## Channel facts

- Registry: `npm`
- Package: `@wildcard-ai/deepcontext`
- Version: `0.1.15`
- 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**: 70/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.6.1, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (21 of 22), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 18/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 314 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1847 tokens (~369/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add ai-wild-card-deepcontext -- npx -y @wildcard-ai/deepcontext
```

### Codex

```bash
codex mcp add ai-wild-card-deepcontext -- npx -y @wildcard-ai/deepcontext
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-wild-card-deepcontext": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@wildcard-ai/deepcontext"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-wild-card-deepcontext --command npx --arg -y --arg @wildcard-ai/deepcontext
```

### Hermes

```yaml
mcp_servers:
  ai-wild-card-deepcontext:
    command: "npx"
    args: ["-y", "@wildcard-ai/deepcontext"]
```

### Other

```json
{
  "mcpServers": {
    "ai-wild-card-deepcontext": {
      "command": "npx",
      "args": [
        "-y",
        "@wildcard-ai/deepcontext"
      ]
    }
  }
}
```

## 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 51, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 50, +26)

- [security regression] CVE-2025-66414 affects this package: high
- [security regression] Known CVEs: unverified → fail
- [security regression] Provenance: fail → unverified
- [security regression] Install scripts: pass → unverified
- [security improvement] 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.
- [functional regression] Capabilities: fail → unverified
- [functional regression] License: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Maintenance: pass → unverified
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Dependency health: unverified → partial
- [functional] Licence: Apache-2.0

### 2026-08-01 (score 24, +24)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] License: unverified → pass
- [functional] Licence: Apache-2.0

### 2026-07-31 (score 0, −39)

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

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

First indexed and scored.

## MCP tools (4)

### `index_codebase` (~289 tokens)

\<tool>
  \<purpose>Prepares a codebase for intelligent search by creating a searchable index</purpose>

  \<when_to_use>
    <scenario>Call this first before searching any new codebase</scenario>
    <scenario>Required prerequisite for search_codebase</scenario>
  \</when_to_use>

  \<parameters>
    <parameter name="codebase_path" required="true">
      <type>string</type>
      <description>ABSOLUTE path to the directory containing source code files</description>
      <examples>
        <valid>/Users/name/project</valid>
        <valid>/home/user/code/repo</valid>
        <invalid>.</invalid>
        <invalid>../project</invalid>
        <invalid>relative/path</invalid>
      </examples>
      <validation>Must be absolute path starting with / (Unix) or C:\ (Windows)</validation>
    </parameter>

    <parameter name="force_reindex" required="false">
      <type>boolean</type>
      <description>Force complete reindexing even if already indexed</description>
      <default>false</default>
      <when_to_use>Code has changed significantly or search results seem outdated</when_to_use>
    </parameter>
  \</parameters>
\</tool>

Input parameters:

- `codebase_path` (string, required)
- `force_reindex` (boolean)

### `search_codebase` (~927 tokens)

\<tool>
  \<purpose>Finds relevant code in an indexed codebase using natural language or keyword queries</purpose>

  \<when_to_use>
    <scenario>Find specific functions, classes, or code patterns</scenario>
    <scenario>Get context before making changes to understand dependencies</scenario>
    <scenario>Explore how existing systems work</scenario>
    <scenario>Locate examples of API usage or patterns</scenario>
  \</when_to_use>

  \<parameters>
    <parameter name="query" required="true">
      <type>string</type>
      <description>Natural language or keyword search query describing what code to find</description>
    </parameter>

    <parameter name="codebase_path" required="true">
      <type>string</type>
      <description>ABSOLUTE path to the codebase directory to search</description>
      <examples>
        <valid>/Users/name/project</valid>
        <valid>/home/user/code/repo</valid>
        <invalid>.</invalid>
        <invalid>../project</invalid>
        <invalid>relative/path</invalid>
      </examples>
      <validation>Must be absolute path starting with / (Unix) or C:\ (Windows)</validation>
    </parameter>

    <parameter name="max_results" required="false">
      <type>number</type>
      <description>Maximum number of code chunks to return</description>
      <default>5</default>
      <best_practice>Keep at default 5 for focused results. Use multiple targeted searches rather than increasing this limit</best_practice>
    </parameter>
  \</parameters>

  \<strategy>
    <guideline>Use specific technical terms: "authentication middleware", "database connection", "error handler"</guideline>
    <guideline>Focus on implementation: "user login function" rather than "user management system"</guideline>
    <guideline>Include file types when relevant: "SQL migration", "React component", "API endpoint"</guideline>
  \</strategy>

  \<workflow>
    <step>Search discovers relevant files and entry points, use imports and exports to find related files</step>…

Input parameters:

- `codebase_path` (string, required)
- `max_results` (number)
- `query` (string, required)

### `get_indexing_status` (~346 tokens)

\<tool>
  \<purpose>Check if codebases are indexed and get their status information</purpose>

  \<enhanced_features>
    <feature>Shows completion statistics for finished indexing (success rates, processing time, performance metrics)</feature>
    <feature>Displays batch processing details (successful/skipped batches)</feature>
    <feature>References log files for detailed debugging</feature>
  \</enhanced_features>

  \<when_to_use>
    <scenario>Before indexing to check if already done</scenario>
    <scenario>After indexing to see completion statistics and success rates</scenario>
    <scenario>Debug why search returned no results</scenario>
    <scenario>Confirm indexing completed successfully</scenario>
    <scenario>Get overview of all indexed codebases</scenario>
  \</when_to_use>

  \<parameters>
    <parameter name="codebase_path" required="false">
      <type>string</type>
      <description>ABSOLUTE path to specific codebase to check</description>
      <examples>
        <valid>/Users/name/project</valid>
        <valid>/home/user/code/repo</valid>
        <invalid>.</invalid>
        <invalid>../project</invalid>
        <invalid>relative/path</invalid>
      </examples>
      <validation>Must be absolute path starting with / (Unix) or C:\ (Windows)</validation>
      <optional_behavior>Omit to get status of all indexed codebases</optional_behavior>
    </parameter>
  \</parameters>

  \<returns>Enhanced indexing status with completion statistics when available</returns>
\</tool>

Input parameters:

- `codebase_path` (string)

### `clear_index` (~272 tokens)

\<tool>
  \<purpose>Permanently removes all indexed data for a codebase</purpose>

  \<when_to_use>
    <scenario>Clear stale data before reindexing after major code changes</scenario>
    <scenario>Remove old indexed codebases no longer needed</scenario>
    <scenario>Fix corrupted index causing search issues</scenario>
  \</when_to_use>

  \<parameters>
    <parameter name="codebase_path" required="false">
      <type>string</type>
      <description>ABSOLUTE path to the codebase to clear</description>
      <examples>
        <valid>/Users/name/project</valid>
        <valid>/home/user/code/repo</valid>
        <invalid>.</invalid>
        <invalid>../project</invalid>
        <invalid>relative/path</invalid>
      </examples>
      <validation>Must be absolute path starting with / (Unix) or C:\ (Windows)</validation>
      <optional_behavior>Omit to clear ALL indexed codebases (use with caution)</optional_behavior>
    </parameter>
  \</parameters>

  \<warnings>
    <warning>Destructive operation. All search capabilities lost until reindexing</warning>
  \</warnings>
\</tool>

Input parameters:

- `codebase_path` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/ai-wild-card-deepcontext/wildcard-ai-deepcontext#diagnostics

## Score history

- 2026-08-03: 51
- 2026-08-02: 50
- 2026-08-01: 24
- 2026-07-31: 0
- 2026-07-30: 39
- 2026-07-28: 39
- 2026-07-27: 39

## Links

- npm package: https://www.npmjs.com/package/@wildcard-ai/deepcontext
- Socket report: https://socket.dev/npm/package/@wildcard-ai/deepcontext
- Changelog RSS feed: https://verifymcp.io/servers/ai-wild-card-deepcontext/wildcard-ai-deepcontext/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-wild-card-deepcontext/wildcard-ai-deepcontext/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-wild-card-deepcontext/wildcard-ai-deepcontext