Modelmeter MCP
An MCP server that exposes tools for querying AI model deprecations, pricing, and capabilities, allowing agents to check stack health, estimate costs, and retrieve model details via JSON-RPC.
Endpoint and access
No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.
https://modelmeter.xyz/mcpWhat its tools do
7 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.
Checks and signals
Each line is separate evidence, not a trust score.
- Passed Endpoint answered the live check ·
- Passed Official MCP Registry namespace is tied to modelmeter.xyz ·
- Passed Endpoint is on the registry namespace domain ·
- Availability 1 of 1 checks passed in 30 days
What you can do with it
- Check if specific models are deprecating or retiring
- Estimate the cost of LLM calls given model and token counts
- List available models and their current pricing
- Retrieve historical pricing data for specific models
Source and maintenance
- Maintenance checked
Protocol and capabilities
- Server
- modelmeter 0.1.0
- MCP protocol negotiated in check
- 2025-06-18
- Tools
- 7 advertised
- Resources
- Not advertised
- Resource templates
- Not advertised
- Prompts
- Not advertised
{
"tools": {}
}Server-provided instructions
Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.
Tools
7 advertised
estimate_cost
Estimate the USD cost of an LLM API call for a given model and token counts. Returns input/output/total cost, plus reseller markup vs. the upstream model when applicable.
{
"type": "object",
"required": [
"model",
"input_tokens",
"output_tokens"
],
"properties": {
"model": {
"type": "string",
"description": "Model id in provider/model form, e.g. anthropic/claude-opus-4-8. Use list_models to discover ids."
},
"input_tokens": {
"type": "integer",
"minimum": 0,
"description": "Number of input (prompt) tokens."
},
"output_tokens": {
"type": "integer",
"minimum": 0,
"description": "Number of output (completion) tokens."
}
}
}get_model
Unified card for one model in a single call: normalized pricing, capabilities (context window, vision, reasoning, tags), availability, reseller markup vs. upstream, and a price-history summary (launch vs. current price, percent change, last change date, all-time low/high).
{
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Model id in provider/model form, e.g. openai/gpt-5-5."
}
}
}list_models
List available models with their current pricing. Optionally filter by provider.
{
"type": "object",
"properties": {
"limit": {
"type": "integer",
"maximum": 1000,
"minimum": 1,
"description": "Max rows to return. Default 200."
},
"provider": {
"type": "string",
"description": "Provider id, e.g. anthropic, openai, google, venice, openrouter."
},
"include_unavailable": {
"type": "boolean",
"description": "Include deprecated/restricted/unavailable models. Default false."
}
}
}get_price_history
Historical pricing time-series for a model or provider. Each point is a dated snapshot of the per-Mtok rates.
{
"type": "object",
"properties": {
"model": {
"type": "string",
"description": "Model id to fetch history for."
},
"since": {
"type": "string",
"description": "ISO date (YYYY-MM-DD); only points on/after this date."
},
"until": {
"type": "string",
"description": "ISO date (YYYY-MM-DD); only points on/before this date."
},
"provider": {
"type": "string",
"description": "Provider id to fetch history for (all its models)."
}
}
}list_events
The changelog of record for the model layer: deprecations, price changes, launches, and the market events around them. Filter by severity to find what demands action: 'breaking' (model going away, ID changing), 'action_required' (price/rate-limit/context changes), 'informational' (releases, funding).
{
"type": "object",
"properties": {
"type": {
"type": "string",
"description": "Event type, e.g. model_deprecation, pricing_change, model_launch."
},
"limit": {
"type": "integer",
"maximum": 500,
"minimum": 1,
"description": "Max events. Default 50."
},
"since": {
"type": "string",
"description": "ISO date (YYYY-MM-DD); events announced on/after."
},
"until": {
"type": "string",
"description": "ISO date (YYYY-MM-DD); events announced on/before."
},
"status": {
"enum": [
"verified",
"unverified",
"all",
"corrected"
],
"type": "string",
"description": "Verification status. Default 'verified' (human-confirmed). 'all' = verified + unverified."
},
"provider": {
"type": "string",
"description": "Filter to events touching this provider."
},
"severity": {
"enum": [
"breaking",
"action_required",
"informational"
],
"type": "string",
"description": "Filter by what the event demands of consumers of the affected models."
}
}
}check_model_dependencies
Is my stack okay? Check a list of model ids against the record: scheduled retirements with days-remaining countdowns and migration targets, past retirements, and other breaking/action-required changes. Id matching tolerates dots vs dashes, dated snapshot suffixes, and bare or provider-prefixed forms. Call this at startup or in CI with the models you depend on.
{
"type": "object",
"required": [
"models"
],
"properties": {
"models": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 50,
"minItems": 1,
"description": "Model ids to check, e.g. [\"gpt-4o\", \"claude-sonnet-4-6\", \"gemini-2.5-flash\"]."
}
}
}list_deprecations
Per-model retirement rows from the record: which model dies when, with runway and migration target. Default shows scheduled (upcoming) retirements sorted by shutdown date.
{
"type": "object",
"properties": {
"limit": {
"type": "integer",
"maximum": 500,
"minimum": 1,
"description": "Max rows. Default 100."
},
"status": {
"enum": [
"scheduled",
"retired",
"all"
],
"type": "string",
"description": "Default scheduled."
},
"provider": {
"type": "string",
"description": "Filter to one provider id."
}
}
}Prompts
Not advertised
Resources
Not advertised
90-day uptime
A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.
- 2026-11-07: 1 of 1 checks answered
30-day availability
Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.
- Successful checks
- 1 of 1 (100%)
- Average latency
- 542 ms
- 95th percentile latency
- 542 ms
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · probe · passed · 542 ms · metadata changed · 7 tool(s)
Connect from your client
Each snippet registers the same endpoint; pick the client you use.
Claude Code
claude mcp add --transport http modelmeter-mcp https://modelmeter.xyz/mcpCodex
codex mcp add modelmeter-mcp --url https://modelmeter.xyz/mcpCursor
{
"mcpServers": {
"modelmeter-mcp": {
"url": "https://modelmeter.xyz/mcp"
}
}
}Cline
{
"mcpServers": {
"modelmeter-mcp": {
"type": "streamableHttp",
"url": "https://modelmeter.xyz/mcp",
"disabled": false
}
}
}VS Code
{
"servers": {
"modelmeter-mcp": {
"type": "http",
"url": "https://modelmeter.xyz/mcp"
}
}
}Gemini CLI
gemini mcp add --transport http modelmeter-mcp https://modelmeter.xyz/mcpClaude Desktop
https://modelmeter.xyz/mcpWindsurf
{
"mcpServers": {
"modelmeter-mcp": {
"serverUrl": "https://modelmeter.xyz/mcp"
}
}
}Let your agent find its tools
Find servers like Modelmeter MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.
Other ai and machine learning servers
Do you run Modelmeter MCP?
Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.