YodMCP
YodMCP — Agenten-Betriebssystem
YodMCP ist ein produktionsorientierter Agenten-Betriebssystem-Kernel auf MCP: Multi-Graph-Speicher, Tasks, Skills, A2A, Attestierung (Software / simuliertes TEE), OpenTelemetry und planbasierte Monetarisierung.
Dieses README ist so geschrieben, dass ein leitender Ingenieur mit nur dieser Datei + dem Quellbaum jede Schnittstelle installieren, bereitstellen, Funktionen ausprobieren und Ende-zu-Ende verifizieren kann.
FOUNDRY-Mapping
FOUNDRY (vom Host verwaltetes Vertrauen und Speicher für langfristige Agentenschwärme) trennt die Erzeugung nicht vertrauenswürdiger Vorschläge von der hostseitigen Verifikation und dem Register etablierter Fakten.
YodMCP ist dieses Register in Produktion: Agents rufen memory_write auf; die Übernahme in den semantischen Speicher ist kontrolliert; der Host besitzt den Evaluator. Ausführliche Notiz: docs/FOUNDRY.md.
First Dollar
Zuerst messen. Platz nehmen, wenn die Schleife hält.
Einheit | Stripe | x402 |
OpenGOS Search $0.40 |
| |
OpenGOS Draft $2.50 |
| |
Agentic OS Cycle $0.75 |
| |
YodMCP Pro $49/mo | USDC |
x402-Schiene: x402-cloudflare-starter. Desk-Sync: https://anamized.grok.me
Related MCP server: Agentic Control Framework (ACF)
Paket-Schnittstellen
| Schnittstelle | Befehl | Standard | Zweck |
|---------|---------|---------|
| MCP | yodmcp | stdio | Lokale MCP-Clients (Cursor, Claude Desktop, usw.) |
| MCP HTTP | yodmcp --http --port 8000 | :8000/mcp | Remote-/Streamable-HTTP-MCP |
| API | yodmcp-api --port 8080 | :8080 | REST-Health, Speicher, Audit, Skills, Abrechnung |
| A2A | yodmcp-a2a --port 9000 | :9000 | Agent Card, Nachrichten, Tasks |
| SDK | from yodmcp.sdk import YodClient | HTTP-Client | Schlanker Client für die API |
| Skills | skills:// + skills/*/SKILL.md | automatisch geladen | Agent Skills als MCP-Ressourcen |
| Verify | pytest + scripts/verify_e2e.py | CI | Substrate-, durable- und TEE-Modi |
Anforderungen
Python 3.11 oder 3.12 (3.10+ deklariert; CI deckt 3.11/3.12 ab)
Optional: Docker für Multi-Service-Compose
Installation
git clone https://github.com/ANAMIZED/YodMCP.git
cd YodMCP
python -m venv .venv && source .venv/bin/activate # recommended
pip install -e ".[dev]"Umgebungsstandards kopieren:
cp .env.example .envVariable | Standard | Bedeutung |
|
|
|
|
| SQLite-Pfad bei durable |
|
|
|
|
|
|
|
| Soft-Quota-Mandantenschlüssel |
| (auto) | Überschreibt das Skills-Wurzelverzeichnis |
| unset | Aktiviert Live-Checkout-Sitzungen |
TEE-Ehrlichkeit:
nitro/sgxsind Provider-Hooks; ohne echte TEE-Bibliotheken fallen sie auf simulierte Ansprüche zurück. Bevorzugen Sie für die lokale Verifizierungsoftwareodersimulated_tee.
Schnellstart (lokal)
# 1) MCP over stdio (attach from an MCP client)
yodmcp
# 2) REST API
yodmcp-api --port 8080
# curl http://127.0.0.1:8080/health
# 3) A2A
yodmcp-a2a --port 9000
# curl http://127.0.0.1:9000/a2a/cardMCP-Client-Konfiguration (stdio)
Cursor – Projekt-.cursor/mcp.json oder globale MCP-Einstellungen:
{
"mcpServers": {
"yodmcp": {
"command": "yodmcp",
"args": [],
"env": {
"YODMCP_MEMORY_BACKEND": "memory",
"YODMCP_PLAN": "free",
"YODMCP_ATTEST_MODE": "software"
}
}
}
}Falls yodmcp nicht im PATH ist, verwenden Sie die Modulform:
{
"mcpServers": {
"yodmcp": {
"command": "python",
"args": ["-m", "yodmcp"],
"cwd": "/absolute/path/to/YodMCP",
"env": {
"PYTHONPATH": "src",
"YODMCP_MEMORY_BACKEND": "memory"
}
}
}
}Claude Desktop – gleiche Form unter mcpServers in claude_desktop_config.json.
Streamable HTTP MCP (Remot-Clients, die URL-Transport unterstützen):
yodmcp --http --host 0.0.0.0 --port 8000
# endpoint: http://127.0.0.1:8000/mcpDocker
docker compose up --build
# API :8080 A2A :9000 MCP HTTP :8000Einzel-API-Container:
docker build -t yodmcp .
docker run --rm -p 8080:8080 -e YODMCP_PLAN=free yodmcpEnde-zu-Ende-Verifizierung (keine externen Konten erforderlich)
# Unit + integration
YODMCP_MEMORY_BACKEND=memory YODMCP_ATTEST_MODE=software \
PYTHONPATH=src pytest tests/ -v
# Durable SQLite + simulated TEE
YODMCP_MEMORY_BACKEND=sqlite YODMCP_MEMORY_DB=/tmp/yodmcp.db \
YODMCP_ATTEST_MODE=simulated_tee \
PYTHONPATH=src pytest tests/ -v
# Exhaustive substrate script
PYTHONPATH=src python scripts/verify_e2e.pyErwartet: alle Tests grün; das Skript gibt ALL E2E CHECKS PASSED aus.
API-Smoke-Test (bei laufendem yodmcp-api):
curl -s http://127.0.0.1:8080/health
curl -s http://127.0.0.1:8080/api/skills
curl -s http://127.0.0.1:8080/api/billing/plans
curl -s http://127.0.0.1:8080/api/billing/statusSDK:
python examples/sdk_quickstart.py # requires API on :8080MCP-Tools (Katalog)
Tool | Beschreibung |
| Einen Speicherknoten einfügen (Fakten/Entscheidungen). Nicht für Pläne ( |
| Knoten nach Ähnlichkeit oder |
| Einen Knoten + zugehörige Kanten endgültig löschen. Idempotent, falls nicht vorhanden. |
| Importanz ≥ 0,8 in semantische Zusammenfassungen überführen. Löscht keine Quellen. |
| Anzahl von Knoten/Kanten/Entitäten. Kein Inhalt ( |
| Ein dauerhaftes Handle für eine anstehende Task erstellen. |
| Ein Handle anhand der ID abrufen. |
| Neueste Handles auflisten, optionaler Statusfilter. |
| Status/Fortschritt/Ergebnis patchen. Nicht abbrechen ( |
| Ein Handle als abgebrochen markieren (nur Kernel-Zustand). |
| Anzahl nach Status. Keine Auflistung ( |
| Agent Skills + |
| A2A-Agent-Card-JSON. Nicht der MCP-Katalog ( |
| Semantische Planvorlagen. Keine Speicherfakten. |
| Summen für Einträge/Treffer des prozessinternen Caches. |
| TRACE-artige Herkunftsansprüche. Nicht der Audit-Trail ( |
| Ereignisse des Decision-System-of-Record für Policy/Tool. |
| MCP-Tools + geladene Skills auflisten. |
| Liveness-Probe ( |
Ressourcen:
skills://{name}— Skill-Markdown-Inhaltyodmcp://agent-card— Agent-Card-JSON
Skills
Eingebaute Skills sind immer registriert. Disk-Skills unter skills/*/SKILL.md werden automatisch geladen (Überschreibung über YODMCP_SKILLS_DIR). Das Repo enthält:
memory-hygiene,safe-tool-use,funding-usdc,repo-bootstrapZusätzlich eingebaut:
long-horizon-planning
Monetarisierung
Plan | $/mo | Tool-Aufrufe/Tag | Dauerhaft | TEE |
Kostenlos | 0 | 500 | — | — |
Pro | 49 | 50k | ja | simuliert |
Enterprise | 499 | unbegrenzt | ja | Nitro/SGX-Hooks |
Soft-Quotas über das Tool-Gate; Upgrade-Hinweise bei Erschöpfung
Live-Stripe-Checkout, wenn
STRIPE_SECRET_KEYgesetzt ist; andernfalls gibt der Checkoutstatus: payment_linkzurück.
Option | Link |
YodMCP Pro | |
YodMCP Enterprise | |
Agentic OS Kernel Support ($99) | |
Public Goods Support ($25) | |
Agentic Systems Consulting Hour ($199) |
Non-Custodial USDC (bevorzugt für Agenten)
Netzwerk | Adresse |
Base |
|
Ethereum |
|
Solana |
|
Kanonisch: funding/addresses.json
Projektstruktur
src/yodmcp/ # package (src-layout)
core/ # server, substrate, context
memory/ # in-memory + durable SQLite multi-graph
tools/ # MCP tool registration + gate
tasks/ skills/ cache/ security/ observability/ monetization/
api/ a2a/ sdk/
skills/*/SKILL.md # portable Agent Skills (loaded at runtime)
scripts/verify_e2e.py
tests/
docs/ARCHITECTURE.md
docs/FOUNDRY.md
docs/TDQS.mdBekannte Einschränkungen (lesen, bevor Sie Produktionsreife beanspruchen)
Plan-Cache verwendet schlanke Embeddings; die standardmäßige Ähnlichkeitsschwelle beträgt 0,68 (keine Produktions-Vektorsuche).
TEE Nitro/SGX sind Hooks mit simuliertem Fallback, sofern Sie keine echten Provider anbinden.
Frontend
src/yodmcp/frontend/dashboard.pyverwendet weiterhin das altecore.runtimeund ist nicht die primäre Steuerungsebene – verwenden Sieyodmcp-api+ MCP-Tools.Quotas sind weich (prozessinterner Zähler); kein verteiltes Abrechnungsbuch.
Prozesse teilen keinen In-Memory-Zustand; verwenden Sie für die Dauerhaftigkeit über mehrere Prozesse hinweg das
sqlite-Backend + ein gemeinsames Volume.
Lizenz
Apache-2.0 · CONTRIBUTING · CHANGELOG · ARCHITECTURE · FOUNDRY · TDQS · AGENTS.md
Available Tools
21 toolsa2a_cardGet A2A Agent CardARead-onlyIdempotent
Return this process's A2A Agent Card JSON (name, skills, endpoints) for agent-to-agent interop. Use when another agent needs the card. Do not use to list MCP tools or skills — that is discover_capabilities or skills_list. Read-only, no parameters, no side effects. Auth: tool policy gate.
Inputs: no named parameters. Returns: object
attestation_recentList recent attestation claimsARead-onlyIdempotent
Return recent attestation claims issued by this kernel (TRACE-style provenance: tool, allow/deny, risk tier, evidence mode). Use to verify a prior sandbox/TEE decision. Do not use for the policy/audit trail — that is audit_recent. This tool does not issue new claims. Read-only. limit is max claims, newest first (default 10). Auth: gate.
Inputs: limit. Returns: object
audit_recentList recent audit eventsARead-onlyIdempotent
Return the newest Decision-System-of-Record audit events (tool calls, policy allow/deny, risk tier, outcome), newest first. Use to inspect what the kernel just decided. Do not use for attestation evidence (attestation_recent) or cache metrics (cache_stats). Read-only. limit caps the list (default 20). Auth: tool policy gate.
Inputs: limit. Returns: object
cache_statsCache statisticsARead-onlyIdempotent
Return entry counts and hit totals for the in-process result/plan cache. Use for diagnostics. Do not use to read a plan (plan_cache_get) or memory (memory_read). Read-only, idempotent, no parameters. Auth: tool policy gate.
Inputs: no named parameters. Returns: object
discover_capabilitiesDiscover tools and skillsARead-onlyIdempotent
List this kernel's MCP tools and loaded Agent Skills, optionally filtered by a substring query. Use at session start or when unsure which tool to call. Do not use to fetch the A2A interoperability card — that is a2a_card — or skill bodies (read skills:// resources after skills_list). Read-only and idempotent. Auth: gate.
Inputs: query. Returns: object
echoEcho a connectivity probeARead-onlyIdempotent
Return the provided message plus server name/version to confirm the MCP session is alive. Use as a liveness probe. Do not use to discover tools (discover_capabilities) or to persist state. Read-only, idempotent, no network I/O, no quota side effects beyond the standard tool gate. message defaults to 'ping'.
Inputs: message. Returns: object
memory_consolidateConsolidate episodic memoryA
Promote high-importance nodes (importance >= 0.8) from from_level into new semantic summary nodes. Use after a burst of memory_write calls to compress working memory. Do not use as a delete — source nodes remain. Mutating, not idempotent (re-running creates additional summaries). Auth: tool policy gate.
Inputs: from_level. Returns: object
memory_deleteDelete a memory nodeADestructiveIdempotent
Permanently delete one memory node and its incident edges/entity index rows. Use when a fact must be forgotten. Do not use to hide a node while keeping it — there is no soft-delete. Destructive and idempotent: missing ids return deleted=false. Prefer memory_read first to confirm the id. Auth: policy gate; may require HITL.
Inputs: item_id (required). Returns: object
memory_readRead memory nodesARead-onlyIdempotent
Retrieve memory nodes by embedding similarity and/or exact item_id, optionally filtered by level, agent, session, or graph kind. Use to recall stored facts. Do not use for reusable plan templates — that is plan_cache_get. Read-only and idempotent. Returns scored items plus neighbor ids. Auth: tool policy gate.
Inputs: graph, level, limit, query, +3 more. Returns: object
memory_statsMemory graph statisticsARead-onlyIdempotent
Return node counts by level plus edge and entity-index sizes for the memory store. Use for capacity/health checks. Do not use to read node content — that is memory_read. Read-only, idempotent, no parameters. Auth: tool policy gate.
Inputs: no named parameters. Returns: object
memory_writeWrite a memory nodeA
Insert one node into the multi-graph memory store (episodic/semantic/procedural) and optionally add causal or entity edges. Use to remember facts, decisions, or session state the host should own. Do not use for reusable task plans — that is plan_cache_put. Mutating and not idempotent: each call creates a new item_id. Gated by plan quota. Nodes with importance >= 0.8 are what memory_consolidate later promotes. Auth: tool policy gate; no network I/O.
Inputs: content (required), level, agent_id, entities, +4 more. Returns: object
plan_cache_deleteDelete a cached planADestructiveIdempotent
Delete the exact plan-cache entry for task_description. Use to drop a stale template. Does not delete memory nodes (that is memory_delete). Destructive and idempotent: missing keys return deleted=false. Auth: tool policy gate.
Inputs: task_description (required). Returns: object
plan_cache_getLookup a cached planARead-onlyIdempotent
Semantic lookup of a previously stored plan template keyed by task_description. Use to reuse a multi-step plan. Do not use to recall facts from memory (memory_read) or to write a plan (plan_cache_put). Read-only. Returns found, similarity score, and plan. Default similarity threshold is 0.68. Auth: tool policy gate.
Inputs: task_description (required). Returns: object
plan_cache_putStore a plan templateA
Store a structured plan template keyed by task_description for later semantic reuse. Use after you have a working plan. Do not use for episodic facts (memory_write). Mutating; same task_description overwrites the exact key. Auth: tool policy gate.
Inputs: plan (required), task_description (required). Returns: object
skills_listList Agent SkillsARead-onlyIdempotent
List loaded Agent Skills with name, skills:// URI, description, and tags. Use to find skill resources to read next. Does not return skill markdown bodies — fetch those via the skills://{name} resource. Do not use for the A2A card (a2a_card). Read-only. Auth: tool policy gate.
Inputs: no named parameters. Returns: object
tasks_cancelCancel a taskADestructiveIdempotent
Mark a task cancelled. Use to stop polling a handle you no longer need. Does not kill an external worker process — it only updates kernel state. Destructive relative to the handle, idempotent if already cancelled. Missing ids return cancelled=false. Prefer tasks_get first. Auth: tool policy gate.
Inputs: task_id (required). Returns: object
tasks_createCreate a durable taskA
Create a durable async task handle (pending) that survives process restart when the sqlite tasks backend is enabled. Use to start long-running work you will poll with tasks_get or list with tasks_list. Do not use to store facts (memory_write) or plans (plan_cache_put). Mutating, not idempotent. ttl_ms controls handle expiry hint. Auth: tool policy gate + plan quota.
Inputs: ttl_ms, metadata, tool_name. Returns: object
tasks_getGet a task by idARead-onlyIdempotent
Fetch one task handle by task_id (status, progress, result, error). Use to poll after tasks_create. Do not use for aggregate counts — that is tasks_stats — or to list many tasks (tasks_list). Read-only and idempotent. Missing ids return task_not_found. Auth: tool policy gate.
Inputs: task_id (required). Returns: object
tasks_listList recent tasksARead-onlyIdempotent
List task handles, newest updated first, optionally filtered by status. Use to recover ids after restart. Do not use to poll a known id (tasks_get) or to mutate state. Read-only and idempotent. Auth: tool policy gate.
Inputs: limit, status. Returns: object
tasks_statsTask store statisticsARead-onlyIdempotent
Return total task count and counts by status for the task store. Use for dashboards. Do not use to read a specific handle (tasks_get) or to list handles (tasks_list). Read-only, idempotent, no parameters. Auth: tool policy gate.
Inputs: no named parameters. Returns: object
tasks_updateUpdate a taskA
Patch status, progress, message, result, or error on an existing task. Use while a worker is running. Do not use to cancel — that is tasks_cancel — or to create a new handle (tasks_create). Mutating; last write wins. Missing ids return task_not_found. Auth: tool policy gate.
Inputs: task_id (required), error, result, status, +2 more. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 21 tools
The tool set is organized into clear subsystems and each description includes explicit 'do not use' cross-references. However, audit_recent and attestation_recent describe very similar recent-decision records, and discover_capabilities vs skills_list vs a2a_card are all discovery-flavored, so a couple of boundaries are easy to blur.
Most memory_, tasks_, plan_cache_, and skills_ tools follow a readable resource_operation pattern. But discover_capabilities, audit_recent, attestation_recent, a2a_card, and echo break that pattern, resulting in a mixed though still understandable naming convention.
With 21 tools, the surface is at the high end and feels heavy for a single server, especially with multiple stats and discovery variants. The broad subsystem coverage justifies most tools, but the overall count is borderline excessive.
The major subsystems have solid lifecycle coverage: memory has write/read/delete/consolidate, plan cache has get/put/delete, and tasks have create/read/list/update/cancel. Minor gaps remain, such as no hard-delete for tasks and no direct update for memory nodes, but agents can work around them.
Maintenance
Related MCP Connectors
Persistent memory, knowledge graph, task management and more for AI agents via MCP.
Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.
Persistent, inspectable memory for AI agents with lineage, correction, and a hosted MCP endpoint.
Agent-native notes, tasks, dev-docs, vaults, sync & handoffs. MCP + OpenAPI dual surface.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables deployment of autonomous AI agents with memory and tool execution capabilities through a WebSocket-based MCP protocol. Provides production-ready infrastructure with REST API access, persistent state management, and extensible function registry for building self-hosted AI systems.-
- AlicenseDqualityDmaintenanceAI-native orchestration layer with 80+ tools for task management, code editing, browser automation, terminal control, and persistent memory across CLI, local MCP, and cloud deployments.697 npm31ISC
- AlicenseNot gradedqualityDmaintenanceFoundational MCP/A2A-native core platform for secure credential injection, native x402 micropayments, and Agent-to-Agent routing.2MIT
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server that equips AI agents with dynamic, persistent, and executable skills. It enables secure script execution and progressive disclosure to reduce context window usage.22 npmMIT