github TypeScript re-analysis due

ni-c/mcp-integration-harness

Drive an MCP server over real stdio against a real backend, and prove every tool was exercised

Drift inferred · capture-to-capture

No drift recorded — single capability capture; advisories appear once its surface changes.

capabilities 0 tools

transport — counts 0 tools · 0 res · 0 prompts permission surface via code analysis

No tools enumerated yet for this server.

skills & danger signals github-tarball

prompt-surface shipped agent-instruction files + hidden-content / dangerous-code findings — quoted from the analyzed source

analyzed commit 0b2cd15 · analyzer v33 · 1w ago

suspicious endpoint 169.254.169.254 (cloud metadata) ni-c-mcp-integration-harness-0b2cd15/test/loopback.test.ts :33 'http://169.254.169.254/latest/meta-data/',

code evidence vv0.1.0 · github-tarball

evidence-backed findings quoted directly from the published source artifact — not inferred

code files: 11

net ni-c-mcp-integration-harness-0b2cd15/src/wait.ts :1 import { createConnection } from 'node:net';
net (weak) ni-c-mcp-integration-harness-0b2cd15/test/wait.test.ts :1 import { createServer, type Server } from 'node:http';

prepublishOnly ni-c-mcp-integration-harness-0b2cd15/package.json :45 npm run build