Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
The changelog of record for the AI stack: sunset checks, deprecations, pricing, and model events.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://modelmeter.xyz/mcpRun this in your terminal
claude mcp add --transport http modelmeter https://modelmeter.xyz/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"modelmeter": {
"url": "https://modelmeter.xyz/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"modelmeter": {
"type": "http",
"url": "https://modelmeter.xyz/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://modelmeter.xyz/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain modelmeter.xyz (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Whisper
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
The changelog of record for the AI stack. Live at modelmeter.xyz.
A machine-readable, source-verified record of everything that changes in the model layer: deprecations with sunset dates and migration targets, silent model swaps behind stable IDs, price changes, releases — plus three years of pricing history and cost tooling. Every event carries its sources with verbatim quotes (most with archive snapshots), a verification status (unverified → human-reviewed verified), and corrections are never silent — a correction event points at what it supersedes.
Built primarily for AI agents to call programmatically, secondarily for humans through a dashboard. Reach it three ways: plain GET URLs returning JSON, a remote [MCP server](#mcp-server) any tool-calling agent can connect to, and a visual dashboard built on the same endpoints. The wedge: clean URLs, stable JSON contracts, an OpenAPI spec, and an llms.txt discoverability file. Most sites in this space are JS-heavy SPAs that agents can't use; Modelmeter is built the other way around.
GET /estimate?model=X&input=N&output=M — token cost for a hypothetical call, including upstream-markup comparison for reseller modelsGET /models — current model catalog, with filtersGET /model?id=X — unified card for one model: normalized pricing, capabilities (context window, vision, reasoning, tags), availability, reseller markup, and a price-history summary (launch vs. current price, % change, all-time low/high)GET /check?models=gpt-4o,claude-sonnet-4-6 — is my stack okay? Verdict per model: scheduled retirements with days-remaining and migration targets, past retirements, breaking changes, or a clean billGET /deprecations — per-model retirement rows: which model dies when, with runway and migration targetGET /feed.xml / GET /feed.json — RSS 2.0 / JSON Feed 1.1 of breaking and action-required eventsGET /events — the changelog of record: deprecations, price changes, launches and surrounding market events, each with severity (breaking | action_required | informational), announced_at/effective_at dates, sources with quotes, and verification status. Filters: provider, type, model, severity, since, until, statusGET /history — historical pricing time-series per model, with filtersGET /pricing.json — raw pricing snapshotGET /events.json — raw events snapshotGET /history.json — raw historical time-seriesSee public/openapi.yaml for the full spec.
Fail CI when a model your repo depends on is deprecated, sunsetting, or already retired:
- uses: modelmeters/modelmeter/actions/check@main
The action scans your repo for known model ids (catalog + every model named in a deprecation event, dashed and dotted spellings), calls /check, annotates the exact file:line of each affected model, writes a job-summary table with migration targets, and exits nonzero per your fail-on policy.
Modelmeter is also a remote MCP server, so any tool-calling agent (Claude, Hermes, …) can call it natively over the Streamable HTTP transport — no auth, no install:
https://modelmeter.xyz/mcp
Tools: check_model_dependencies, list_deprecations, estimate_cost, get_model, list_models, get_price_history, list_events. Start with list_models to discover ids, then get_model or estimate_cost. The MCP tools return the same data as the REST endpoints above — use whichever your runtime prefers.
pricing/ — current and historical model pricing across providersevents/ — the events record (schema 2.0.0): deprecations, price changes, releases, and market events with primary-source citations, verbatim quotes, and verification statusEach entry carries a last_verified date. Daily snapshots in pricing/snapshots/ accumulate the historical record. Wrong pricing is the existential risk — the schema requires explicit human verification before an entry is served.
Found a price change? Open a PR updating pricing/current.json with the new value, an updated last_verified date, and the source URL.
Spotted a meaningful AI market event? Add an entry to events/current.json with primary-source citations and verified: true.
Automation opens issues when provider pricing pages change. Pick one up if you want to help.
MIT — see LICENSE.