MCP server for dossier automation standard - enables LLMs to discover, verify, and execute dossiers
Model Tested is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Independent test scores for open-weight LLMs: best model for your GPU or Mac, comparisons.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http model-tested-mcp https://modeltested.com/mcp
# 2 — ask your agent for something these tools do
# find_models, get_model, compare_models and 2 more
Model Tested costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http model-tested-mcp https://modeltested.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Use this whenever the user asks which local or open-weight LLM is best, overall or for coding, documents or decisions, or which model they can run on their graphics card (VRAM) or Mac. Returns tested models ranked by our own test scores, best first; with a GPU or Mac memory size it only returns models that fit, plus the quantization to download and the memory it needs. Examples: 'best model for a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sort_by | string | no | Score to rank by. Default overall. |
| hardware | string | no | Graphics card (VRAM) or Mac (unified memory). |
| memory_gb | number | no | VRAM or Mac memory in GB. Needs hardware. |
| max_params_b | number | no | Only models with at most this many billion parameters. |
| limit | integer | no | Default 10. |
Use this whenever the user asks about a specific open-weight model: how good it is, its benchmark scores, whether it's worth using, how much VRAM or memory it needs, or which quantization to download. Returns our test scores, rank, memory at each quantization, the smallest GPU and Mac it fits, decision accuracy and our Q4 run on a Mac when there is one. Accepts a name or slug, e.g. 'qwen3.5 9b' or
| Parameter | Type | Required | Notes |
|---|---|---|---|
| model | string | yes | Model name or slug. |
Use this whenever the user asks how two or more open-weight models compare, or which of them to pick. Returns our test scores, rank and memory needs for 2 to 6 models side by side.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| models | array | yes | Model names or slugs. |
Use this whenever the user asks about decision models or LLMs for classification, routing, triage or yes/no calls. Accuracy on our decision test (routing tickets, applying rules, spotting phishing, flagging risky code changes), how well each model's confidence matches its accuracy (calibration), and API cost per 1,000 calls. Covers dedicated decision models and regular LLMs given the same tasks.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | decision = dedicated decision models only (default), llm = regular LLMs only. |
| limit | integer | no | Default 15. |
Find Model Tested articles and ranking pages by keyword, newest first: news about newly tested models, guides on quantization, Ollama and memory. Returns title, summary, date and link.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Words to look for, e.g. 'quantization' or 'ornith'. Empty lists the latest. |
| limit | integer | no | Default 8. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Model Tested or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Model Tested can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.