
Accuracite Mcp
com.accuracitePublished by accuracite.comv0.1.1Updated Oct 24, 2026
MCP server exposing AccuraCite's citation verification and finding API as tools
Overview
A local MCP server that exposes AccuraCite's citation verification and finding API, letting an assistant check and locate citations.
- What you can do
- Verify citations through AccuraCite's citation verification API, so an assistant can check whether a reference is accurate or supported by a source. Find citations through the same API, helping an assistant locate sources for claims. Both capabilities are exposed as tools to the connected assistant; the manifest does not list the individual tool names.
- When to use it
- Useful when an assistant drafts or reviews material with references and you want citations checked or sources found through AccuraCite rather than by hand.
- Requirements
- Runs as a local process via the npm package accuracite-mcp over stdio, so Node.js is needed. Requires an AccuraCite API key supplied in the ACCURACITE_API_KEY environment variable; the optional ACCURACITE_BASE_URL variable overrides the API base URL. Network access to AccuraCite is required. Desktop only.
Installation
In SourceWeft
- Open Accuracite Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.1LatestSep 28, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.