mcpbeat Sign in

VeriGhost-Clarity MCP Server

answering

VeriGhost-Clarity is answering right now. Last checked 1 min ago.

Hallucination validator and factual grounding checker for LLM outputs.

Uptime history 47 days of history · worst day 99%
47 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
96 ms
Response time
average over 24h
authentication required
Access
sse

Nothing serious here today

Today is the operative word: we check VeriGhost-Clarity every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add verighost --transport http https://verighost-mcp.vercel.app/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "verighost": {
      "url": "https://verighost-mcp.vercel.app/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.verighost]
url = "https://verighost-mcp.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "verighost": {
      "url": "https://verighost-mcp.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "verighost": {
      "url": "https://verighost-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://verighost-mcp.vercel.app/api/mcp sse needs auth 41 ms 1 min ago

Alternatives to VeriGhost-Clarity

same job, measured the same way
Perf MCP
by perf-ai

Fact-check and fix AI outputs. Hallucination detection, schema validation, auto-repair.

30 installs/wk local only
HallucC — Hallucination & Safety Guardian
by fredyee

Hallucination & safety checks for LLM/Agent outputs: claim-level fact-check with citations.

answering
Qc Validator
by mdfifty50-boop

Output quality control and validation for AI agents

36 installs/wk local only
retriEVAL
by hcarrillo001

LLM evals as MCP tools: score outputs for faithfulness, relevancy, and hallucination.

local only
JSON Contracts
by json-contracts

JSON contract registry and validator for structured LLM and agent outputs.

53 installs/wk local only
Lens MCP
by mrhpython

Outside-in validation gate for AI-generated text; a separate model checks LLM output, fail-closed.

39 installs/wk local only
Arkheiaai
by arkheiaai

Detect fabrication and hallucination in any LLM output. 30+ models supported.

46 installs/wk local only
eleata Claim Verifier
by hernaninverso

Grounding/hallucination guard: verify a claim against evidence (Supported/Refuted/NEE).

34 installs/wk local only

VeriGhost-Clarity — questions

Answers built from our own checks of this server.

Why is there no tool list for VeriGhost-Clarity?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is VeriGhost-Clarity working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 96 ms. The bar chart above shows every period we have measured.
How do I connect VeriGhost-Clarity?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does VeriGhost-Clarity need an API key?
Yes. Every time we knock, VeriGhost-Clarity answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is VeriGhost-Clarity?
It answers our handshake in 96 ms on average, which is faster than 83% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.