# webcite-mcp-server [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/strategyconnect/webcite-mcp-server  
**GitHub Stars:** 0  
**npm Downloads (last month):** 1029  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/webcite-mcp-server

## Description
WebCite MCP Server - verify AI claims against authoritative sources, bind quotes back to their source passage, and extract document figures deterministically. Works with any MCP-compatible agent or tool.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "webcite-mcp-server": {
    "command": "npx",
    "args": ["-y","webcite-mcp-server"]
  }
}
```

## Documentation

## What webcite-mcp-server does

webcite-mcp-server exposes WebCite capabilities through the Model Context Protocol. Its primary use is claim verification: an agent can submit a factual claim and receive evidence from authoritative publications, with quotations associated with the passages they came from. The workflow can be constrained with source requirements such as an official country, primary-source status, or an approved domain.

The server also supports document-oriented review. Original image, PDF, or PowerPoint bytes can be uploaded for parsing, after which an agent can inspect coverage, unreadable areas, claim limits, and source or page locators. This is intended for extracting and checking figures from source documents, not for assuming that a completed upload or review captured every value.

## How it works

The hosted MCP endpoint is a Streamable HTTP service at `https://api.webcite.co/mcp`. A client can be pointed to that endpoint using the connection flow at `https://webcite.co/connect`. The remote service uses the `public` profile for supported public API workflows.

Claim verification can use `verify_claim` or `verify_claim_stream`. Official-source constraints belong in the request’s `filters`; known public HTTPS reports can be supplied through `source_urls`. A URL or `site:` expression written inside the claim does not replace those request fields.

For remote retrieval, `upload_url` can obtain bounded original bytes from a public HTTPS URL, subject to public-address and redirect checks, and return asset references. Uploaded material should be parsed before review. Verification and extraction operations can be long-running, so saved review, citation, job, and operation IDs are useful when a request times out or produces an uncertain result.

## Setup and configuration

Use an MCP client that supports the hosted Streamable HTTP transport and configure it with `https://api.webcite.co/mcp`. The published package and the hosted API are separate deployments: installing or publishing the package does not deploy the hosted service, frontend, or MCP binary.

Local SDK and self-hosted MCP requests use a 15-minute default headers-and-body timeout. `WEBCITE_API_TIMEOUT_MS` can override that value when a different timeout is needed. The hosted endpoint and self-hosted deployment should be treated as separate serving identities when checking available behavior.

## Tools and capabilities

- Verify factual claims against authoritative sources.
- Stream claim-verification results with `verify_claim_stream`.
- Apply official-source and domain filters to verification requests.
- Associate quotations with their originating source passages.
- Upload bounded source content from public HTTPS URLs with `upload_url`.
- Review figures in images, PDFs, and PowerPoint documents with source and page locators.

## Limitations and notes

Evidence retrieval is bounded and does not guarantee exhaustive source coverage. A search with no evidence does not establish that the information is unavailable. An extraction failure remains a failure, and a successful upload, completed review, or large citation set does not certify that every figure was read or verified.

For uploaded slides, citation links do not guarantee pixel-level highlighting. Review the original publisher passage before treating a verification stance as proof. When a request times out or its result is uncertain, retain the associated identifiers, read retained progress before retrying, and reuse an idempotency key only for the same request.

_Full upstream README: https://allmcps.com/mcp/webcite-mcp-server/readme_