Skip to main content
The Scite MCP server exposes 54 tools across six groups. Call tools/list to get the live catalog with full input schemas; this page is the narrative index.

Literature

Search papers, read full text, and find open-access PDFs.

Verification

Check claims and reference lists, record citation decisions, and format bibliographies.

Citation analysis

Traverse the citation graph, page through citing statements, and run bibliometrics.

Evidence

Patents, trials, grants, FDA device and drug records, adverse events, and safety alerts.

Collections

Create and maintain saved sets of papers, with notes and files.

Account

Alerts, Assistant chat history, and MCP usage and billing.

The catalog

Literature

Verification

Citation analysis

Evidence

Collections

Account

Access requirements

Every tool above is visible in tools/list when your credential carries the mcp scope. Access is enforced when you call the tool, not when you list it, so a tool can appear in the catalog and still return an error on tools/call. Full-text content follows the paper’s license, not your plan. Tools that return quoted text (search_literature, read_fulltext, get_citation_statements, check_claim, citation_graph) return it for openly licensed papers and papers your organization is licensed for. Otherwise they return contentDenied: true and keep the metadata, tallies, and citation types. Organization licenses work differently from individual accounts on Evidence tools. If your account is on an organization license, reaching the Pro tier does not unlock Evidence. Your license needs the explicit evidence:<dataset>:mcp entitlement. Email sales to have one added. When a tool call fails an access check, the server returns JSON-RPC error -32003 with the required plan or scope in the error payload:
After an upgrade, new entitlements can take up to 15 minutes to reach an active MCP session. To apply them immediately, disconnect and reconnect the Scite MCP server in your client.

Tool annotations

Each tool carries MCP annotations that describe its behavior. Clients use these to decide what needs confirmation. The remaining tools write data but don’t destroy it: the Collection create, update, and add tools, upload_collection_file, report_citations, and manage_subscription when you pass pay_as_you_go_limit. get_more_tools sends feedback to Scite, so don’t treat it as read-only.

Conventions

Two query conventions run through the catalog, and they are not the same one.
  • search_literature, bibliometrics, and the other literature tools use named parameters: term, dois, limit, offset, and typed filters. This matches the Search API.
  • Every Evidence tool uses the compact q / f / p / s / sortDir form. This matches the Evidence API.
Search-then-fetch is the intended pattern for Evidence. Search results are deliberately slim to save context; call the matching get_* tool only when you need fields the search result doesn’t already carry. Every tool also accepts an optional user_intent string: a short snake_case label for why the tool is being called, such as reference_check. It feeds anonymous usage analytics and doesn’t change results.
  • Scite MCP: setup, authentication, and the JSON-RPC protocol
  • Prompts: the prebuilt workflows the server ships
  • Glossary: Smart Citation terminology used across tool responses