ClaimsMCP MCP Server

An implementation of the "Claimify" methodology for factual claim extraction, delivered as a local Model Context Protocol (MCP) server. This tool

Local serverstdioPython

What is the ClaimsMCP MCP server?

ClaimsMCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. An implementation of the "Claimify" methodology for factual claim extraction, delivered as a local Model Context Protocol (MCP) server. This tool implements the multi-stage claim extraction approach detailed in the academic paper "Towards.

What you get

Claimify extracts verifiable, decontextualized factual claims from text using a sophisticated four-stage pipeline:

  • Research-based methodology — Implements the peer-reviewed Claimify approach
  • Structured outputs — Uses OpenAI's structured outputs for reliable, type-safe responses
  • MCP integration — Seamlessly integrates with development environments
  • Robust parsing — Handles various text formats including lists and paragraphs
  • Context-aware — Uses surrounding sentences to resolve ambiguities
  • Multi-language support — Preserves original language while extracting claims

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration and credentials

You will need one environment variable: OPENAI_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • OpenAI API: Requires an OpenAI API key (if your MCP host does not support sampling (Github Copilot in vsCode does)) - Compatible Model: Must use a model that supports structured outputs: - gpt-4o (recommended) - gpt-4o-mini (faster and cheaper) - Python 3.10+: For proper type hints and Pydantic support

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the claimsmcp mcp server does with a few real requests.

Choosing this one

This sits in the AI and media services group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by AdamGustavsson; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against ClaimsMCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

How to install the ClaimsMCP MCP server

{
  "mcpServers": {
    "claimify-local": {
      "command": "/path/to/your/claimify-env/bin/python",
      "args": [
        "/path/to/your/project/claimify_server.py"
      ]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • OpenAI API: Requires an OpenAI API key (if your MCP host does not support sampling (Github Copilot in vsCode does)) - Compatible Model: Must use a model that supports structured outputs: - gpt-4o (recommended) - gpt-4o-mini (faster and cheaper) - Python 3.10+: For proper type hints and Pydantic support
VariableDescriptionRequired
OPENAI_API_KEYCredential the server authenticates with.Yes

Frequently asked questions

It connects ClaimsMCP to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with ClaimsMCP directly.