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.

已驗證STDIO僅桌面安全與監控AI 與機器學習

概覽

AI 產生的概覽

本機 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 的網路。
安裝前請注意
所有被分析的文字都會送到第三方 API,提示詞、工具輸出與 RAG 片段會離開本機;廠商稱請求為無狀態、不儲存資料。API 金鑰屬機密,不應寫入共用設定。免費額度之外有付費方案,README 中的合規聲明屬廠商宣傳,並非獨立認證。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Zentric Protocol Mcp,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

[Zentric Protocol]



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.

What's in this repoWhat's not in this repo
Authentication middleware (/middleware)IntegrityGuard detection engine
Stripe webhook handler (/api/webhooks)PrivacyGuard PII detection engine
Supabase schema & migrations (/supabase)Signature database (22 injection vectors)
API interface contracts & response shapesModel weights and training data
Landing page & documentation (index.html)Audit record signing infrastructure

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

TierPriceRequestsStart
FreeFree10,000/moGet API key →
Indie$29/mo25,000/moSee pricing →
Team$99/mo100,000/moSee pricing →
Scale$499/mo500,000/moSee pricing →
EnterpriseCustomUnlimitedContact →

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.

Input Signal     │     ▼┌─────────────────────────────────────────┐│           ZENTRIC PROTOCOL              ││                                         ││  ┌─────────────┐  ┌─────────────────┐  ││  │IntegrityGuard│→│  PrivacyGuard   │  ││  │ 22 injection │  │  12 PII types   │  ││  │  signatures  │  │  7 languages    │  ││  └─────────────┘  └────────┬────────┘  ││                             ▼           ││                    ┌──────────────┐     ││                    │ ZentricReport│     ││                    │ UUID+SHA-256 │     ││                    │  GDPR Art.30 │     ││                    └──────────────┘     │└─────────────────────────────────────────┘     │     ▼Verdict + Certificate → Your System

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.

json
{  "report_id": "zp_01HXYZ...",  "uuid": "f47ac10b-58cc-4372-a567-0e02b2c3d479",  "timestamp_utc": "2026-05-14T22:00:00.000Z",  "sha256": "e3b0c44298fc1c149afb...",  "verdict": "CLEARED",  "integrity": {    "injection_detected": false,    "signatures_matched": [],    "confidence": null  },  "privacy": {    "pii_detected": true,    "entities": [      { "type": "EMAIL", "action": "REDACTED", "position": [42, 61] }    ]  },  "compliance": {    "audit_record": true,    "ccpa": true,    "eu_ai_act_s52": true  },  "latency_ms": 0.05}

API Reference

Authentication

bash
curl -X POST https://api.zentricprotocol.com/v1/analyze \  -H "Authorization: Bearer zp_live_..." \  -H "Content-Type: application/json" \  -d '{    "input": "Your prompt or user input here",    "modules": ["integrity", "privacy"],    "options": {      "anonymize": true,      "language": "auto"    }  }'

Response

json
{  "status": "ok",  "verdict": "CLEARED",  "report": { ... },  "anonymized_input": "Your prompt or user input here",  "latency_ms": 0.05}

Verdict States

VerdictDescription
CLEAREDInput passed all checks. Safe to forward to LLM.
BLOCKEDInjection or high-risk pattern detected. Reject.
ANONYMIZEDPII found and redacted. Anonymized input returned.

SDKs

LanguageStatus
Pythonpip install zentricprotocol (coming Q3 2026)
Node.jsnpm install @zentricprotocol/sdk (coming Q3 2026)
REST APIAvailable now

Compliance Coverage

Zentric Protocol is designed from the ground up for regulated AI deployments.

StandardCoverage
GDPR Art. 30Reproducible audit record per request — one component of an Art.30 documentation strategy
GDPR Art. 25Privacy by design — anonymization as default
CCPA §1798.100Consumer data identification and processing record
EU AI Act §52Transparency obligations resolved at infrastructure level

Pricing

TierPriceRequestsUse Case
FreeFree10,000/moTest the protocol end-to-end, no credit card
Indie$29/mo25,000/moSolo developers shipping their first AI feature
Team$99/mo100,000/moSmall teams running AI in production
Scale$499/mo500,000/moHigh-volume pipelines and multi-agent systems
EnterpriseCustomUnlimitedRegulated industries, EU data residency, dedicated SLA

→ 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.

bash
curl -X POST https://api.zentricprotocol.com/v1/analyze \  -H "Authorization: Bearer zp_live_..." \  -H "Content-Type: application/json" \  -d '{"input": "<tool_output_or_rag_chunk_here>", "modules": ["integrity", "privacy"]}'

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

analyze_prompt(text: string) -> ZentricReport

Returns: verdict (CLEARED / BLOCKED), risk_score, matched signatures, pii_entities, report_hash (SHA-256), latency_ms.

Install via npm

bash
npx zentric-protocol-mcp

Claude Desktop configuration

Add to your claude_desktop_config.json:

json
{  "mcpServers": {    "zentric-protocol": {      "command": "npx",      "args": ["zentric-protocol-mcp"],      "env": {        "ZENTRIC_API_KEY": "your_api_key"      }    }  }}

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
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.1.3最新Sep 16, 2026

評分

已滿足適用檢查項的 40%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。