Auxiliar

Eval-backed tool discovery for AI agents, on the auxiliar.ai web-access gateway — one API key for 24 search, scraping, browser-automation and voice APIs, upstream keys injected server-side, usage at each provider's real metered price.

Ask it "what's the best provider for this job?" and it answers from measured public benchmarks — every provider runs the identical task corpus per verb; scorecards carry their run dates; weak scores are published, not hidden.

Install

claude mcp add auxiliar -- npx auxiliar-mcp

or in any MCP client config:

{ "mcpServers": { "auxiliar": { "command": "npx", "args": ["auxiliar-mcp"] } } }

Tools

Every response carries the run date behind each number (measured_on, latest_run), the ranking context (rank #n of m), honest caveats, providers excluded_by_constraints (never silently dropped), and gated_not_scored entries for providers that couldn't be scored on the shared corpora.

Recommendations return an executable call pattern:

https://api.auxiliar.ai/{provider}/{provider-native-path}
Authorization: Bearer <your auxiliar API key>

Same paths, parameters and responses as each provider's own docs — the gateway injects the upstream key server-side. Get a key (with $5 free credit, no card) at auxiliar.ai.

Where the data comes from

Benchmark data loads at runtime from auxiliar.ai/evals.json (1h in-memory cache) and falls back to a bundled snapshot offline — responses declare which via data_source. The same data renders the human-readable scorecards at auxiliar.ai/tools. Rankings carry no house incentive: the gateway's fee is flat at credit top-up, so nothing is earned by steering you toward pricier providers.

Development

npm install
npm run build         # tsc → dist/ (+ bundled data snapshot)
npm test              # unit tests + end-to-end stdio round-trip
npm run update-fallback  # refresh src/data/evals-fallback.json from production

Releasing: bump the version in package.json and server.json (two spots) — npm run check-versions (run automatically at prepublish) enforces sync — then npm publish and mcp-publisher publish.

Roadmap

• v0.23 (this release) — eval-backed discovery.
• v1.0 — in-loop execution: call the providers through the gateway from this MCP (web_search, scrape, extract, crawl, …), routed by the same measured rankings.

License

MIT