adsp-sdk-mcp-server@1.24.1
VERIFIEDPublisher claims: "Government of Alberta - MCP server for ADSP documentation and Node SDK reference lookup." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Server started and answered tools/list.- Tested
- MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
- Not tested
- what the tools do when called with real credentials
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- what the tools do when called with real credentials
Reasonable to connect. No credential asked for, no third-party host named, Server started and answered tools/list.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-11 and scored it 88/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 26 s · 2 scenarios · 0 deviationsStatic findings
console.error(`[adsp-sdk-mcp-server] Unknown MCP_TRANSPORT="${raw}". Valid values: stdio, http. Defaulting to stdio.`);Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.return 'Access token was rejected (401). Run `npx @abgov/adsp-cli login` again to refresh it.';Fix: Pin versions and sources; vendor anything fetched at install time.{ type: 'text', text: 'Not authenticated. Run `npx @abgov/adsp-cli login` in a terminal, then retry.' },Fix: Pin versions and sources; vendor anything fetched at install time.'authentication: run `npx @abgov/adsp-cli login` once in a terminal (interactive), or set ' +Fix: Pin versions and sources; vendor anything fetched at install time.console.error(`[adsp-sdk-mcp-server] HTTP server listening on :${port}`);Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.'Requires authentication: run `npx @abgov/adsp-cli login` once in a terminal (interactive), or set ' +Fix: Pin versions and sources; vendor anything fetched at install time.{ type: 'text', text: 'Not authenticated. Run `npx @abgov/adsp-cli login` in a terminal, then retry.' },Fix: Pin versions and sources; vendor anything fetched at install time.return 'Access token was rejected (401). Run `npx @abgov/adsp-cli login` again to refresh it.';Fix: Pin versions and sources; vendor anything fetched at install time.reason: 'Verify your email address.',Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for @abgov/adsp-sdk-mcp-server@1.24.1 as of 3d ago. This is the package itself, not its dependencies.