Inspectra MCP Server
inspectra
npm
v0.7.2
Source verified
Published by fascinax — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Multi-agent code audit system powered by GitHub Copilot Custom Agents and MCP
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 3.6 = 96. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −3.6 | Near-miss of @modelcontextprotocol/inspector MTC-SUP-005 | supply-chain |
2. Client adoption risk — 96 − 6 = 90. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 3
high Shell/command execution in server code (mcp/dist/tools/conventions-analysis.js)MTC-SRC-002
In the server's implementation (`mcp/dist/tools/conventions-analysis.js:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: { execFile } from "node:child_process"; import { promisify } from "node:util"; import { createIdSequence } from "../util
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server mcp/dist/tools/conventions-analysis.js
high Shell/command execution in server code (mcp/dist/tools/security.js)MTC-SRC-002
In the server's implementation (`mcp/dist/tools/security.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: { execFile } from "node:child_process"; import { readFile } from "node:fs/promises"; import { join } from "node:path"; i
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server mcp/dist/tools/security.js
medium Near-miss of @modelcontextprotocol/inspector (edit distance 2)MTC-SUP-005
"inspectra" is edit-distance 2 from the package "@modelcontextprotocol/inspector". Verify this is the intended package.
Fix: Confirm you meant "@modelcontextprotocol/inspector". Install packages only from their documented, official name.
Location: package inspectra
Tools 49
Each tool and what it can reach — statically extracted from the published source.
inspectra_age_todosno sensitive capabilityinspectra_analyze_bundle_sizeno sensitive capabilityinspectra_analyze_complexityno sensitive capabilityinspectra_analyze_dependenciesno sensitive capabilityinspectra_check_a11y_templatesno sensitive capabilityinspectra_check_adr_presenceno sensitive capabilityinspectra_check_build_timingsno sensitive capabilityinspectra_check_dead_exportsno sensitive capabilityinspectra_check_dependency_stalenessno sensitive capabilityinspectra_check_deps_vulnsno sensitive capability
Show 39 more tools ↓
inspectra_check_file_lengthsno sensitive capabilityinspectra_check_function_lengthsno sensitive capabilityinspectra_check_i18nno sensitive capabilityinspectra_check_layeringno sensitive capabilityinspectra_check_magic_numbersno sensitive capabilityinspectra_check_maven_depsno sensitive capabilityinspectra_check_namingno sensitive capabilityinspectra_check_observabilityno sensitive capabilityinspectra_check_param_countsno sensitive capabilityinspectra_check_readme_completenessno sensitive capabilityinspectra_check_rest_conventionsno sensitive capabilityinspectra_check_test_qualityno sensitive capabilityinspectra_check_todosno sensitive capabilityinspectra_check_ux_consistencyno sensitive capabilityinspectra_compare_reportsno sensitive capabilityinspectra_detect_circular_depsno sensitive capabilityinspectra_detect_code_smellsno sensitive capabilityinspectra_detect_deprecated_apisno sensitive capabilityinspectra_detect_doc_code_driftno sensitive capabilityinspectra_detect_dry_violationsno sensitive capabilityinspectra_detect_env_example_driftno sensitive capabilityinspectra_detect_flaky_testsno sensitive capabilityinspectra_detect_missing_testsno sensitive capabilityinspectra_detect_runtime_metricsno sensitive capabilityinspectra_generate_claude_mdno sensitive capabilityinspectra_generate_codex_agents_mdno sensitive capabilityinspectra_log_activityno sensitive capabilityinspectra_merge_domain_reportsno sensitive capabilityinspectra_parse_coverageno sensitive capabilityinspectra_parse_lint_outputno sensitive capabilityinspectra_parse_playwright_reportno sensitive capabilityinspectra_parse_test_resultsno sensitive capabilityinspectra_read_activity_logno sensitive capabilityinspectra_render_htmlno sensitive capabilityinspectra_render_pdfno sensitive capabilityinspectra_render_trendno sensitive capabilityinspectra_run_semgrepno sensitive capabilityinspectra_scan_secretsno sensitive capabilityinspectra_score_findingsno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (49 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.7.2 latest |
A 90/100 | 3 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan inspectra --onlineMore in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.