fact-checker-mcp
v0.13.0
Published
Fact-Checker MCP Server - SENSE + GATE verification service with semantic cache
Readme
Fact-Checker MCP Server
A Model Context Protocol (MCP) server that provides AI-powered fact-checking and claim verification. Uses Claude Haiku for claim extraction, SPO-based semantic fingerprinting, and Redis caching for deduplication.
Exposes both an MCP (StreamableHTTP) interface for AI agents and a REST API for HTTP clients.
Features
MCP Tools
| Tool | Description |
| --------------- | -------------------------------------------------------------------------------------------------------------------- |
| extractClaims | Extract verifiable claims from text with type and durability classification |
| verifyContent | Verify outbound content — extracts claims, checks each against cache + Haiku, returns verdicts and corrected content |
| verifySignal | Verify an inbound signal claim — returns a trust assessment with action recommendation |
| getFactMemory | Search the fact-checker cache for previously verified claims |
REST API
| Method | Endpoint | Description |
| ------ | ---------------------------- | ---------------------------------- |
| POST | /api/extract-claims | Extract claims from text |
| POST | /api/verify-content | Verify content (GATE tool) |
| POST | /api/verify-signal | Verify a signal claim (SENSE tool) |
| GET | /api/fact-memory?query=... | Search cached verifications |
| GET | /health | Health check |
Quick Start
Prerequisites
- Node.js 20+
- An Anthropic API key
- Redis (optional — caching is gracefully skipped when unavailable)
Install
git clone https://github.com/luminarylane/fact-checker-mcp.git
cd fact-checker-mcp
npm install
npm run buildConfigure
Copy the example env file and add your Anthropic API key:
cp .env.example .env
# Edit .env and set ANTHROPIC_API_KEYRun
# Development (auto-reload)
npm run dev
# Production
npm startThe server starts two listeners:
- REST API on port 8004 (configurable via
PORT) - MCP transport on port 8005 (configurable via
MCP_PORT)
Claude Desktop Configuration
Add to your claude_desktop_config.json:
{
"mcpServers": {
"fact-checker": {
"command": "node",
"args": ["/path/to/fact-checker-mcp/dist/index.js"]
}
}
}How It Works
Claim Extraction (extractClaims)
Extracts verifiable claims from text using Claude Haiku. Each claim is classified by type (statistic, company_fact, quote, product_claim, market_assertion, opinion) and durability (permanent, durable, transient, volatile).
Content Verification (verifyContent / GATE)
Full content verification pipeline:
- Extract claims from content
- Fingerprint each claim using SPO (Subject-Predicate-Object) triples
- Check Redis cache for previously verified claims
- Verify uncached claims via Claude Haiku with optional brand data and web context
- Return verdicts (
publish,revise,block) with corrected content
Signal Verification (verifySignal / SENSE)
Verifies a single inbound claim (e.g., "Company X raised $50M") and returns:
- Signal verdict:
verified,likely_true,uncertain,likely_false,contradicted - Action recommendation:
safe_to_act,proceed_with_caution,needs_human_review,do_not_act
Semantic Fingerprinting
Claims are normalized into Subject-Predicate-Object triples via Haiku, then hashed. Equivalent claims (different wording, same meaning) produce the same fingerprint, enabling cache deduplication.
Fact Memory (getFactMemory)
Search previously verified claims by keyword. Useful for avoiding re-verification during multi-step workflows.
Configuration
| Env Var | Default | Description |
| --------------------- | --------------------------- | ------------------------------------------------------- |
| ANTHROPIC_API_KEY | — | Required. Anthropic API key |
| ANTHROPIC_MODEL | claude-haiku-4-5-20251001 | Model to use for verification |
| REDIS_URL | — | Redis connection URL (optional) |
| PORT | 8004 | REST API port |
| MCP_PORT | 8005 | MCP transport port |
| HOST | 0.0.0.0 | Bind address |
| CACHE_TTL_PERMANENT | -1 | Cache TTL for permanent facts (seconds, -1 = no expiry) |
| CACHE_TTL_DURABLE | 2592000 | Cache TTL for durable facts (30 days) |
| CACHE_TTL_TRANSIENT | 86400 | Cache TTL for transient facts (1 day) |
| CACHE_TTL_VOLATILE | 3600 | Cache TTL for volatile facts (1 hour) |
Architecture
- Transport: StreamableHTTP (MCP) + Express (REST)
- AI: Claude Haiku for claim extraction, verification, and SPO fingerprinting
- Cache: Redis with durability-based TTLs (gracefully degrades without Redis)
- Rate Limiting: Token-bucket rate limiter for Anthropic API calls (100 req/min)
- Safety: Untrusted content wrapped with hashed markers for prompt injection defence
Development
# Development server (auto-reload)
npm run dev
# Type check
npx tsc --noEmit
# Run tests
npm test
# Test with coverage
npm run test:coverage
# Build
npm run build