Auxiliar Mcp

io.github.auxiliar-ai由 GitHub 账号 auxiliar-ai 发布v0.23.0更新于 Nov 3, 2026

Eval-backed discovery for the auxiliar.ai gateway — the best web-access provider per job, measured.

概览

AI 生成的概览

本地 stdio MCP 服务器,基于实测基准评分卡,为搜索、抓取、浏览器自动化、语音等任务推荐最合适的网页访问服务商。

可以做什么
  • 针对 search、scrape、crawl、extract、screenshot、act 等任务动词,按质量、延迟、成本等约束推荐排序后的服务商
  • 查看某个动词的完整排行榜,含原始指标与运行日期
  • 查看单个服务商的完整信息:路由、定价、选用与避坑建议、带日期的评分卡
  • 说明 auxiliar.ai 网关是什么、如何获取密钥、如何调用
  • 返回推荐服务商的可执行调用方式
适用场景
当助手需要在众多网页访问 API 中做选择,并希望依据公开、带日期的基准数据而非猜测时适用;也适合计划通过 auxiliar.ai 网关统一调用网页任务的场景。
运行要求
通过 npx 在本地运行(需要 Node.js)。未声明任何环境变量或请求头。基准数据运行时从 auxiliar.ai 获取,离线时回退到内置快照。真正调用推荐的服务商需要另行获取 auxiliar.ai API 密钥。
安装前请注意
服务器本身未声明凭据,但其返回的调用方式使用 auxiliar.ai API 密钥作为 bearer 令牌,用量按各服务商的实际计量价格从网关额度中扣费。推荐结果指向特定商业网关。基准数据在运行时从远程文件加载,排名依赖该来源。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Auxiliar Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

auxiliar-mcp

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

bash
claude mcp add auxiliar -- npx auxiliar-mcp

or in any MCP client config:

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

Tools

ToolWhat it does
recommend_toolsBest provider(s) for a job (search, scrape, crawl, extract_ai, extract_rules, answer, screenshot, scrape_domain, act, act_agent, serp, parse, watch), ranked by measured quality/latency/cost/errors. Optional optimize_for, max_latency_ms, max_cost_usd, limit.
get_scorecardThe full leaderboard for one verb — every scored provider, raw metrics, run dates.
get_providerOne provider in full: route, pricing, choose/avoid guidance, all its dated scorecards.
about_auxiliarWhat the gateway is, how to get a key, how to call it.

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

bash
npm installnpm run build         # tsc → dist/ (+ bundled data snapshot)npm test              # unit tests + end-to-end stdio round-tripnpm 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

来源:README.md,提交 42cdcaa

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.23.0最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分