Find the cheapest AI model that passes your own tests, and keep it that way.
Claude · Gemini · OpenAI · Bedrock · Vertex AI · local models — published by Indigloo
Install · How it works · MCP tools · Quick start · Privacy · Security
How it works
flowchart LR
A["Audit<br/><sub>models and SDKs in your repo</sub>"] --> B["Draft evals<br/><sub>from your prompts, PII dropped</sub>"]
B --> C["Evaluate<br/><sub>your keys · pass rate · latency · cost</sub>"]
C --> D["Rank<br/><sub>cost per passing answer</sub>"]
D --> E["Route<br/><sub>cheapest first, escalate on failure</sub>"]
F["Size<br/><sub>weights + KV cache vs your GPU</sub>"] -.-> C
classDef step fill:#f3f0e8,stroke:#1c1b19,color:#1c1b19;
classDef pick fill:#f3f0e8,stroke:#cd462a,color:#cd462a;
class A,B,C,E,F step;
class D pick;
| Skill | What it does |
|---|---|
find-model |
Recommends models across Claude, Gemini, OpenAI, cloud, and local options for your task, budget, and route, including coding subtasks in an IDE. |
eval-models |
Runs your examples against shortlisted models and measures pass rate, latency, and billed cost with your own keys. |
route-models |
Builds a cheapest-first routing setup: a standalone router with quality guards plus a LiteLLM config. |
size-local-model |
Estimates memory for weights and KV cache and compares it with your hardware. |
Advisory only: nothing is deployed, your active model is never changed, and data goes only to providers you configure and approve. Personal data and secrets are blocked before sending by default; see DATA-PROTECTION.md for how this maps to India's DPDP Act.
Install
Requires Python 3.9+ on your PATH as python3 (see Windows). Nothing to pip install.
| Client | Command | Skills | MCP tools |
|---|---|---|---|
| Claude Code | /plugin marketplace add Abhiindigloo/EvalHarness then /plugin install model-finder@model-finder |
✅ | ✅ via .mcp.json |
| OpenAI Codex CLI | codex plugin marketplace add Abhiindigloo/EvalHarness then codex plugin add model-finder@model-finder |
✅ | ✅ via mcp.json (Agent Plugins format, runs ./mcp/server.py). Codex gives the server no workspace, so the agent passes the project path |
| GitHub Copilot CLI | copilot plugin marketplace add Abhiindigloo/EvalHarness then copilot plugin install model-finder@model-finder |
✅ | ✅ via mcp.json |
| Gemini CLI | gemini extensions install https://github.com/Abhiindigloo/EvalHarness |
✅ | ✅ via gemini-extension.json |
| Cursor | Install from the Cursor marketplace or cursor.directory once listed. Until then, clone into ~/.cursor/plugins/local/model-finder and reload the window |
✅ | ✅ via mcp.json or .cursor-plugin/plugin.json → .mcp.json |
| Any MCP client, from PyPI | uvx model-finder-mcp (published by the release workflow; see Releases) |
— | ✅ |
| VS Code, JetBrains, Windsurf, others | Add the server to the client's MCP settings (manual setup) | — | ✅ |
| Other Agent Skills clients | Copy skills/<name>/ into the client's skills directory |
✅ | — |
Gemini CLI only starts extension MCP servers in folders you have trusted; it asks the first time you open a project.
Manual MCP setup
VS Code — .vscode/mcp.json (top-level key is servers)
{
"servers": {
"model-finder": {
"type": "stdio",
"command": "python3",
"args": ["/absolute/path/to/EvalHarness/mcp/server.py"],
"env": { "MODEL_FINDER_ROOT": "${workspaceFolder}" }
}
}
}
Cursor — .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"model-finder": {
"command": "python3",
"args": ["/absolute/path/to/EvalHarness/mcp/server.py"],
"env": { "MODEL_FINDER_ROOT": "${workspaceFolder}" }
}
}
}
JetBrains, Windsurf, Claude Desktop and others — mcpServers
If the client has no workspace variable, write the project path:
{
"mcpServers": {
"model-finder": {
"command": "python3",
"args": ["/absolute/path/to/EvalHarness/mcp/server.py"],
"env": { "MODEL_FINDER_ROOT": "/absolute/path/to/your/project" }
}
}
}
Clone the repo once and replace /absolute/path/to/EvalHarness. Repository tools read only inside the workspace: the roots your client shares over MCP, else MODEL_FINDER_ROOT, else the server's working directory. A filesystem root or home directory is refused.
Windows
Codex, Copilot CLI and Cursor start the server as ./mcp/server.py, which relies on its #!/usr/bin/env python3 line; on Windows use the manual setup or uvx model-finder-mcp. If python3 is not on your PATH, the MCP server will not start. Install Python from python.org (tick "Add python.exe to PATH") and either create a python3 alias or use the manual setup with "command": "py" and "args": ["-3", "C:/path/to/EvalHarness/mcp/server.py"].
MCP tools
Ten read-only tools, so the same features work as tools in every supported IDE:
| Tool | What it does |
|---|---|
modelfinder_audit_models |
Lists AI model IDs and SDKs in your repo with file:line locations, routes and hard-coded IDs |
modelfinder_draft_eval_examples |
Drafts eval examples from prompt files and fixtures, dropping anything with personal data or secrets |
modelfinder_create_eval_config · modelfinder_validate_eval_config |
Builds and checks an eval config: call count, env var names, unpriced models, guard verdict |
modelfinder_check_output |
Tests a reply against eval checks or routing guards |
modelfinder_rank_eval_results |
Ranks results by cost per passing answer, with the cost/reliability cascade |
modelfinder_generate_routing |
Returns routing.json and a LiteLLM config from eval results |
modelfinder_estimate_cost |
Monthly token cost and cost per accepted result |
modelfinder_estimate_memory |
Local memory for weights and KV cache |
modelfinder_scan_sensitive_data |
Personal-data and secrets scan (categories and counts only) |
Every tool returns a readable markdown summary by default and the full result as structured JSON (response_format: "json" puts the JSON in the text too). Large results are paginated (limit, offset, has_more, next_offset), modelfinder_audit_models can filter by provider family or hard-coded IDs, and unknown arguments are rejected with the list of valid ones. The server never opens a network connection, never reads API keys and never writes files. Only eval_models.py and the generated router.py call model providers, with your keys, when you run them.
Quick start
In your IDE, ask: "Audit which AI models this repo uses, then draft evals from our prompts and test whether a cheaper model passes." The assistant uses the MCP tools to audit and draft, agrees checks with you, and asks before the paid run.
From a terminal:
cp skills/eval-models/assets/example-config.json my-eval.json # fill in verified model IDs and prices
export ANTHROPIC_API_KEY=... GEMINI_API_KEY=... OPENAI_API_KEY=...
python3 skills/eval-models/scripts/repo_scan.py audit . # what the repo uses
python3 skills/eval-models/scripts/repo_scan.py examples . # draft examples from prompt files
python3 skills/eval-models/scripts/eval_models.py my-eval.json --dry-run
python3 skills/eval-models/scripts/eval_models.py my-eval.json --out results
python3 skills/route-models/scripts/make_routing.py --results results/results.json --guards guards.json --out routing
python3 routing/router.py routing/routing.json "your prompt"
Size a local model:
python3 skills/size-local-model/scripts/estimate_memory.py --params-b 8.03 --bits 16 \
--layers 32 --kv-heads 8 --head-dim 128 --context 8192 --available-gib 24
Tests
python3 -m unittest discover -s tests -v
End-to-end tests run against a local mock of the OpenAI-compatible, Anthropic, and Gemini APIs, and drive the MCP server over stdio; no key or network access is needed. evaluations/ holds a 10-question agent evaluation of the MCP tools.
Releases
- Bump the version everywhere (
python3 tests/check_release_version.pylists any field that differs) and add a CHANGELOG entry. - Push a tag
vX.Y.Z.release.ymlruns the tests, checks the versions, builds the package, publishes it to PyPI with trusted publishing, then publishesserver.jsonto the official MCP Registry. - One-time setup:
- PyPI: add a pending trusted publisher for project
model-finder-mcp(ownerAbhiindigloo, repositoryEvalHarness, workflowrelease.yml, environmentpypi), ideally from the Indigloo PyPI organization, and create thepypienvironment in the repository settings. - MCP Registry (
co.indigloo/model-finder, verified through the indigloo.co domain). On your own machine, with OpenSSL 3:openssl genpkey -algorithm Ed25519 -out mcp-registry-key.pem echo "TXT record for indigloo.co: v=MCPv1; k=ed25519; p=$(openssl pkey -in mcp-registry-key.pem -pubout -outform DER | tail -c 32 | base64)" echo "GitHub secret MCP_REGISTRY_PRIVATE_KEY: $(openssl pkey -in mcp-registry-key.pem -noout -text | grep -A3 'priv:' | tail -n +2 | tr -d ' :\n')"
Add the TXT record at the apex of indigloo.co, create a repository environmentmcp-registry, store the hex key as its secretMCP_REGISTRY_PRIVATE_KEY, then deletemcp-registry-key.pemor keep it in a password manager.
- PyPI: add a pending trusted publisher for project
Repository layout
skills/ shared Agent Skills (single source of truth)
mcp/server.py local MCP server (stdio, standard library only)
.mcp.json MCP launch config for Claude Code and Cursor (${CLAUDE_PLUGIN_ROOT}); disabled as a
project config inside this repo by .claude/settings.json
mcp.json Agent Plugins MCP launch config (Codex, Copilot CLI, Cursor): runs ./mcp/server.py
server.json, pyproject.toml MCP Registry entry and PyPI package (model-finder-mcp); pypi/ holds the package marker
glama.json Glama directory ownership
.github/workflows/ tests on every push; release.yml publishes tags to PyPI and the MCP Registry
.claude-plugin/ Claude Code (and Copilot CLI) plugin + marketplace manifests
.codex-plugin/ Codex plugin manifest
.agents/plugins/ Codex repository marketplace
.cursor-plugin/ Cursor plugin + marketplace manifests
gemini-extension.json Gemini CLI extension (context: GEMINI.md)
plugin.json Agent Plugins manifest with OpenAI listing metadata
AGENTS.md, GEMINI.md skill index for agents that read root instructions
PRIVACY.md, TERMS.md, SUPPORT.md pages the marketplace listings link to
assets/ logo, README plates, and DESIGN.md (the visual language)
skills/eval-models/scripts/mf_core.py is duplicated in skills/route-models/scripts/ so each skill works on its own. The test suite fails if the copies differ.
Support · Privacy · Terms · Security · Data protection
MIT License · © 2026 Indigloo Softwares Private Limited
Metadata
Release files for model-finder-mcp 1.3.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| model_finder_mcp-1.3.5.tar.gz | 68.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| model_finder_mcp-1.3.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 148.9 kB
Release files / model_finder_mcp-1.3.5.tar.gz
| Download URL | model_finder_mcp-1.3.5.tar.gz |
|---|---|
| Size | 68.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a2046a0bcd6c00517ab716d2c3f7dc4f1799bb86d1a9ff6bfac49a42c8bd4081
|
|
BLAKE2b-256 checksum How to use checksums |
7ce0fed1f2054fc82207131f04fd756d2de0942120a22eb59d48558e8cd84067
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logRelease files / model_finder_mcp-1.3.5-py3-none-any.whl
| Download URL | model_finder_mcp-1.3.5-py3-none-any.whl |
|---|---|
| Size | 80.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4df6bf258cee3ed78d8d3fcade2c5fc0fb2631d139e5d57ed282dd97a1633e23
|
|
BLAKE2b-256 checksum How to use checksums |
0dd7ba9c00794d410bca5fe39f939e853d46841c3cebe447b7def40fca4f12b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency log