mcp-server-tibet-core
The Trust Kernel for AI - MCP Server
Audit as a Precondition, Not an Afterthought.
MCP (Model Context Protocol) server that gives Claude, Codex, Gemini, and other AI assistants full TIBET provenance capabilities.
Installation
pip install mcp-server-tibet-core
Quick Start
Add to your Claude Desktop config (~/.config/claude/claude_desktop_config.json):
{
"mcpServers": {
"tibet-core": {
"command": "mcp-server-tibet-core"
}
}
}
Restart Claude Desktop. Now your AI can create provenance tokens for every action!
Available Tools
| Tool | Description |
|---|---|
tibet_create |
Create a provenance token BEFORE any action |
tibet_verify |
Verify a token's integrity |
tibet_chain |
Get full provenance chain for a token |
tibet_export |
Export audit trail (JSON/markdown/summary) |
tibet_list |
List recent tokens |
tibet_status |
Get TIBET provider status |
TIBET Provenance Model
Every action is documented with four dimensions:
- ERIN (what's IN) - The content/data of the action
- ERAAN (attached) - Dependencies and references
- EROMHEEN (around) - Context and environment
- ERACHTER (behind) - The WHY - intent and purpose
Example Usage
When your AI performs an action, it can now document it:
AI: I'll create a TIBET token before modifying this file.
[tibet_create]
- action: "file_write"
- erin: {"file": "config.py", "changes": "Added API key validation"}
- erachter: "Improve security by validating API keys before use"
- eraan: ["issue-123", "security-audit-2024"]
- eromheen: {"branch": "main", "user": "jasper"}
Token created: tbt_abc123...
Now you have an immutable audit record of what the AI did and why.
Why TIBET?
- Compliance Ready: AI Act, NIS2, GDPR, DORA
- Audit Trail: Every action documented before execution
- Trust Kernel: Like TPM for hardware, but for AI actions
- Enterprise Grade: Used by 1,162+ enterprise mirrors
Links
Philosophy
"Don't ask what your AI did. Know before it acts."
Every AI action, documented before execution. Compliance built-in, not bolted-on. One kernel. Every AI. Full provenance.
One love, one fAmIly!
MIT License - Humotica 2024-2026
License
MIT
Credits
Designed by Jasper van de Meent. Built by Jasper and Root AI as part of HumoticaOS.
Stack-positie: Groep agentic · Bootstrap = OSAPI-handshake naar tibet + jis (fail → snaft-rule + tibet-pol-rapport) · ← tibet-core · mcp-server-tibet → · See STACK.md · See demo/golden-path/ for the spine end-to-end.
Enterprise
For private hub hosting, SLA support, custom integrations, or compliance guidance:
| Enterprise | enterprise@humotica.com |
| Support | support@humotica.com |
| Security | security@humotica.com |
See ENTERPRISE.md for details.
Metadata
Release files for mcp-server-tibet-core 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mcp_server_tibet_core-0.1.1.tar.gz | 7.4 kB | Without provenance | Details for mcp_server_tibet_core-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_server_tibet_core-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for mcp_server_tibet_core-0.1.1-py3-none-any.whl |
Total release size: 14.4 kB
Release files / mcp_server_tibet_core-0.1.1.tar.gz
| Download URL | mcp_server_tibet_core-0.1.1.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c47548c237c59c9c11e46c368c0af58a2b9d03b09f1309addc26d77c0227f4a1
|
|
BLAKE2b-256 checksum How to use checksums |
8c7ebc62631f065a2a4b1765a62cdc14b8762eddc29557cafb93e660140c3202
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / mcp_server_tibet_core-0.1.1-py3-none-any.whl
| Download URL | mcp_server_tibet_core-0.1.1-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7dc9667a1b73474ed109a1821dd5fff77645fa24015c091f128c42bf576d75cd
|
|
BLAKE2b-256 checksum How to use checksums |
bac2fda02d60e0b69dd5f69a9088370c8c37f342dc454feb023342dbdafee4af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for mcp-server-tibet-core 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.