_ registry / mcp streamable-http · checked 3m ago

citestamp

https://mcp.citestamp.com

Registry code: 99112a70298c7b68

api record

Call these when a question turns on a specific paper's citations, references, support, refutation or replication record, or when a reference is about to be cited and should be grounded first; identify the work by DOI, arXiv id or OpenAlex id. CiteStamp grounds citations against a typed, identity-resolved graph that hard-separates asserted (human-signed) from inferred (machine-derived) edges. Every result carries a tier, an attribution, and provenance. Most inferred edges are attributed openalex-snapshot: bulk citation metadata projected from OpenAlex, which publishes it at source. The rest…

endpoint
https://mcp.citestamp.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is citestamp live?
Yes — it answered the hub's last check (checked 3m ago). It answered 100% of checks over the last 30 days.
Is citestamp free to use?
Yes — the hub reached it with no key and no payment.
What tools does citestamp have?
7 tools: edges_about, references_of, check_reference, what_cites, what_refutes, what_supports, retraction_listing.
Is citestamp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.7%· all time 99.7%

latency
175ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 383 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • find works that cite a paper
  • list references of a paper
  • check if a paper was retracted
  • find supporting or refuting evidence for a paper
takes → gives
text → data
tools
6 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 7 tools
7 never probed 0 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • edges_about reads unknown 3m ago

    Every 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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "identifier"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 100,
          "maximum": 1000,
          "minimum": 1,
          "description": "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": {
          "type": "integer",
          "default": 0,
          "minimum": 0,
          "description": "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 than it consumed. Keep going while has_more is true."
        },
        "identifier": {
          "type": "string",
          "description": "DOI, arXiv id, OpenAlex id, or internal claim id"
        },
        "asserted_only": {
          "type": "boolean",
          "default": false,
          "description": "If true, restrict to human-signed (asserted) edges. If false (default), return both asserted and machine-inferred edges."
        }
      }
    }
    arguments 30 lines
  • references_of reads unknown 3m ago

    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 wants to check a reference before reusing it. Paged.

    mcp-tool

    {
      "type": "object",
      "required": [
        "identifier"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 100,
          "maximum": 1000,
          "minimum": 1,
          "description": "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": {
          "type": "integer",
          "default": 0,
          "minimum": 0,
          "description": "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 than it consumed. Keep going while has_more is true."
        },
        "identifier": {
          "type": "string",
          "description": "DOI, arXiv id, OpenAlex id, or internal claim id"
        },
        "asserted_only": {
          "type": "boolean",
          "default": false,
          "description": "If true, restrict to human-signed (asserted) edges. If false (default), return both asserted and machine-inferred edges."
        }
      }
    }
    arguments 30 lines
  • check_reference unknown 9h ago

    Whether 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 was never published.

    mcp-tool

    {
      "type": "object",
      "required": [
        "identifier"
      ],
      "properties": {
        "identifier": {
          "type": "string",
          "description": "The reference to check: a DOI (10.x/y, doi:10.x/y or a doi.org URL), an arXiv id, or the reference as written (a title or a full citation)"
        }
      }
    }
    arguments 12 lines
  • what_cites reads unknown 9h ago

    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 claimed 'cited by' is real. Returns edges with tier + attribution; paged.

    mcp-tool

    {
      "type": "object",
      "required": [
        "identifier"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 100,
          "maximum": 1000,
          "minimum": 1,
          "description": "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": {
          "type": "integer",
          "default": 0,
          "minimum": 0,
          "description": "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 than it consumed. Keep going while has_more is true."
        },
        "identifier": {
          "type": "string",
          "description": "DOI, arXiv id, OpenAlex id, or internal claim id"
        },
        "asserted_only": {
          "type": "boolean",
          "default": false,
          "description": "If true, restrict to human-signed (asserted) edges. If false (default), return both asserted and machine-inferred edges."
        }
      }
    }
    arguments 30 lines
  • what_refutes reads unknown 9h ago

    Edges 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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "identifier"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 100,
          "maximum": 1000,
          "minimum": 1,
          "description": "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": {
          "type": "integer",
          "default": 0,
          "minimum": 0,
          "description": "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 than it consumed. Keep going while has_more is true."
        },
        "identifier": {
          "type": "string",
          "description": "DOI, arXiv id, OpenAlex id, or internal claim id"
        },
        "asserted_only": {
          "type": "boolean",
          "default": false,
          "description": "If true, restrict to human-signed (asserted) edges. If false (default), return both asserted and machine-inferred edges."
        }
      }
    }
    arguments 30 lines
  • what_supports reads unknown 3m ago

    Edges 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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "identifier"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 100,
          "maximum": 1000,
          "minimum": 1,
          "description": "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": {
          "type": "integer",
          "default": 0,
          "minimum": 0,
          "description": "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 than it consumed. Keep going while has_more is true."
        },
        "identifier": {
          "type": "string",
          "description": "DOI, arXiv id, OpenAlex id, or internal claim id"
        },
        "asserted_only": {
          "type": "boolean",
          "default": false,
          "description": "If true, restrict to human-signed (asserted) edges. If false (default), return both asserted and machine-inferred edges."
        }
      }
    }
    arguments 30 lines
  • retraction_listing reads unknown 17h ago

    Whether 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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "identifier"
      ],
      "properties": {
        "identifier": {
          "type": "string",
          "description": "DOI in any common form (10.x/y, doi:10.x/y or a doi.org URL)"
        }
      }
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 99112a70298c7b68.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/99112a70298c7b68/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/99112a70298c7b68/badge.svg)](https://brick.blue/agent/99112a70298c7b68?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.