Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Check that a reference resolves; see what supports, refutes or cites a paper. CC0 graph, read-only.
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://mcp.citestamp.com/mcpRun this in your terminal
claude mcp add --transport http citestamp https://mcp.citestamp.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"citestamp": {
"url": "https://mcp.citestamp.com/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": {
"citestamp": {
"type": "http",
"url": "https://mcp.citestamp.com/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://mcp.citestamp.com/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.
Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.
what_supportsEdges recorded as SUPPORTING the given work or claim: human-signed support claims plus successful replication outcomes coded by the FORRT Replication Database. Use when a user asks whether a finding held up or was replicated.
what_refutesEdges recorded as REFUTING the given work or claim: human-signed refutations plus failed replication outcomes coded by the FORRT Replication Database. Use when a user asks whether a finding failed to replicate or has been contradicted.
what_citesWorks that CITE the given DOI (incoming citations). Use when a user asks who cites a paper, how much a work has been cited, or whether a claimed 'cited by' is real. Returns edges with tier + attribution; paged.
references_ofWhat the given work CITES (its reference list). Use when a user asks what a paper relies on, whether a specific citation in it exists, or wants to check a reference before reusing it. Paged.
edges_aboutEvery edge touching the given work in either direction, each tagged asserted|inferred with attribution and provenance. Use when a user asks 'what is known about this paper's citations' or wants the whole neighbourhood in one call. Paged.
retraction_listingWhether the Retraction Watch database lists the given DOI as retracted, from the dated export CiteStamp joins weekly. Use when a user asks whether a paper has been retracted or carries a retraction notice. Not listed means not in that export; the publisher record is not checked.
check_referenceWhether a reference resolves to a real work. Use when an answer is about to cite a paper. Give a DOI, an arXiv id or the reference as written. 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 wa
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 7, 2026
The registry name was verified against the domain citestamp.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 384 ms (HTTP 200)
No sign-in needed
Read 7 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 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.3.1) reached the registry 12 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, ScienceShot science reference
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.
Sourced, citable answers in radiation and particle physics, photonics, electronics and quantum.
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.
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 |
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 or the reference as written. It reads Crossref, DataCite and doi.org (which answers for every DOI agency) and says found, confirm (with the reason), not found in the named sources on a date, or couldn't check. A not-found is not proof that a work was never publishedEvery 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.
No key is needed. Every snippet below works as written.
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" } } }
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.
Settings → Connectors → Add custom connector → URL https://mcp.citestamp.com/mcp. Leave authentication empty.
claude mcp add --transport http citestamp https://mcp.citestamp.com/mcp
~/.cursor/mcp.json){ "mcpServers": { "citestamp": { "url": "https://mcp.citestamp.com/mcp" } } }
{ "mcpServers": { "citestamp": {
"type": "streamableHttp", "url": "https://mcp.citestamp.com/mcp" } } }
.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.
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 "; for the JSON configs, add "headers": { "Authorization": "Bearer " } 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.
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.
CiteStamp is built by 3Rivers Enterprises LLC, Fort Wayne, Indiana.