Free context-engineering audits for AI agents. BYOK Anthropic key. Top-3 findings per scan.
Free-tier context engineering audits for production AI agents, delivered as MCP tools you can call from Claude Desktop, Cursor, Claude Code, or any MCP-compatible client.
What you get: top-3 findings on your system prompts, tool definitions, or context packing, on demand, no account needed.
What it costs: nothing. The free scan is genuinely free. Upgrade paths to the $49 Instant Audit and $750 Full Audit are surfaced in the response footer; they're not paywalls on this tool.
Most production agent failures aren't model failures — they're context engineering failures. Ambiguous instructions, underspecified tools, bloated context, no regression tests on prompt changes. Those problems are spottable by a trained reader. Archonics has trained that reader and published it as an MCP tool so you can get a second opinion on your agent's context without filing a support ticket.
The underlying audit engine applies Archonics Audit Methodology v1.0, the same spec that drives our paid audits.
audit_system_promptPaste a system prompt. Get back the three most important context engineering issues in it, ranked by severity, with specific recommendations.
Covers: role clarity, instruction conflicts, negative space, priority structure when instructions conflict, token efficiency, format specification precision, failure-mode coverage.
audit_tool_definitionPaste a tool/function definition. Get back the three most important issues affecting how reliably the model will call it.
Covers: description quality (the "when to use this tool" question), parameter schema precision, parameter documentation, error response design, discoverability.
audit_context_packingPaste a representative context payload (or describe it structurally). Get back the three most important efficiency and quality issues.
Covers: content inventory, redundancy across sections, freshness/relevance, ordering, truncation risk, prompt-cache utilization.
Add to your claude_desktop_config.json:
{
"mcpServers": {
"archonics-audit": {
"command": "npx",
"args": ["-y", "@archonics/mcp-audit"],
"env": {
"ANTHROPIC_API_KEY": "your-anthropic-api-key-here"
}
}
}
}
Add to your .cursor/mcp.json:
{
"mcpServers": {
"archonics-audit": {
"command": "npx",
"args": ["-y", "@archonics/mcp-audit"],
"env": {
"ANTHROPIC_API_KEY": "your-anthropic-api-key-here"
}
}
}
}
claude mcp add archonics-audit npx -y @archonics/mcp-audit
Then set ANTHROPIC_API_KEY in your environment.
The audit engine runs on Claude. You bring your own API key so:
If you'd rather not bring your own key, use the $49 Instant Audit at agent.market — we cover the API costs and return a full-methodology audit PDF.
Submitted content is processed ephemerally. No prospect content is retained on Archonics infrastructure or used to train any model. The API call pattern is: your client → your Anthropic API key → Anthropic → your client. Archonics servers are not in this path.
Aggregated, anonymized patterns across many audits may inform improvements to the methodology — "18 of 20 audited systems lacked prompt-regression tests" — but specific content never feeds that process.
Details: archonics.ai/privacy
If the free scan surfaces issues worth fixing, two paid tiers go deeper:
MIT. Use it, fork it, audit yourself.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @archonics/mcp-auditMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-archonics-mcp-audit": {
"command": "npx",
"args": [
"-y",
"@archonics/mcp-audit"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@archonics/mcp-auditnpmio.github.archonics/mcp-audit works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.