Inquisitor MCP server
io.github.1111111111111111111114oLvT2/inquisitor·v0.2.2·5 starsHypothesis-driven problem solving for AI agents: probe, falsify, escalate.
5 stars62 downloads/wk
Reviews
Write oneNobody has reviewed Inquisitor yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Inquisitor tools (7)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
inquisitor_analyzeScan a project directory and return a structured overview.
inquisitor_phase_getGet the current phase of the Newton investigation.
inquisitor_phase_setAdvance to a new phase in the Newton investigation process.
inquisitor_scaffoldSet up a new project with best practices and minimal boilerplate.
inquisitor_searchSearch the web using DuckDuckGo (free), Brave, or SearXNG.
inquisitor_traceTrace a function, class, or method through the codebase.
inquisitor_verifyValidate investigation findings against the original problem definitions.
Public scan report
scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it
- Code scan23 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 51 days ago12/15
- Maintainer identityregistry namespace matches repository owner6/10
How Inquisitor compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 70% of 48,255 servers
- Tools
- 7
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 5
- more than 83% of 28,688 servers
- Downloads a week
- 62
- more than 50% of 12,191 servers with a package
What its tools let an agent do: 7 read
Install Inquisitor in Claude Code, Cursor or VS Code
claude mcp add inquisitor -- uvx inquisitor-mcp
What the publisher says
From the Inquisitor repository's README, as published. We do not edit it. Read it on GitHub
inquisitor
Hypothesis-driven problem solving for AI agents Probe · Falsify · Escalate — never overcomplicate, never blind-retry
<!-- mcp-name: io.github.iamalisson/inquisitor -->
Overview
inquisitor makes AI agents solve problems the way a chess engine plays chess: it cannot explore every branch, so it estimates complexity first, prunes paths that add no information, and spends its search budget only where the problem actually is.
It ships as two coordinated layers:
- MCP server (inquisitor-mcp) — the engine. Web search, project analysis, code tracing, project scaffolding, and a persistent investigation state machine. Works with any MCP-compatible agent: OpenCode, Claude Code, Claude Desktop, Cursor.
- Agent skill (skills/inquisitor/SKILL.md) — the behavioral layer. Injects the probe-and-gate loop, the pruning rules, and the full methodology into the agent's reasoning.
The method is not invented here — it is assembled from primary sources: Newton's Analysis→Synthesis skeleton, hardened with the scientific method's own defenses against wrong assumptions (falsification, strong inference, competing-hypotheses analysis, anti-fixation reframes, pre-mortems) and constrained by engineering discipline (NASA/JPL's Power of Ten, surgical-change guidelines, the minimalism ladder). Every source is cited in Foundations.
Web search, codebase scans, and code tracing are tools invoked when local evidence is insufficient — never mandatory rituals.
How it decides
Depth is an output, not a label. An LLM's up-front difficulty guess is its least reliable signal — poorly calibrated, and biased to under-rate exactly the hard problems that matter. So inquisitor never classifies a problem before understanding it: it runs a cheap probe (the single cheapest action that could confirm or kill the best current hypothesis), and the probe's result — never the prediction — sets the depth:
flowchart TD
P([Problem]) --> F["FRAME<br/>done = ? · must not break = ?"]
F --> D{"delegate?<br/>a specialist skill<br/>owns this"}
D -->|yes| SK["hand off — /tdd,<br/>/code-review, ..."]
D -->|no| PR["PROBE<br/>cheapest action that could confirm<br/>or kill the best hypothesis"]
PR -->|"obvious, local"| SH["<b>Shallow</b><br/>fix → verify<br/><i>no ceremony</i>"]
PR -->|"clear single-<br/>component cause"| ST["<b>Standard</b><br/>frame → minimal evidence<br/>→ fix → verify"]
PR -->|"root cause unknown,<br/>multi-component"| DE["<b>Deep</b> — Newton 7-phase:<br/>DEFINE → AXIOMS → ANALYSIS →<br/>EXPERIMENT → SYNTHESIS →<br/>VALIDATE → QUERY<br/><i>+ session tracking as memory</i>"]
SH -.->|"gate trigger /<br/>failed fix / low confidence"| ST
ST -.->|"gate only raises depth —<br/>never lowers"| DEShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Inquisitor: common questions
- Is Inquisitor MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the Inquisitor safety report
- How do I install Inquisitor?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Inquisitor need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Inquisitor maintained?
- The last commit was 90 days ago (2026-08-05). The latest release is v0.2.2.
- How does Inquisitor compare with other MCP servers?
- safety score 85/100 (higher than 70% of 48,255 servers); tools 7 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.