ai.wild-card/deepcontext
NPM · @WILDCARD-AI/DEEPCONTEXT · SCANNED AUG 3
Advanced codebase indexing and semantic search MCP server
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 Security70
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.6.1, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (21 of 22), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency18
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 314 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability73
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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 · @wildcard-ai/deepcontext
claude mcp add ai-wild-card-deepcontext -- npx -y @wildcard-ai/deepcontext
codex mcp add ai-wild-card-deepcontext -- npx -y @wildcard-ai/deepcontext
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-wild-card-deepcontext": {
"type": "local",
"command": [
"npx",
"-y",
"@wildcard-ai/deepcontext"
],
"enabled": true
}
}
} openclaw mcp add ai-wild-card-deepcontext --command npx --arg -y --arg @wildcard-ai/deepcontext
mcp_servers:
ai-wild-card-deepcontext:
command: "npx"
args: ["-y", "@wildcard-ai/deepcontext"] {
"mcpServers": {
"ai-wild-card-deepcontext": {
"command": "npx",
"args": [
"-y",
"@wildcard-ai/deepcontext"
]
}
}
} 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.
- 3 Aug 26 +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.
- 2 Aug 26 +26
- CVE-2025-66414 affects this package: high ▼ security
- Known CVEs: unverified → fail ▼ security
- Provenance: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ 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: fail → unverified ▼ functional
- License: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Stability: unverified → 0.23 ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Dependency health: unverified → partial ▲ functional
- Licence: Apache-2.0 functional
- 1 Aug 26 +24
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Licence: Apache-2.0 functional
- 31 Jul 26 −39
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 39
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 3 Aug 2026 · Analysed npm/@wildcard-ai/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w48q-cv73-mx4w | CVE-2025-66414 | high | yes |
Dependencies 21 packages
21 packages in the resolved dependency tree · 21 deprecated · 6 stale.
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.
clear_index ~272
<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>
| Name | Type | Req | Description |
|---|---|---|---|
| codebase_path | string | — | — |
No output schema declared.
No examples provided.
get_indexing_status ~346
<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>
| Name | Type | Req | Description |
|---|---|---|---|
| codebase_path | string | — | — |
No output schema declared.
No examples provided.
index_codebase ~289
<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>
| Name | Type | Req | Description |
|---|---|---|---|
| codebase_path | string | yes | — |
| force_reindex | boolean | — | — |
No output schema declared.
No examples provided.
search_codebase ~927
<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>…
| Name | Type | Req | Description |
|---|---|---|---|
| codebase_path | string | yes | — |
| max_results | number | — | — |
| query | string | yes | — |
No output schema declared.
No examples provided.