CiteStamp
REMOTE · MCP.CITESTAMP.COM · SCANNED SEP 24
Citation-health over a CC0 citation graph: what supports, refutes, or cites a paper. Read-only.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1234 tokens (~246/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the CiteStamp MCP server?
CiteStamp is a hosted endpoint at https://mcp.citestamp.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.citestamp.com
claude mcp add --transport http com-citestamp-citestamp 'https://mcp.citestamp.com/mcp'
{
"mcpServers": {
"com-citestamp-citestamp": {
"url": "https://mcp.citestamp.com/mcp"
}
}
} {
"servers": {
"com-citestamp-citestamp": {
"type": "http",
"url": "https://mcp.citestamp.com/mcp"
}
}
} [mcp_servers.com-citestamp-citestamp] url = "https://mcp.citestamp.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-citestamp-citestamp": {
"type": "remote",
"url": "https://mcp.citestamp.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-citestamp-citestamp --url 'https://mcp.citestamp.com/mcp' --transport streamable-http
mcp_servers:
com-citestamp-citestamp:
url: "https://mcp.citestamp.com/mcp" {
"McpServers": {
"com-citestamp-citestamp": {
"Transport": "http",
"Url": "https://mcp.citestamp.com/mcp"
}
}
} assistant mcp add com-citestamp-citestamp -t streamable-http -u 'https://mcp.citestamp.com/mcp'
{
"mcpServers": {
"com-citestamp-citestamp": {
"type": "http",
"url": "https://mcp.citestamp.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Aug 26 +6
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.1.0 → 1.1.0 functional
- Tool “edges_about” changed its title: Edges about cosmetic
- Tool “references_of” changed its title: References of cosmetic
- Tool “what_cites” changed its title: What cites cosmetic
- Tool “what_refutes” changed its title: What refutes cosmetic
- Tool “what_supports” changed its title: What supports cosmetic
- 26 Aug 26 72
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 20 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- “edges_about” added an optional parameter “limit” cosmetic
- “edges_about” added an optional parameter “offset” cosmetic
- “references_of” added an optional parameter “limit” cosmetic
- “references_of” added an optional parameter “offset” cosmetic
- “what_cites” added an optional parameter “limit” cosmetic
- “what_cites” added an optional parameter “offset” cosmetic
- “what_refutes” added an optional parameter “limit” cosmetic
- “what_refutes” added an optional parameter “offset” cosmetic
- “what_supports” added an optional parameter “limit” cosmetic
- “what_supports” added an optional parameter “offset” cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://mcp.citestamp.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=citestamp.com | CN=WE1,O=Google Trust Services,C=US | 8 Aug 2026 | 6 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 7bd34d93dbbacd171344e90d56d4c5dc |
| SANs: citestamp.com, mcp.citestamp.com, *.mcp.citestamp.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.citestamp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| citestamp.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.citestamp.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.citestamp.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
edges_about Edges about ~206
Every edge touching the given work or claim, in either direction, each tagged with its trust tier (asserted|inferred) and attribution/provenance.
| Name | Type | Req | Description |
|---|---|---|---|
| asserted_only | boolean | – | If true, restrict to human-signed (asserted) edges. If false (default), return both asserted and machine-inferred edges. |
| identifier | string | yes | DOI, arXiv id, OpenAlex id, or internal claim id |
| limit | integer | – | Maximum edges to return per tier (default 100, max 1000). Well-cited works have thousands; the response reports has_more and inferred_total so you can tell a page from the whole answer. |
| offset | integer | – | How many edges to skip, for paging. Advance by the LIMIT you asked for, not by the number of results you got back — duplicates are removed after the window is taken, so a page can return fewer rows t… |
No output schema declared.
No examples provided.
references_of References of ~185
What the given work CITES (its outgoing references).
| Name | Type | Req | Description |
|---|---|---|---|
| asserted_only | boolean | – | If true, restrict to human-signed (asserted) edges. If false (default), return both asserted and machine-inferred edges. |
| identifier | string | yes | DOI, arXiv id, OpenAlex id, or internal claim id |
| limit | integer | – | Maximum edges to return per tier (default 100, max 1000). Well-cited works have thousands; the response reports has_more and inferred_total so you can tell a page from the whole answer. |
| offset | integer | – | How many edges to skip, for paging. Advance by the LIMIT you asked for, not by the number of results you got back — duplicates are removed after the window is taken, so a page can return fewer rows t… |
No output schema declared.
No examples provided.
what_cites What cites ~188
Works or claims that CITE the given identifier (incoming citations).
| Name | Type | Req | Description |
|---|---|---|---|
| asserted_only | boolean | – | If true, restrict to human-signed (asserted) edges. If false (default), return both asserted and machine-inferred edges. |
| identifier | string | yes | DOI, arXiv id, OpenAlex id, or internal claim id |
| limit | integer | – | Maximum edges to return per tier (default 100, max 1000). Well-cited works have thousands; the response reports has_more and inferred_total so you can tell a page from the whole answer. |
| offset | integer | – | How many edges to skip, for paging. Advance by the LIMIT you asked for, not by the number of results you got back — duplicates are removed after the window is taken, so a page can return fewer rows t… |
No output schema declared.
No examples provided.
what_refutes What refutes ~190
Edges asserting or indicating that something REFUTES the given work or claim.
| Name | Type | Req | Description |
|---|---|---|---|
| asserted_only | boolean | – | If true, restrict to human-signed (asserted) edges. If false (default), return both asserted and machine-inferred edges. |
| identifier | string | yes | DOI, arXiv id, OpenAlex id, or internal claim id |
| limit | integer | – | Maximum edges to return per tier (default 100, max 1000). Well-cited works have thousands; the response reports has_more and inferred_total so you can tell a page from the whole answer. |
| offset | integer | – | How many edges to skip, for paging. Advance by the LIMIT you asked for, not by the number of results you got back — duplicates are removed after the window is taken, so a page can return fewer rows t… |
No output schema declared.
No examples provided.
what_supports What supports ~190
Edges asserting or indicating that something SUPPORTS the given work or claim.
| Name | Type | Req | Description |
|---|---|---|---|
| asserted_only | boolean | – | If true, restrict to human-signed (asserted) edges. If false (default), return both asserted and machine-inferred edges. |
| identifier | string | yes | DOI, arXiv id, OpenAlex id, or internal claim id |
| limit | integer | – | Maximum edges to return per tier (default 100, max 1000). Well-cited works have thousands; the response reports has_more and inferred_total so you can tell a page from the whole answer. |
| offset | integer | – | How many edges to skip, for paging. Advance by the LIMIT you asked for, not by the number of results you got back — duplicates are removed after the window is taken, so a page can return fewer rows t… |
No output schema declared.
No examples provided.
What is the CiteStamp MCP server?
CiteStamp is an MCP server listed in the public MCP registry as com.citestamp/citestamp. Citation-health over a CC0 citation graph: what supports, refutes, or cites a paper. Read-only. This page covers its hosted endpoint (https://mcp.citestamp.com/mcp).
Is the CiteStamp MCP server safe to use?
CiteStamp scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CiteStamp MCP server expose?
CiteStamp exposes 5 tools: what_supports, what_refutes, what_cites, references_of, edges_about. Their descriptions and schemas cost roughly 959 tokens of context every time the server is loaded.
Does the CiteStamp MCP server require authentication?
No. We connected to CiteStamp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CiteStamp MCP server still maintained?
CiteStamp is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.