MCP server de CiteStamp
Commit 10 nov 2026Verifica referencias académicas e identifica citas que respaldan, refutan o han sido retractadas utilizando registros públicos y un grafo de citas CC0.
También conocido como citestamp/mcp, mcp
- Stars
- 0
- Herramientas
- 3
- Descargas, 30 días
- —
- Última versión
- 1.3.1
- Último commit
- 10 nov 2026
- Licencia
- MIT
¿Qué es CiteStamp MCP?
Verifica referencias académicas e identifica citas que respaldan, refutan o han sido retractadas utilizando registros públicos y un grafo de citas CC0. Expone 3 herramientas, como edges_about, retraction_listing, check_reference.
Resumen generado a partir del README del proyecto
Acerca del MCP server de CiteStamp
CiteStamp ofrece un MCP server remoto que permite a investigadores y desarrolladores verificar la validez de las citas académicas. Al conectarse al endpoint alojado mediante streamable-http, los usuarios pueden prevenir alucinaciones de la IA comprobando si las referencias corresponden a trabajos reales o si han sido retractadas. El servidor accede a un grafo de citas CC0 y cruza los datos con registros públicos como Crossref, DataCite, OpenAlex y PubMed.
Esta herramienta está diseñada para usarse con varios clientes de IA, incluyendo Claude, Cursor, Gemini y Cline. Funciona sin autenticación obligatoria, ofreciendo un nivel anónimo limitado a 10 solicitudes por minuto por IP. Los usuarios pueden aumentar este límite a 60 o 600 solicitudes por minuto proporcionando una API key opcional (gratuita o Pro) mediante un encabezado de autorización. El sistema distingue entre accountable edges firmados por identidades humanas con ORCID e inferred edges generados por máquinas, lo que permite a los agentes filtrar por niveles específicos de confiabilidad de datos.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar CiteStamp MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar CiteStamp MCP en Claude Code
$ claude mcp add --transport http mcp https://mcp.citestamp.com/mcpInstalar CiteStamp MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.citestamp.com/mcp"
}
}
}Instalar CiteStamp MCP en VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "http",
"url": "https://mcp.citestamp.com/mcp"
}
}
}Instalar CiteStamp MCP en VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"http","url":"https://mcp.citestamp.com/mcp"}'Instalar CiteStamp MCP en Codex
$ codex mcp add mcp --url https://mcp.citestamp.com/mcpInstalar CiteStamp MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] url = "https://mcp.citestamp.com/mcp"
Instalar CiteStamp MCP en Gemini CLI
$ gemini mcp add -s user --transport http mcp https://mcp.citestamp.com/mcpInstalar CiteStamp MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.citestamp.com/mcp",
"type": "http"
}
}
}Herramientas de CiteStamp MCP 3
Detectado desde el READMEedges_aboutretraction_listingcheck_reference
| edges_about | — | |
| retraction_listing | — | |
| check_reference | — |
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Aún no verificado. Un servidor necesita una puntuación de 80, ningún hallazgo grave y suficientes datos para que podamos revisarlo. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesiblecitestamp/mcp is public and reachablegithub.com/citestamp/mcp ↗Aprobado
- El paquete indica este repositorio como su origenNo verificado
- Procedencia de la compilación (atestación de Sigstore)No verificado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-11-10github.com/citestamp/mcp ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo verificado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
- Sin instrucciones ocultas para el modelo3 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo tool named like delete, drop or execAprobado
- El endpoint remoto responde al handshake de MCPinitialize answered with protocol 2025-06-18 in 794 msAprobado
README
Ver en GitHubCiteStamp MCP server
Ground citations before your agent emits them.
CiteStamp is a free citation-health tool for researchers: it checks references against the public scholarly registries (Crossref, DataCite, OpenAlex) and flags the ones that do not resolve to a known work or that a publisher has marked retracted, the hallucinated-citation failure mode LLM users keep hitting.
This repo is the install guide for the hosted MCP server over CiteStamp's CC0 citation graph. There is nothing to build or run locally; the server is remote.
| Endpoint | https://mcp.citestamp.com/mcp |
| Transport | streamable-http |
| Protocol | 2025-06-18 |
| Auth | None. Anonymous at 10 requests/min per IP. An optional free key (email info@citestamp.com) raises that to 60/min; Pro to 600/min |
| Data | CC0 citation graph; human-signed and machine-inferred claims kept strictly apart |
The tools (all read-only)
what_supports/what_refutes: typed edges bearing on a claimwhat_cites/references_of: the citing and cited works around a referenceedges_about: edges on a topicretraction_listing: whether the Retraction Watch database lists a DOI as retracted, from the dated export CiteStamp joins weekly. Not listed means not in that export; it does not check the publisher recordcheck_reference: whether a reference resolves to a real work, before an answer cites it. Give a DOI, an arXiv id, a PubMed ID or the reference as written. It reads Crossref, DataCite and doi.org (which answers for every DOI agency), and PubMed for a PubMed ID given without a DOI, and says found, confirm (with the reason), not found in the named sources on a date, or couldn't check. A PubMed ID that leads to no record, or to another paper, is a confirm: only a DOI that no agency registered can be not found. A not-found is not proof that a work was never published
Every result carries its tier: accountable edges are signed by a human identity (ORCID); inferred edges are machine-derived. Your agent can ask for signed-only.
Add it to your client
No key is needed. Every snippet below works as written.
Gemini CLI (extension)
gemini extensions install https://github.com/citestamp/mcp
Or add the server by hand in ~/.gemini/settings.json:
{ "mcpServers": { "citestamp": { "httpUrl": "https://mcp.citestamp.com/mcp" } } }
Gemini Spark (custom app)
In the Gemini web app: Settings & help → Connected Apps → under "Custom apps for Spark"
click Add a custom app → enter https://mcp.citestamp.com/mcp → Next. Type @ in a
prompt and pick CiteStamp to make Gemini use it. Custom apps need access to Gemini Spark
on a personal Google Account with Keep Activity on.
Claude (claude.ai / Desktop)
Settings → Connectors → Add custom connector → URL https://mcp.citestamp.com/mcp.
Leave authentication empty.
Claude Code
claude mcp add --transport http citestamp https://mcp.citestamp.com/mcp
Cursor (~/.cursor/mcp.json)
{ "mcpServers": { "citestamp": { "url": "https://mcp.citestamp.com/mcp" } } }
Cline (MCP settings)
{ "mcpServers": { "citestamp": {
"type": "streamableHttp",
"url": "https://mcp.citestamp.com/mcp" } } }
VS Code (.vscode/mcp.json)
{ "servers": { "citestamp": {
"type": "http",
"url": "https://mcp.citestamp.com/mcp" } } }
If a snippet drifts from your client's current config schema, your client's MCP docs win; the endpoint is the stable part.
Optional: raise the rate limit
A key is never required. If you hold one, send it as a header on the same endpoint:
Authorization: Bearer <your key>
For Claude Code that is --header "Authorization: Bearer <your key>"; for the JSON
configs, add "headers": { "Authorization": "Bearer <your key>" } to the server entry.
A bad key is a loud 401, never a silent downgrade to anonymous, so add the header only
once you have a key.
What this is not
CiteStamp reports what public registries say at a dated point in time. It does not
judge the truth or quality of any work. check_reference answers found, confirm (with
the reason), not found in the named sources on a date, or couldn't check; a not-found
is not proof a work was never published. retraction_listing says whether the dated
Retraction Watch export lists a DOI, and does not check the publisher record.
Statements about works, never about people.
Links
- Integration guide + REST API: https://citestamp.com/for-ai
- Check a bibliography in the browser (free, nothing uploaded): https://citestamp.com/check
- Reference-health badge for any DOI: https://citestamp.com/citestamped/
- Privacy: https://citestamp.com/privacy · Contact: info@citestamp.com
CiteStamp is built by 3Rivers Enterprises LLC, Fort Wayne, Indiana.
Preguntas sobre CiteStamp MCP
¿Cómo agrego CiteStamp MCP a Claude Code?
Ejecuta claude mcp add --transport http mcp https://mcp.citestamp.com/mcp en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego CiteStamp MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Qué herramientas proporciona CiteStamp MCP?
Expone 3 herramientas, incluidas edges_about, retraction_listing, check_reference.
¿Cuál es la diferencia entre accountable edges e inferred edges?
Los accountable edges están firmados por una identidad humana a través de ORCID, mientras que los inferred edges son derivados por máquinas.