MCP Server
Markdown (para LLMs)Añade verificación de citas académicas a Claude Desktop, Cursor o cualquier cliente MCP compatible.
Qué obtienes
Dos herramientas que envuelven la API REST de CiteTrue. Mismos créditos, misma precisión — solo vía MCP en lugar de HTTP.
| Herramienta | Propósito | Créditos / llamada |
|---|---|---|
| verify | Split a text blob into references and verify each against real sources. | 1 per ref; tricky ones up to 5 |
| get_credits | Devuelve el saldo de créditos de la cuenta. | 0 |
Inicio rápido
- Ir a Panel → Claves API y hacer clic en Nueva clave API. Copiar la clave que empieza con
sk_. - Abrir la configuración del cliente MCP (ver Configuración del cliente) y añadir el bloque citetrue.
- Reiniciar el cliente MCP — no solo el chat, la app entera.
- Pedir al asistente "Verifica estas citas: [pegar]". Llamará verify y resumirá.
Configuración del cliente
Cualquier cliente MCP por stdio sirve. A continuación los tres más comunes; otros usan la misma estructura.
Claude Desktop
Instala CiteTrue como extensión de Claude Desktop — sin editar JSON ni configurar Node. El servidor empaquetado se ejecuta con el Node que incluye Claude Desktop.
Descargar para Claude DesktopHaz doble clic en el archivo descargado (o arrástralo a Ajustes → Extensions) y pega tu clave API cuando se te solicite — se guarda de forma segura en el llavero de tu sistema.
Importante: tras instalar, asegúrate de que la extensión esté habilitada (activada) en Ajustes → Extensions y reinicia Claude Desktop — eso es lo que activa sus herramientas.
O configurar manualmente
Editar ~/Library/Application Support/Claude/claude_desktop_config.json en macOS, %APPDATA%\Claude\claude_desktop_config.json en Windows:
{
"mcpServers": {
"citetrue": {
"command": "npx",
"args": ["-y", "@citetrue/mcp-server"],
"env": {
"CITETRUE_API_KEY": "sk_..."
}
}
}
}Cursor
En Settings → MCP → Add new MCP server, usar la misma estructura command/args/env que el JSON de Claude Desktop abajo.
Windsurf, Zed, otros
Cualquier cliente MCP stdio funciona — sea cual sea la ruta de config, los tres mismos campos (command, args, env).
Configuración
| Variable de entorno | Predeterminado | Notas |
|---|---|---|
| CITETRUE_API_KEY | — (Requerido) | Token Bearer del dashboard. |
| CITETRUE_API_URL | https://api.citetrue.com | Sobrescribir para despliegues self-hosted. |
Herramientas
verify
Split a free-form text blob into individual references and verify each against real sources. Every reference goes through the same flow, and each one in the result reports what it cost.
Parámetros
Supply exactly one of text or taskHash:
textstring — raw text containing one or more references: numbered / bulleted / blank-line-separated lists, BibTeX, or prose with in-text author-year citations. Max 10MB.taskHashstring — resume a task started by an earlier call (thetaskHashit returned). Finished results are replayed without charging again; citations that still need checking are completed and billed as usual.forcebool, optional — ignore cached results and check the text again from scratch (billed like a new check). Only applies withtext.
Salida
{
"taskHash": "...",
"refs": [
{
"hash": "a1b2c3...",
"text": "[1] Vaswani, A., Shazeer, N., Parmar (2017)...",
"assessment": "authentic",
"value": {
"type": "citation",
"title": "Attention is all you need",
"authors": ["A Vaswani", "N Shazeer", "N Parmar"],
"year": 2017,
"url": "https://..."
},
"note": "",
"notices": [],
"confidence": 0.97,
"cost": 1
}
],
"cost": 2,
"balance": 248
}Each ref's cost is what the task has charged for that citation: 1 for most citations, up to 5 for tricky ones that needed more data sources and more analysis, 0 if it was already paid for in another task. Resuming a task with taskHash reports the same per-ref numbers again — they are not new charges. The top-level cost is what this call newly charged (0 when a finished task is simply replayed), and balance is what's left afterwards — it can be negative (see Billing). note is a free-form one-line natural-language explanation in English (intended for end-user display); for programmatic checks, match on notices[] instead.
Assessment values
authentic— paper exists and is the one cited;valuecontains the matched paper.unsure— found something but can't confirm;noticesandconfidencedescribe why.inauthentic— definitively not found / fabricated / unrelated.invalid— input wasn't a citation; pipeline refused to search.error— verification failed on this ref;errors[]lists tokens.exceeded— credits ran out before this ref ran.
Facturación
Same credits as the REST API. Most citations cost 1 credit. Tricky ones that need more data sources and more analysis can cost up to 5. If you run out of credits mid-check, citations already in progress still finish; the overage is deducted at your next credit reset, so balance can be negative. Citations that couldn't start for lack of credits come back as exceeded. get_credits is free.
Solución de problemas
If the server fails to start, ensure npx is on PATH and CITETRUE_API_KEY is set.
Mantenido por el equipo de CiteTrue · Última actualización: