
Zentric Protocol Mcp
io.github.ZentricProtocol由 GitHub 账号 ZentricProtocol 发布v0.1.3更新于 Oct 28, 2026
Prompt injection + PII detection for LLM apps and agent pipelines. Deterministic, sub-25ms.
概览
本地 MCP 服务器,将文本发送至 Zentric Protocol 托管 API 检测提示注入与 PII,返回判定结果和带签名的审计报告。
- 可以做什么
- 分析文本中的提示注入与越狱特征,返回 CLEARED 或 BLOCKED 判定、命中的特征和风险评分。
- 识别并匿名化邮箱、电话、身份证号、IBAN、SWIFT 等个人信息,支持遮蔽、掩码、令牌化和假名化处理。
- 为每次请求生成带 UUID、SHA-256 哈希、UTC 时间戳和延迟的签名审计记录,可用作合规证据。
- 可在代理流程的多个环节检查输入,例如用户消息、工具输出、RAG 片段和记忆读取。
- 适用场景
- 适合助手或代理流程会接收不可信文本、并希望在内容进入模型前做确定性预检并留下可审计记录的场景。也适合对提示注入和个人数据有合规或审计要求的团队。
- 运行要求
- 通过 npx 从 npm 包 zentric-protocol-mcp 本地运行,需要 Node.js。需要 Zentric Protocol API 密钥,通过环境变量 ZENTRIC_API_KEY 提供;免费额度为每月 10,000 次请求。需要能访问 Zentric Protocol API 的网络。
安装
在 SourceWeft 中
- 打开 控制台中的 Zentric Protocol Mcp,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
ZENTRIC PROTOCOL
Prompt injection detection & PII anonymization with a signed audit trail — for LLM apps and AI agents.
[Status] [Latency] [Precision] [GDPR] [EU AI Act] [CCPA]
Every prompt, RAG chunk and tool output inspected before it reaches your model — deterministic CLEARED / ANONYMIZED / BLOCKED verdicts with a signed audit record (SHA-256 + UUID + UTC) per request.
Detection tells you what happened. The audit record is what you show your auditor — GDPR Art. 30 evidence today, EU AI Act readiness tomorrow.
→ Get API key (free, 10,000 req/mo) · Quickstart · Integrity Report v1.0 (PDF)
[Zentric Protocol — See it in action]
A real prompt injection attempt. Caught in <0.1ms. Your model never sees it.
Repository Scope & Commercial License
This repository exists for transparency and contribution — not as a deployable alternative to the hosted service.
Cloning this repository does not give you access to the Zentric processing service. The detection engine that inspects prompts, detects PII, and generates signed audit reports runs on Zentric's infrastructure and requires an active license.
Why publish the middleware?
Because trust is infrastructure. You should be able to verify how authentication works, how your API key is validated, and how subscription state is checked before your requests reach the engine. We believe in auditability at every layer — including our own enforcement code.
Contributions welcome
We accept contributions to the middleware, webhook handler, and Supabase schema. Open a PR or file an issue. For security-related contributions, see the Security section.
Getting access
What is Zentric Protocol?
Zentric Protocol is an infrastructure integrity layer for AI systems. It sits between your application and your LLM, examining every signal — prompts, responses, user inputs — and returning a cryptographically-signed verdict before execution continues.
It is not a filter. It does not guess. It applies deterministic rules across a standardized pipeline and returns a structured, auditable JSON report for every request.
Performance
Zentric uses deterministic signature matching — not an ML classifier. Every block is a known pattern match, which means 100% precision on known patterns and zero false positives: nothing is ever blocked unless it matches a catalogued signature. Verdicts are returned in sub-millisecond time (no model in the hot path), so the same input always produces the same verdict.
Any published metric is reproducible: run npm run benchmark (benchmarks/run.mjs) against the public deepset/prompt-injections dataset to verify the numbers yourself.
The Three Modules
01 · IntegrityGuard
Detects prompt injection, jailbreak attempts, and instruction overrides before they reach your LLM.
- 22 catalogued injection signatures
- 7 supported languages (EN, ES, FR, DE, PT, ZH, JA)
- Deterministic multilingual signature matching — no ML model in the verdict path
- Mean server-side processing: <0.1ms (sub-millisecond; no model in the hot path)
02 · PrivacyGuard
Identifies and anonymizes PII in prompts and responses. Regional standards treated as first-class entities.
- 12 PII entity types, format-validated (Luhn, IBAN mod-97, mod-11, NIF/NIE checksum): SSN, NIF, CPF, CURP, IBAN, SWIFT, passport, email, phone, and more
- Regional pattern recognition (EU, US, LATAM)
- Anonymization operators: redact, mask, tokenize, pseudonymize
03 · ZentricReport
Every request that passes through the protocol generates a signed, immutable audit record.
API Reference
Authentication
Response
Verdict States
SDKs
Compliance Coverage
Zentric Protocol is designed from the ground up for regulated AI deployments.
Pricing
→ See plans · → Get API key · → Contact for Enterprise
Architecture Principles
Deterministic. The same input always produces the same verdict. No probabilistic black boxes in the critical path.
Stateless. The protocol does not store your data. Each request is processed and returned. The audit record is yours.
Composable. Deploy the full stack, a single guard, or wire only the audit layer into existing infrastructure.
Auditable. Every verdict is signed with SHA-256, timestamped in UTC, and assigned a UUID. Your compliance team will thank you.
For Agent Pipelines
Agent attacks don't arrive through the chat input. They arrive through tool call responses, RAG chunks, and memory retrievals — any external content that enters the prompt window. Your system prompt doesn't protect you here: it doesn't run until after the input is already parsed.
Wire Zentric at every ingestion point, not just on user messages:
- LLM input — user messages before they reach the model
- Tool output — external API responses before they re-enter the context window
- RAG retrieval — document chunks before they are assembled into the prompt
- Memory reads — stored context before it is injected into the next turn
One POST to /v1/analyze. The verdict comes back in sub-millisecond time. The agent continues or halts based on the result. Nothing else changes in your pipeline.
MCP Server — Claude Desktop Integration
Zentric Protocol ships a native Model Context Protocol (MCP) server that integrates directly with Claude Desktop and any MCP-compatible agent runtime.
What it does
The MCP server exposes Zentric's detection engine as a native MCP tool. When wired into Claude Desktop, the agent automatically calls analyze_prompt before sending any input to the LLM — user messages, tool responses, RAG chunks, and memory retrievals are all checked.
MCP Tool exposed
Returns: verdict (CLEARED / BLOCKED), risk_score, matched signatures, pii_entities, report_hash (SHA-256), latency_ms.
Install via npm
Claude Desktop configuration
Add to your claude_desktop_config.json:
Get your API key at zentricprotocol.com/quickstart — free tier is 10,000 requests/month, no credit card required.
MCP server source
The MCP server source code is in /mcp-server. It is built with the Model Context Protocol SDK and published to npm as zentric-protocol-mcp.
Security
We take the security of this protocol seriously. If you discover a vulnerability, please report it responsibly.
- Email: [email protected]
- Subject:
[SECURITY] <brief description> - Response SLA: 48 hours acknowledgement, 7 days resolution target
We do not operate a public bug bounty program at this time. Responsible disclosure is acknowledged in our changelog.
Roadmap
- IntegrityGuard v1.0 — 22 signatures, 7 languages
- PrivacyGuard v1.0 — 12 PII types, EU/US/LATAM
- ZentricReport v1.0 — SHA-256, UUID, GDPR Art.30
- REST API (production)
- Python SDK — Q3 2026
- Node.js SDK — Q3 2026
- Streaming support (SSE) — Q3 2026
- Webhook callbacks — Q4 2026
- Self-hosted deployment option — 2027
Contact
Zentric Protocol · Infrastructure Integrity for the AI Era
zentricprotocol.com · © ZP MMXXVI · v1.0.0
Built for CTOs who know that trust is infrastructure, not a feature.
来源:README.md,提交 6f83c07
工具
0版本历史
1- v0.1.3最新Sep 16, 2026
评分
已满足适用检查项的 40%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
请在仓库或注册中心条目中声明许可证。