DocQA MCP

com.agentsconsultants.apiPublished by api.agentsconsultants.comv1.0.2Updated Oct 24, 2026

AI document verification: catch hallucinations, arithmetic errors, and field mismatches.

VerifiedSTDIODesktop onlyAI & ML

Overview

AI-generated overview

DocQA MCP lets an AI assistant verify documents through the DocQA service, catching hallucinations, arithmetic errors and field mismatches.

What you can do
Verify documents through the DocQA service, checking content for hallucinations, arithmetic errors and field mismatches. The manifest lists no individual tools, so the exact operations are not documented; the stated purpose is AI document verification.
When to use it
Useful when an assistant produces or reviews documents and you want an automated check for fabricated content, calculation mistakes or mismatched fields before relying on the output.
Requirements
Runs as a local process over stdio, installed from the npm package docqa-mcp, so Node.js is needed. A DocQA API key is required in the DOCQA_API_KEY environment variable; the key is obtained from the provider's site. Network access to the DocQA service is implied.
Before you install
The server requires a secret API key in DOCQA_API_KEY; keep it out of shared configuration and logs. Documents submitted for verification are sent to the third-party DocQA service, so avoid sending confidential material unless that is acceptable. The manifest lists no tools, so what it reads or changes cannot be confirmed in advance.

Installation

In SourceWeft

  1. Open DocQA MCP in the dashboard and add it to a workspace.
  2. 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

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 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.