Skip to content

Modelmeter

by modelmeter.xyz · remote · no sign-in to list tools · v1.0.0 · published by xyz.modelmeter

The changelog of record for the AI stack: sunset checks, deprecations, pricing, and model events.

Changes · 2

7 tools: 2 change things and 5 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http modelmeter https://modelmeter.xyz/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

7 tools

Changes things 2Claude Code: ask
  • check_model_dependenciesIs my stack okay?No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • estimate_costEstimate the USD cost of an LLM API call for a given model and token counts.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 5Claude Code: allow
  • get_modelUnified card for one model in a single call: normalized pricing, capabilities (context window, vision, reasoning, tags), availability, reseller markup vs.No findings

    Why it is in this group

    • The name "get_model" says "get": a word for reading.
    Description, as the server wrote it
    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).
  • get_price_historyHistorical pricing time-series for a model or provider.No findings

    Why it is in this group

    • The name "get_price_history" says "get": a word for reading.
    Description, as the server wrote it
    Historical pricing time-series for a model or provider. Each point is a dated snapshot of the per-Mtok rates.
  • list_deprecationsPer-model retirement rows from the record: which model dies when, with runway and migration target.No findings

    Why it is in this group

    • The name "list_deprecations" says "list": a word for reading.
    Description, as the server wrote it
    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.
  • list_eventsThe changelog of record for the model layer: deprecations, price changes, launches, and the market events around them.No findings

    Why it is in this group

    • The name "list_events" says "list": a word for reading.
    Description, as the server wrote it
    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).
  • list_modelsList available models with their current pricing.No findings

    Why it is in this group

    • The name "list_models" says "list": a word for reading.
    Description, as the server wrote it
    List available models with their current pricing. Optionally filter by provider.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http modelmeter https://modelmeter.xyz/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__modelmeter__get_model",
      "mcp__modelmeter__list_models",
      "mcp__modelmeter__get_price_history",
      "mcp__modelmeter__list_events",
      "mcp__modelmeter__list_deprecations"
    ],
    "ask": [
      "mcp__modelmeter__estimate_cost",
      "mcp__modelmeter__check_model_dependencies"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as modelmeter. Review it before you use it.