Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Checks whether each cited source supports the claim it backs. Blinded human-first, local-first.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"citevahti": {
"command": "uvx",
"args": [
"citevahti"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add citevahti -- uvx citevahtiPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"citevahti": {
"command": "uvx",
"args": [
"citevahti"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"citevahti": {
"type": "stdio",
"command": "uvx",
"args": [
"citevahti"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 9 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub heidihelena, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.46.0) llegó al registro hace 3 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Python (uv) en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, alalanet — check before you pay
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
Check packages, MCP servers and x402 endpoints before agents install or pay. Signed.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Does the cited paper actually support the claim? Check every citation in your manuscript — before a reviewer does.
CiteVahti walks you through your manuscript one claim at a time. You decide whether each cited source really backs the sentence; an optional AI gives a *blinded* second opinion (you rate first, it can never overrule you); and every decision is saved as a timestamped, tamper-evident record on your own computer.
Free while in beta. CiteVahti is local-first: your manuscript stays on your device
unless *you* choose to turn on an external AI model. No account. Nothing uploaded.
What beta means here: the review workflow and your data format are stable, but the
tool is young and your feedback still shapes it. The app does not update itself yet —
when a new version ships you replace it yourself (steps under *Updating*, below; the
panel can check for a newer version, but only if you turn that on). If something is
confusing or judged wrong, say so — beta reports are how it improves.
Researchers, clinicians, and students who write papers and want to be sure every citation holds up — without learning new software or touching a command line. If you can open a file on your computer, you can use CiteVahti.
What it does for you
On a Mac, use the desktop app. It's a normal app: download it, open it, review.
.docx or .md) onto the window. The panel walks you through the rest, one step at a time — there's nothing to memorise.Want an AI assistant to help pre-screen citations? Whenever you're ready, click the CiteVahti menu-bar icon → Start Agent Server. CiteVahti first explains exactly what an assistant can and cannot do — and either way, you rate every claim yourself and make every final call.
If you already work in Claude, install CiteVahti as a one-click extension and drive the review by chatting. *(This is also the path on Windows and Linux, where the desktop app isn't available yet.)*
citevahti- -macos-arm64.mcpb *(signed + notarized)*citevahti- -windows-x64.mcpbcitevahti- -linux-x64.mcpbFirst time on macOS you may see a one-time security prompt — the extension is a zip,
which macOS can't pre-stamp even though the app inside is signed and notarized. If it
appears: right-click the file → Open, or go to **System Settings → Privacy & Security →
"Open Anyway"**. After that it installs and runs normally.
First time on Windows you may see a SmartScreen warning ("Windows protected your PC")
— the Windows build is unsigned, so Windows can't check who published it. If it appears:
click More info, then Run anyway. After that it installs and runs normally.
Updating — your review data is never touched; only the program is replaced
CiteVahti.app, download the newest citevahti- -macos-arm64.app.zip from the latest release, and replace the old CiteVahti.app in Applications with it. Your reviews live in the project folder you chose, not inside the app, so nothing is lost..mcpb from the latest release. Ask your assistant to run the `status` tool to confirm the running version. *(macOS Intel: install via pip install "citevahti[mcp]", or run the Apple-Silicon .mcpb under Rosetta.)*pip install --no-cache-dir --upgrade "citevahti[mcp]", then pip show citevahti to confirm the version.For developers & technical readers — pip, CLI, architecture, security
Everything below assumes a terminal; none of it is needed to use the app.
Try it on synthetic data (nothing of yours touched — builds an invented ledger and opens the panel showing every claim state):
pip install "citevahti[mcp]"
citevahti demo
Run the review panel from the terminal:
pip install "citevahti[mcp]"
citevahti run
CiteVahti opens the review panel on your machine at 127.0.0.1 and tells you the one next thing to do.
Run the desktop app from source (the same supervised shell as the packaged .app):
pip install "citevahti[app]"
citevahti-app
What the app actually runs: CiteVahti.app is a thin shell supervising two local processes — the review panel engine (for you) and an optional MCP agent server (for a chat client; it can suggest and stage, but it can never rate for you, see your rating first, or make the final call). Both bind only to 127.0.0.1, write rotating logs (menu-bar icon → *Open Logs Folder*), exit on their own if the app dies, and shut down cleanly when you quit. The agent server is off until you enable it and can be stopped anytime from the menu bar.
Deeper reading:
CiteVahti always tells you the one next thing to do — there's no command to remember and nothing to set up.
You start by adding your manuscript — choose a Word or Markdown file, drag it onto the window, or paste the text. Nothing is uploaded.
Then you work through each claim on a simple card that walks a visible Rate → Reveal → Decide → Write path, so you always know where you are:
Every decision is saved to a timestamped, tamper-evident review record — a plain-language log of what you reviewed and in what order. Export it as a Word document, a print-ready report, or a review-packet .zip (which even includes an auto-filled methods paragraph with your review's real numbers) for a methods section, a co-author, a supervisor, or a journal.
Stop losing evidence work after each project. Most citation checks vanish after one manuscript or one deadline. Every claim you assess in CiteVahti is saved to your own private evidence map, so next time you work on the same topic you don't start from zero — pull back earlier judgments, see what you already checked, and spot where the literature is thin, contradictory, or overclaimed.
It stays on your machine. Sharing into the wider, de-identified community evidence map is a separate, opt-in step, and you preview the exact payload before anything is sent — never your manuscript, search history, patient data, registry data, or private project identifiers.
You always rate first. CiteVahti can then show a second rating from an AI, and compare the two — but the AI value stays hidden until your rating is in, and the final decision is always yours. There's no hidden AI subscription: pick the mode you want, or leave AI off entirely.
You can get the second opinion from:
Run the AI on your own machine (free, nothing leaves your device)
brew install ollama).qwen2.5 is recommended for claim checking: ollama pull qwen2.5
(Pick a smaller tag if your machine is tight on memory, e.g. ollama pull qwen2.5:3b.)
To update later, re-pull the same name (ollama pull qwen2.5).
CiteVahti is local-first. Full policy: [https://vahtian.com/citevahti/privacy](https://vahtian.com/citevahti/privacy) (source: [docs/PRIVACY.md](https://github.com/heidihelena/citevahti/blob/main/docs/PRIVACY
Solo se muestra el principio; lee el resto en el repo