Optimal-path problem solving for AI agents: web search, code tracing, Newton-method investigation.
Inquisitor MCP server exists for a simple reason — assistants are far more useful when they can act on Inquisitor directly instead of describing what you should do. Optimal-path problem solving for AI agents: web search, code tracing, Newton-method investigation.
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.
Once Inquisitor is connected, these are the calls the assistant has available:
inquisitor_search — Multi-backend web search (DuckDuckGo free/keyless, Brave, SearXNG) with content extraction (HTML + PDF)inquisitor_analyze — Project overview: languages, frameworks, tests, deps, git historyinquisitor_trace — Symbol tracing: definition, callers, callees with file:line refsinquisitor_verify — Completeness check: every phase recorded? evidence cited? (semantic validation — contradictions, DEFINE satisfaction — stays with the agent)inquisitor_scaffold — Minimal project scaffolding with researched best practicesBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 2 environment variables: BRAVE_API_KEY, SEARXNG_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the search and retrieval group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Inquisitor's toolset — inquisitor_search, inquisitor_analyze, inquisitor_trace and 2 more — is a fair guide to whether it matches your workflow. It is maintained by 1111111111111111111114oLvT2; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Inquisitor's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| inquisitor_search | Multi-backend web search (DuckDuckGo free/keyless, Brave, SearXNG) with content extraction (HTML + PDF) |
| inquisitor_analyze | Project overview: languages, frameworks, tests, deps, git history |
| inquisitor_trace | Symbol tracing: definition, callers, callees with file:line refs |
| inquisitor_verify | Completeness check: every phase recorded? evidence cited? (semantic validation — contradictions, DEFINE satisfaction — stays with the agent) |
| inquisitor_scaffold | Minimal project scaffolding with researched best practices |
{
"mcpServers": {
"inquisitor": {
"command": "npx",
"args": ["-y", "skills"],
"env": {
"BRAVE_API_KEY": "your-value",
"SEARXNG_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| BRAVE_API_KEY | Credential the server authenticates with. | Yes |
| SEARXNG_URL | Endpoint or connection string the server talks to. | Yes |
The simplest web tool that matters — fetch any URL and get model-ready markdown back.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Put 6,000+ pre-built scrapers at your assistant's fingertips through one MCP endpoint.