TheAIMeters MCP server
Which servers in the official MCP registry are TheAIMeters's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-15
- Registry namecom.theaimeters/theaimetersverified in the MCP registry
The registry name sits under theaimeters.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-15
- Tools5
- Server calls itselftheaimeters
- Server version0.1.0
- Protocol version2025-06-18
On 2026-10-15 the server answered initialize and tools/list without a sign-in. First answer in 157 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 3 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
- Answeredmeasuring3 of the 7 daily checks it takes to print a share
- Median first answer563 ms
- Space in an agent's context≈ 643 tokensthe definitions of all its tools (5), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results5 of 5 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
list_metersList all meters as returned by the TheAIMeters API, without recalculating their values.
get_meterGet one meter by its exact slug from list_meters (not its UUID). Use this when the slug is known; this is not a text search. Returns the stored API data without recalculating values, or a tool error if the meter does not exist.
search_metersFind meters when the exact slug is unknown. The backend searches for a literal, case-insensitive substring in slug, label, group and sourceNote, and orders matches by slug. This is not semantic search; no matches returns an empty meters…
get_methodologyExplain how TheAIMeters indicators are produced. Omit slug for the general methodology and meter-to-methodology mappings. Supply an exact meter slug for its calculation, formula, assumptions, limitations, refresh policy and structured…
get_sourcesList the complete TheAIMeters source catalog with stable IDs, names, URLs and categories. Use this for an overview of references. For sources supporting one specific meter, use get_methodology with its slug. Does not fetch the referenced…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"theaimeters": {
"type": "http",
"url": "https://www.theaimeters.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http theaimeters https://www.theaimeters.com/mcpclaude.ai, ChatGPT and other clients: add https://www.theaimeters.com/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.