原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Veritasgraph

作者:bibinprathap版本 0.1.2i★ –i在你的电脑上运行
注册名称io.github.bibinprathap/veritasgraph

安装

概览

作者提供的说明(英文原文)

Zero-trust, air-gapped Enterprise GraphRAG MCP server with offline, citation-grounded answers.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 需要你自己填写: VERITASGRAPH_MODEL, OLLAMA_HOST, STUDIO_DATA_DIR

你需要

  • PyPI已安装 Python 的 uv(用于 uvx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "veritasgraph": {
      "command": "uvx",
      "args": [
        "veritasgraph-mcp"
      ],
      "env": {
        "VERITASGRAPH_MODEL": "your-value",
        "OLLAMA_HOST": "your-value",
        "STUDIO_DATA_DIR": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add veritasgraph --env VERITASGRAPH_MODEL=your-value --env OLLAMA_HOST=your-value --env STUDIO_DATA_DIR=your-value -- uvx veritasgraph-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "veritasgraph": {
      "command": "uvx",
      "args": [
        "veritasgraph-mcp"
      ],
      "env": {
        "VERITASGRAPH_MODEL": "your-value",
        "OLLAMA_HOST": "your-value",
        "STUDIO_DATA_DIR": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "veritasgraph": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "veritasgraph-mcp"
      ],
      "env": {
        "VERITASGRAPH_MODEL": "your-value",
        "OLLAMA_HOST": "your-value",
        "STUDIO_DATA_DIR": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • VERITASGRAPH_MODEL env
    Default local Ollama model for ingest/query (e.g. qwen3:latest).
  • OLLAMA_HOST env
    Local Ollama endpoint.
  • STUDIO_DATA_DIR env
    Directory where the knowledge-graph snapshot is persisted.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 bibinprathap 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 18329 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 18329 个服务器的 13% 更新
  • 基础检查结果等于或优于此分类中其他 18329 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Veritasgraph 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.1.2)于4个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, Excaliself

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者:formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者:desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211前天更新
安装

Excaliself

作者:maciekzygmunt

Find, read, create, edit, and organize Excalidraw drawings in your self-hosted Excaliself instance.

在云端运行今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

VeritasGraph — The Governed, On-Prem GraphRAG & Agent Framework

Stop chunking blindly. Combine Tree-Search structure with Knowledge-Graph reasoning — and wire it into governed AI agents. Runs 100% locally or in the cloud.

🎯 Traditional RAG guesses based on similarity. VeritasGraph reasons based on structure.

Don't just find the document — understand the connection, then act on it with governed agents.

🌐 Live site · ⭐ Star · 🍴 Fork · 💬 Discuss · 🐛 Report a bug


python -m veritasgraph_mcp     # from repo root (needs local Ollama for ingest/query)

[▶️️ Watch the Full Talk & Live Demo on YouTube (27 mins)](https://www.youtube.com/watch?v=MDo1Mk8R5Wo)

Why Vector RAG Breaks on Deep Research
  • Attribution is a data model, not a prompt: Storing provenance at write time prevents hallucinated citations at read time.
  • Deterministic retrieval: Graph traversal is fully reproducible, separating factual evidence traces from stochastic LLM generation.
  • Explicit abstention: The agent identifies missing graph edges and returns "insufficient evidence" rather than guessing.

-

📚 Featured Guide — Build Governed AI Agents On-Prem

A complete walkthrough of designing, wiring, and shipping governed AI agents entirely on your own infrastructure.

**📄 Read the guide: *Build Governed AI Agents On-Prem* (PDF)**

▶️ [Watch the walkthrough on YouTube](https://youtu.be/sA7ReEgdJfg)


🚀 Quick Start (2 lines, no GPU)

pip install veritasgraph

veritasgraph demo --mode=lite

That's it — an interactive demo using cloud APIs (OpenAI/Anthropic), no local models required.

ModeBest ForRequirements
--mode=liteQuick demo, no GPUOpenAI/Anthropic API key
--mode=localPrivacy, offline useOllama + 8GB RAM
--mode=fullProduction, all featuresDocker + Neo4j
export OPENAI_API_KEY="sk-..."        # Lite: cloud APIs, zero setup

veritasgraph demo --mode=lite

veritasgraph demo --mode=local --model=llama3.2 # 100% offline with Ollama veritasgraph start --mode=full # full GraphRAG pipeline

Useful links: ⚡ Live docs · 🎮 Live demo · 📖 Article · 📄 Research paper


🏥 Example Implementation — MedTrust Agent

[MedTrust Agent](MedTrust%20Agent/README.md) is a complete, reproducible example implementation of the VeritasGraph governed-agent architecture, applied to medical and pharmaceutical workflows — a zero-trust, observable LLM agent framework (NEECON 2026 paper).

  • Zero-trust control plane: least-privilege IAM with step-up authorization — no tool runs before authorization succeeds.
  • Governed answers: mandatory [doc#chunk] citations; uncited answers are withheld or routed to human review.
  • Tamper-evident audit: keyed, hash-chained audit log with published anchors.
  • Honest evaluation: security measured directly from the running code (100% unauthorized actions blocked, Wilson 95% CIs), answer quality clearly labelled *illustrative*; 69 tests, a versioned 40-scenario suite, and a one-command reproduce script.
python -m medtrust.demo    # end-to-end governed demo, 100% offline

📄 Read the full write-up: MedTrust Agent README


🧩 Built with VeritasGraph

A growing ecosystem of projects is building on VeritasGraph for enterprise GraphRAG, agent orchestration, fact-checking, and governed reasoning.

Community projects and integrations

If you are building with VeritasGraph and want to be featured here, open a PR or reach out with a short repo description and usage summary.


� Live Example — Floorplan-KG Takeoff Demo

A hosted, zero-setup example of VeritasGraph applied to construction drawings. Upload a floorplan PDF (or pick a bundled sample) and the engine extracts rooms, dimensions, openings, fixtures, and schedules — then builds a knowledge graph and quantity takeoff you can query, all with verifiable provenance back to the source sheet.

[🏗️ Try the Floorplan-KG demo](https://spaceai-llmpc.ngrok.app/floorplan) — *free, no login; runs the live PyMuPDF/pdfplumber extraction pipeline.*

  • What it shows: PDF → structured rooms/dimensions/schedules → knowledge graph → CSV/XLSX takeoff export, with a VeritasGraph assist panel for grounded Q&A over the extracted graph.
  • Why it matters: the same governed-attribution model that powers document RAG applies to geometry — every measured quantity traces back to a specific sheet and element rather than a guessed value.
  • Example output: a single-sheet residential plan returns ~17 rooms and ~2,400 sq ft in under 200 ms.

Studio is a local Agent Build Workspace (FastAPI + single-page UI) that lets you build a knowledge graph from your own documents and wire it into agents alongside tools, memory, data logging, guardrails, and headroom-style context budgeting — then chat with those agents live and watch every stage of the orchestration pipeline. Everything runs 100% locally against Ollama.

[🎮 Try the Studio Live](https://bibinprathap.github.io/VeritasGraph/studio/) — *stable URL that always redirects to the current running studio tunnel.*

Run it:

pip install -r requirements.txt

ollama serve & ollama pull qwen3:latest # any local chat model STUDIO_DATA_DIR="$PWD/studio_api/data" \ uvicorn studio_api.main:app --host 127.0.0.1 --port 8200 --log-level warning

Studio UI → http://localhost:8200/studio · API docs → /docs

One-command end-to-end demo (builds a graph + drives a fully-wired agent through graph reasoning, memory recall, PII redaction, and a guardrail block):

python3 demos/agent-studio/sample_pipeline.py --model qwen3:latest

What's inside — full Studio feature set

  • 🧩 Knowledge Graph builder & explorer — ingest text, extract entities/relationships locally, inspect nodes/edges with grounded evidence.
  • 🔎 Graph Q&A with citations — multi-hop answers backed by [doc#chunk] source attribution.
  • 🤖 Agent workspace — create/edit agents with model selection, prompt/persona settings, and per-agent capability toggles.
  • 🔀 Governed orchestration pipeline — per-turn flow of Guardrails → Memory → Knowledge Graph → Headroom budget → Tools → Data log, with full trace visibility.
  • 🧰 Editable tools catalog — add, edit, enable/disable, test, and delete tools directly in Studio.
  • 🌐 External real tool support — call real HTTP endpoints with configurable method, auth header, and custom headers.
  • 🔌 MCP bridge integrations — local MCP proxy connectors (e.g. Chrome DevTools MCP, Unity MCP) with health-aware probing.
  • 🛡️ Guardrails — PII redaction and policy-block controls with visible guardrail-block metrics.
  • 🧠 Memory + Data logs — per-agent short-term memory and interaction-log persistence.
  • 📈 Evaluation & fine-tune simulation — run eval suites, track pass-rate trends, and queue/monitor fine-tune jobs.
  • 💬 Playground — run governed agent conversations live and inspect the pipeline trace.
  • 📊 KPI dashboard — active agents, connected tools, eval pass rate, and guardrail-block counters.

See [`studio_api

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx