_ registry / mcp streamable-http · checked 1h ago

scholar-sidekick-app

https://scholar-sidekick.com

Registry code: 3e3a2d8423d661d1

api record

Scholar Sidekick turns scholarly identifiers (DOI, PMID, PMCID, ISBN, ISSN, arXiv, ADS bibcode, WHO IRIS URL) into citation trust signals with an interactive citation card. Use audit_citations to check a WHOLE reference list in one call — always prefer it over repeating verify_citation, which is for a single citation; verify_citation to check whether one claimed citation matches the real record at its identifier (catches the real-DOI + fabricated-title pattern); format_citation to resolve one to five identifiers into a formatted reference in any of 10,000+ styles; check_retraction to see…

endpoint
https://scholar-sidekick.com/api/apps/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 scholar-sidekick-app live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is scholar-sidekick-app free to use?
Yes — the hub reached it with no key and no payment.
What tools does scholar-sidekick-app have?
4 tools: verify_citation, audit_citations, format_citation, check_retraction.
Is scholar-sidekick-app 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 100%· all time 100%

latency
237ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 288 checks · signed record
  • degraded → live
_ what it is for
topic
knowledge & reference academic & research
used for
  • audit a list of citations
  • check if a work is retracted
  • format scholarly citations
  • verify a single citation
