Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Live registry of AI model specs, context windows, and per-token pricing.
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://modelright.dev/api/mcpRun this in your terminal
claude mcp add --transport http modelright https://modelright.dev/api/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"modelright": {
"url": "https://modelright.dev/api/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": {
"modelright": {
"type": "http",
"url": "https://modelright.dev/api/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://modelright.dev/api/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 modelright.dev (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 (0.1.0) reached the registry 30 days 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, AI Deprecations
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.
AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.
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.
Live registry of AI model specs, context windows, and per-1M-token pricing — running at [modelright.dev](https://modelright.dev).
A Next.js + Postgres app that keeps a real, current catalog of LLMs: the OpenRouter catalog is synced hourly, Artificial Analysis enriches models with benchmark and speed data, and every price change lands in an append-only snapshot log that powers the changes feed and price-history charts.
/models searchable/filterable by provider, status, price ceiling, context floor, modality, and free-tier; /providers directory/models/[provider]/[slug])/compare); SEO-friendly pair pages at /compare/a-vs-b/pick and /pick/{chat,coding,long-context,vision,cheap-bulk} rank models by an explicit rule written on the page/changes lists recent price/status changes and model additions/removals, with an RSS feedGET /api/v1/models (same filters as the UI), /api/v1/models/{provider}/{slug}, /api/v1/providers, /api/v1/changes; OpenAPI at /openapi.json/api/mcp (also /.well-known/mcp) with six read tools (search_models, get_model, list_providers, compare_models, get_changes, get_ingest_status)/llms.txt, /agents.txt, A2A agent card (/.well-known/agent-card.json), Smithery server card (/.well-known/mcp/server-card.json), server.json MCP-registry listing/api/bot-hit), and MCP call logging, all rendered on a token-gated /admin + /admin/analyticsPOST /api/ingest (Bearer token, zod-validated, idempotent upsert) and POST /api/cron/sync (hourly OpenRouter + AA sync, marks removed models rather than deleting)postgres driver) — migrations in drizzle/src/lib + src/app/apinpm install
cp .env.example .env # set DATABASE_URL npm run db:migrate npm run db:seed # optional fixture data so pages render pre-ingest npm run dev # http://localhost:3000
| Script | Purpose |
|---|---|
npm run dev / build / start | Next.js lifecycle |
npm run typecheck | tsc --noEmit |
npm run test | Vitest with coverage |
npm run db:generate / db:migrate / db:seed | Drizzle schema lifecycle + fixtures |
See .env.example. Highlights: DATABASE_URL (required), INGEST_TOKEN + CRON_SECRET (write-path auth), AA_API_KEY (Artificial Analysis enrichment), ADMIN_TOKEN (gates /admin), ANALYTICS_SALT (daily visitor-hash salt — rotate to reset identities).
This repo is maintained by a LiveGraph improvement loop: queued items in QUEUE.md are picked up, implemented, tested, and merged by agents. PLAN.md holds the product roadmap, docs/loop-reports/ is the per-item delivery log, and GROWTH.md/growth/assets/ hold the distribution plan and media kit (including a walkthrough video). If you're evaluating agent-driven development, the queue history and loop reports are the interesting part.
MIT — see LICENSE.