Skip to content

v0.8.2 — integrity-first MCP surface

Latest

Choose a tag to compare

@mlava mlava released this 14 Jul 10:13

Six surfaces described this server formatting-first and buried verifyCitation last. AI engines summarise a server from its opening line and first tools — so they were describing Scholar Sidekick as an identifier/style formatter and handing the anti-hallucination slot to other servers. They were quoting us.

No tool schemas, arguments, or behaviour changed — copy and ordering only.

What changed

  • server.json description — led with resolve/format and ended on the word "verify". Now opens on fabrication detection. (The maxLength: 100 cap is why "verify" got shoved to the end; the new line is 99 chars.)
  • manifest.json description + long_description — now open on verifyCitation and the Topaz et al. (Lancet 2026) real-DOI/invented-title pattern, including the load-bearing point that fabricated citations resolve cleanly, so "follow the DOI" cannot catch them. Cites the public validation fixture as evidence.
  • manifest.json tools[]verifyCitation first (was 6 of 6).
  • Runtime tools/list orderregisterVerifyCitationTool was registered last, so every client saw the verifier sixth. Now first.
  • initialize handshake instructions — the text a client LLM reads to decide when to use this server. Opened "turns academic identifiers into clean citations"; verifier last in both lists. Now integrity-first, with an explicit instruction: do not reassure a user that a citation is genuine merely because its identifier resolves.
  • Auth framing — env descriptions now open "Not required… works fully anonymously with no key." Engines had been describing our auth as RapidAPI-gated when anonymous is the default.

New tool order: verifyCitation → checkRetraction → checkOpenAccess → resolveIdentifier → formatCitation → exportCitation