api.citestamp.com
https://api.citestamp.com/mcp
active Production-safe Score 94/100 http no auth
At a glance
| Endpoint | https://api.citestamp.com/mcp |
|---|---|
| Source | https://citestamp.com/ |
| Transport | http |
| Tools | 7 |
| Auth | none |
| First seen | 2026-11-11 12:58:40 |
| Last checked | 2026-11-17 21:46:23 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 390 / 671 ms |
| Last successful check | 2026-11-17 21:46:23 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (7)
what_supports— Edges recorded as SUPPORTING the given work or claim: human-signed support claims plus successful replication outcomes coded by the FORRT Rewhat_refutes— Edges recorded as REFUTING the given work or claim: human-signed refutations plus failed replication outcomes coded by the FORRT Replicationwhat_cites— Works 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 clareferences_of— What 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 waedges_about— Every edge touching the given work in either direction, each tagged asserted|inferred with attribution and provenance. Use when a user asksretraction_listing— Whether the Retraction Watch database lists the given DOI as retracted, from the dated export CiteStamp joins weekly. Use when a user asks wcheck_reference— Whether a reference resolves to a real work. Use when an answer is about to cite a paper. Give a DOI, arXiv id, PMID or reference as written
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:46:23 | ✓ | ✓ | 800 ms | 90 | active |
| 2026-11-17 21:31:17 | ✓ | ✓ | 446 ms | 90 | active |
| 2026-11-17 21:16:06 | ✓ | ✓ | 409 ms | 90 | active |
| 2026-11-17 21:00:58 | ✓ | ✓ | 424 ms | 90 | active |
| 2026-11-17 20:45:48 | ✓ | ✓ | 409 ms | 90 | active |
| 2026-11-17 20:30:46 | ✓ | ✓ | 808 ms | 90 | active |
| 2026-11-17 20:15:39 | ✓ | ✓ | 421 ms | 90 | active |
| 2026-11-17 19:59:34 | ✓ | ✓ | 634 ms | 90 | active |
| 2026-11-17 19:44:27 | ✓ | ✓ | 534 ms | 90 | active |
| 2026-11-17 19:29:23 | ✓ | ✓ | 492 ms | 90 | active |
| 2026-11-17 19:14:21 | ✓ | ✓ | 311 ms | 90 | active |
| 2026-11-17 18:58:36 | ✓ | ✓ | 326 ms | 90 | active |
| 2026-11-17 18:43:34 | ✓ | ✓ | 312 ms | 90 | active |
| 2026-11-17 18:28:33 | ✓ | ✓ | 397 ms | 90 | active |
| 2026-11-17 18:13:31 | ✓ | ✓ | 511 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://api.citestamp.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/api-citestamp-com-mcp # JSON