ai.wild-card/deepcontext
NPM · @WILDCARD-AI/DEEPCONTEXT · SCANNED SEP 26
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 → 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 @modelcontextprotocol/sdk 0.6.1, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 7 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency17
- 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 368 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 (good).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 Management87
- Stability observed for 26 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the ai.wild-card/deepcontext MCP server?
ai.wild-card/deepcontext runs locally as an npm package, launched with npx -y @wildcard-ai/deepcontext. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @wildcard-ai/deepcontext
claude mcp add ai-wild-card-deepcontext -- npx -y @wildcard-ai/deepcontext
{
"mcpServers": {
"ai-wild-card-deepcontext": {
"command": "npx",
"args": [
"-y",
"@wildcard-ai/deepcontext"
]
}
}
} {
"servers": {
"ai-wild-card-deepcontext": {
"command": "npx",
"args": [
"-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": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@wildcard-ai/deepcontext"
]
}
}
} assistant mcp add ai-wild-card-deepcontext -t stdio -c npx -a -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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −3
- Stability: pass → 0.77 functional
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 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 26 Sept 2026 · Analysed npm/@wildcard-ai/deepcontext@0.1.15
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-w48q-cv73-mx4w | CVE-2025-66414 | high | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 22 packages
| Packages resolved | 22 |
|---|---|
| Stale | 7 |
| 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 →
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.
What is the ai.wild-card/deepcontext MCP server?
ai.wild-card/deepcontext is an MCP server listed in the public MCP registry as ai.wild-card/deepcontext. Advanced codebase indexing and semantic search MCP server. This page covers its npm package (@wildcard-ai/deepcontext).
Is the ai.wild-card/deepcontext MCP server safe to use?
ai.wild-card/deepcontext scores 65 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 26 September 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 ai.wild-card/deepcontext MCP server expose?
ai.wild-card/deepcontext exposes 4 tools: index_codebase, search_codebase, get_indexing_status, clear_index. Their descriptions and schemas cost roughly 1,834 tokens of context every time the server is loaded.
Is the ai.wild-card/deepcontext MCP server still maintained?
ai.wild-card/deepcontext is still listed as active in the MCP registry. We last reached this channel on 26 September 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 ai.wild-card/deepcontext MCP server under?
ai.wild-card/deepcontext declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.