takes → gives
data → data
tools
4 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 4 tools
4 never probed 0 of 4 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.

  • verify_citation reads unknown 1h ago

    Check whether a claimed citation matches the real record at its identifier — catches the real-DOI + fabricated-title pattern (Topaz et al. 2026). Returns a verdict: matched, mismatch, not_found, or ambiguous.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "title"
  ],
  "properties": {
    "ads": {
      "type": "string",
      "maxLength": 50
    },
    "doi": {
      "type": "string",
      "maxLength": 200
    },
    "isbn": {
      "type": "string",
      "maxLength": 50
    },
    "issn": {
      "type": "string",
      "maxLength": 50
    },
    "pmid": {
      "type": "string",
      "maxLength": 50
    },
    "year": {
      "type": "integer",
      "maximum": 9999,
      "minimum": 0,
      "description": "Claimed publication year."
    },
    "arxiv": {
      "type": "string",
      "maxLength": 50
    },
    "pmcid": {
      "type": "string",
      "maxLength": 50
    },
    "title": {
      "type": "string",
      "maxLength": 2000,
      "minLength": 1,
      "description": "The claimed title of the work."
    },
    "authors": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "family"
        ],
        "properties": {
          "given": {
            "type": "string",
            "maxLength": 200
          },
          "family": {
            "type": "string",
            "maxLength": 200,
            "minLength": 1
          }
        }
      },
      "maxItems": 50,
      "description": "Claimed authors (family/given)."
    },
    "container": {
      "type": "string",
      "maxLength": 500,
      "description": "Claimed journal / container title."
    },
    "whoIrisUrl": {
      "type": "string",
      "maxLength": 2000
    },
    "semanticTitle": {
      "type": "boolean",
      "description": "Also run the semantic title check: a calibrated model judgment of whether the claimed title and the resolved title describe the same work. Catches one-word swaps in long titles that string similarity misses. A flagged title moves matched → ambiguous (review), never mismatch. Not byte-deterministic. Default false."
    }
  }
}
    arguments 84 lines
  • audit_citations reads unknown 8h ago

    Check a WHOLE reference list in one call — the batch counterpart to verify_citation. Use this whenever there is more than one citation to check (a pasted bibliography, a reference list, "are these references real?"): parse the list into one object per citation and send them together, rather than calling verify_citation repeatedly. Each entry gets the same fabrication check (a real, resolvable identifier paired with a title that does NOT match the resolved paper; Topaz et al., Lancet 2026) plus an optional retraction lookup. Audits up to 25 entries per call and reports any excess as truncated. Returns a per-entry verdict table and totals.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "citations"
  ],
  "properties": {
    "citations": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "title"
        ],
        "properties": {
          "ads": {
            "type": "string",
            "maxLength": 50
          },
          "doi": {
            "type": "string",
            "maxLength": 200
          },
          "isbn": {
            "type": "string",
            "maxLength": 50
          },
          "issn": {
            "type": "string",
            "maxLength": 50
          },
          "pmid": {
            "type": "string",
            "maxLength": 50
          },
          "year": {
            "type": "integer",
            "maximum": 9999,
            "minimum": 0,
            "description": "Claimed publication year."
          },
          "arxiv": {
            "type": "string",
            "maxLength": 50
          },
          "pmcid": {
            "type": "string",
            "maxLength": 50
          },
          "title": {
            "type": "string",
            "maxLength": 2000,
            "minLength": 1,
            "description": "The claimed title of the work."
          },
          "authors": {
            "type": "array",
            "items": {
              "type": "object",
              "required": [
                "family"
              ],
              "properties": {
                "given": {
                  "type": "string",
                  "maxLength": 200
                },
                "family": {
                  "type": "string",
                  "maxLength": 200,
                  "minLength": 1
                }
              }
            },
            "maxItems": 50,
            "description": "Claimed authors (family/given)."
          },
          "container": {
            "type": "string",
            "maxLength": 500,
            "description": "Claimed journal / container title."
          },
          "whoIrisUrl": {
            "type": "string",
            "maxLength": 2000
          }
        }
      },
      "maxItems": 100,
      "minItems": 1,
      "description": "The reference list to check, one object per citation (same fields as verify_citation). Up to 25 are audited per call; any beyond that are reported as truncated."
    },
    "semanticTitle": {
      "type": "boolean",
      "description": "Also run the semantic title check: a calibrated model judgment of whether the claimed title and the resolved title describe the same work. Catches one-word swaps in long titles that string similarity misses. A flagged title moves matched → ambiguous (review), never mismatch. Not byte-deterministic. Default false."
    },
    "checkRetractions": {
      "type": "boolean",
      "description": "Also check each entry for retractions and expressions of concern. Default true."
    }
  }
}
    arguments 102 lines
  • format_citation reads unknown 8h ago

    Resolve one to five scholarly identifiers (DOI, PMID, PMCID, ISBN, arXiv, ISSN, ADS bibcode, WHO IRIS URL) and format them in a citation style (Vancouver, APA, AMA, IEEE, CSE, or any of 10,000+ CSL styles).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "identifiers"
  ],
  "properties": {
    "lang": {
      "type": "string",
      "pattern": "^[A-Za-z]{2,3}(?:[-_][A-Za-z0-9]{2,8})?$",
      "maxLength": 16,
      "description": "BCP-47 locale, e.g. en-US or en-GB. Default en-US."
    },
    "style": {
      "type": "string",
      "pattern": "^[A-Za-z0-9:-]+$",
      "maxLength": 64,
      "description": "Citation style id (e.g. vancouver, apa, ama, ieee, cse, or any CSL style). Default vancouver."
    },
    "identifiers": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 500,
        "minLength": 1
      },
      "maxItems": 5,
      "minItems": 1,
      "description": "One to five scholarly identifiers (DOI, PMID, PMCID, ISBN, arXiv, ISSN, ADS bibcode, or WHO IRIS URL)."
    }
  }
}
    arguments 32 lines
  • check_retraction reads unknown 8h ago

    Check whether ONE work has been retracted, corrected, or had an expression of concern raised (Crossref / Retraction Watch). Accepts a DOI, PMID, PMCID, arXiv id, or ADS bibcode. For more than one work, call audit_citations instead (it screens every entry for retractions in one call) — do not call this tool in a loop; repeated single calls hit the rate limit.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 500,
      "minLength": 1,
      "description": "A DOI, PMID, PMCID, arXiv id, or ADS bibcode to check for retraction / correction / concern."
    }
  }
}
    arguments 15 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 3e3a2d8423d661d1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3e3a2d8423d661d1/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/3e3a2d8423d661d1/badge.svg)](https://brick.blue/agent/3e3a2d8423d661d1?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
80%

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.