com.shiftinbits/constellation
NPM · @CONSTELLATIONDEV/MCP · SCANNED SEP 20
Code Intelligence Platform for AI Coding Agents
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to ShiftinBits/constellation-mcp). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-only).Pass
- Actively maintained (last published 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability87
- 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
- Tool/resource definitions use about 1716 tokens (~90/item across 19 items; 1 tools + 18 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
How do I install the com.shiftinbits/constellation MCP server?
com.shiftinbits/constellation runs locally as an npm package, launched with npx -y @constellationdev/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @constellationdev/mcp
claude mcp add com-shiftinbits-constellation -- npx -y @constellationdev/mcp
{
"mcpServers": {
"com-shiftinbits-constellation": {
"command": "npx",
"args": [
"-y",
"@constellationdev/mcp"
]
}
}
} {
"servers": {
"com-shiftinbits-constellation": {
"command": "npx",
"args": [
"-y",
"@constellationdev/mcp"
]
}
}
} codex mcp add com-shiftinbits-constellation -- npx -y @constellationdev/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-shiftinbits-constellation": {
"type": "local",
"command": [
"npx",
"-y",
"@constellationdev/mcp"
],
"enabled": true
}
}
} openclaw mcp add com-shiftinbits-constellation --command npx --arg -y --arg @constellationdev/mcp
mcp_servers:
com-shiftinbits-constellation:
command: "npx"
args: ["-y", "@constellationdev/mcp"] {
"McpServers": {
"com-shiftinbits-constellation": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@constellationdev/mcp"
]
}
}
} assistant mcp add com-shiftinbits-constellation -t stdio -c npx -a -y @constellationdev/mcp
{
"mcpServers": {
"com-shiftinbits-constellation": {
"command": "npx",
"args": [
"-y",
"@constellationdev/mcp"
]
}
}
} 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.
- 20 Sept 26 0
- Stability: 0.97 → pass security
- 19 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.
- 17 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.
- 15 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.
- 14 Sept 26 −3
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Stability: pass → 0.80 functional
- Package version: 1.2.8 → 1.2.10 functional
- 13 Sept 26 0
- Stability: 0.97 → pass security
- 12 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.
- 10 Sept 26 −1
- Stability: pass → 0.90 functional
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 20 Sept 2026 · Analysed npm/@constellationdev/mcp@1.2.10
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | ShiftinBits/constellation-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/ShiftinBits/constellation-mcp/.github/workflows/publish.yml@refs/tags/v1.2.10 |
| Rekor log index | 2834959843 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:cc627dbdfc1c9e76b9d248e915124c59727c9b95f150a995ba21900b6aa2d923b689ce71987a1801f52c43c7419fa9a3de0f32452d410d29759b2d0e8 |
Background: How many MCP packages publish verified provenance →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 31 |
| 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 →
code_intel Code Intelligence ~837
DECISION RULE: Structure questions → this tool. Text search → Grep. Before using Grep, ask: Is this a STRUCTURE question (definitions, callers, impact) or a TEXT question (strings, config)? QUICK START: `return await api.searchSymbols({query: "AuthService"})` — simple queries are one-liners. Run `api.listMethods()` for full API reference with signatures and descriptions. Run `api.help("methodName")` for inline TypeScript type definitions — no resource reads needed. Compose: `const [impact, deps] = await Promise.all([api.impactAnalysis({symbolId}), api.getDependents({filePath})]);` WHY THIS TOOL: Graph-backed intelligence finds indirect relationships, transitive dependencies, and breaking change risks that text search cannot detect. "What uses X?" disambiguation: getDependents (file imports) vs getCallGraph (call chain) vs traceSymbolUsage (all usages). USE IMMEDIATELY WHEN: • BEFORE using Edit on a function/class → run impactAnalysis({symbolId}) first • BEFORE exploring an unfamiliar codebase → run getArchitectureOverview() • BEFORE refactoring → trace getDependencies + getDependents for blast radius • Running 3+ Grep calls for structure? STOP → use code_intel instead TOP 5 QUESTIONS (query is case-insensitive substring match): • "Where is X defined?" / "Find function Y" → searchSymbols({query}) • "What calls X?" / "What imports this?" → getDependents({filePath}) or getCallGraph({symbolId}) • "What does X depend on?" → getDependencies({filePath}) • "Safe to modify X?" / "Blast radius?" → impactAnalysis({symbolId}) • "Find dead code" / "Unused exports?" → findOrphanedCode() • "Complex functions?" / "Refactoring targets?" → searchSymbols results include complexity.cyclomaticComplexity + complexityRisk per function NOT FOR: literal string search, log messages, config values, or reading source code. Use Grep/Glob/Read for those. Supports TypeScript, JavaScript, Python, and more — run api.getCapabilities() to check your project. File-path-scoped methods (getDepen…
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | JavaScript code to execute. Can use top-level await. Available API methods: searchSymbols, getSymbolDetails, getDependencies, getDependents, findCircularDependencies, traceSymbolUsage, getCallGraph,… |
| cwd | string | yes | Absolute path to the project directory being queried. Used to locate the correct constellation.json by finding the git repository root. Set this to the root of the repository or workspace folder you… |
| timeout | number | – | Optional execution-time override in milliseconds. When omitted, the sandbox derives the timeout from the static complexity of your code (heavier api.* methods raise the budget) and clamps the result… |
| Name | Type | Req | Description |
|---|---|---|---|
| asOfCommit | string | – | – |
| error | string | – | – |
| lastIndexedAt | string | – | – |
| logs | array | – | – |
| result | – | – | – |
| resultContext | object | – | – |
| success | boolean | yes | – |
| time | number | – | – |
| timeoutBreakdown | object | – | – |
No examples provided.
What is the com.shiftinbits/constellation MCP server?
com.shiftinbits/constellation is an MCP server listed in the public MCP registry as com.shiftinbits/constellation. Code Intelligence Platform for AI Coding Agents. This page covers its npm package (@constellationdev/mcp).
Is the com.shiftinbits/constellation MCP server safe to use?
com.shiftinbits/constellation scores 97 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 com.shiftinbits/constellation MCP server expose?
com.shiftinbits/constellation exposes 1 tool: code_intel. Their descriptions and schemas cost roughly 837 tokens of context every time the server is loaded.
Is the com.shiftinbits/constellation MCP server still maintained?
com.shiftinbits/constellation is still listed as active in the MCP registry. We last reached this channel on 20 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 com.shiftinbits/constellation MCP server under?
com.shiftinbits/constellation declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.