io.github.ANAMIZED/yodmcp

Official registry AI and agents

Autonomous MCP Agent OS: multi-graph memory, Tasks, Skills, A2A, attestation, OpenTelemetry.

What can you do with io.github.ANAMIZED/yodmcp?

  • skills://{name} — skill markdown body
  • yodmcp://agent-card — agent card JSON

Install

The installation steps are in the documentation below. Documentation

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. YodMCP — Agent Operating System
  2. FOUNDRY mapping
  3. Package surfaces
  4. Requirements
  5. Install
  6. Quick start (local)
  7. Docker
  8. Verify end-to-end (no external accounts required)
  9. MCP tools (catalog)
  10. Skills
  11. Monetization
  12. Project layout
  13. Known limitations (read before claiming production)
  14. License

YodMCP — Agent Operating System

YodMCP is a production-oriented Agent Operating System kernel on MCP: multi-graph memory, Tasks, Skills, A2A, attestation (software / simulated TEE), OpenTelemetry, and plan-based monetization.

This README is written so a senior engineer with only this file + the source tree can install, deploy every surface, exercise features, and verify end-to-end.

FOUNDRY mapping

FOUNDRY (host-owned trust and memory for long-horizon agent swarms) separates untrusted proposal generation from host-owned verification + established-facts registry.

YodMCP is that registry in production: agents call memory_write; promotion to semantic memory is gated; the host owns the evaluator. Full note: docs/FOUNDRY.md.

First dollar

Meters first. Seat if the loop holds.

UnitStripex402
OpenGOS Search $0.40BuyGET /v1/search
OpenGOS Draft $2.50BuyGET /v1/draft
Agentic OS Cycle $0.75BuyGET /v1/cycle
YodMCP Pro $49/moSubscribeUSDC

x402 rail: x402-cloudflare-starter. Desk sync: https://anamized.grok.me

Package surfaces

SurfaceCommandDefaultPurpose
MCPyodmcpstdioLocal MCP clients (Cursor, Claude Desktop, etc.)
MCP HTTPyodmcp --http --port 8000:8000/mcpRemote / Streamable HTTP MCP
APIyodmcp-api --port 8080:8080REST health, memory, audit, skills, billing
A2Ayodmcp-a2a --port 9000:9000Agent Card, message, tasks
SDKfrom yodmcp.sdk import YodClientHTTP clientThin client for the API
Skillsskills:// + skills/*/SKILL.mdauto-loadedAgent Skills as MCP resources
Verifypytest + scripts/verify_e2e.pyCISubstrate + durable + TEE modes

Requirements

  • Python 3.11 or 3.12 (3.10+ declared; CI covers 3.11/3.12)
  • Optional: Docker for multi-service compose

Install

git clone https://github.com/ANAMIZED/YodMCP.git
cd YodMCP
python -m venv .venv && source .venv/bin/activate   # recommended
pip install -e ".[dev]"

Copy environment defaults:

cp .env.example .env
VariableDefaultMeaning
YODMCP_MEMORY_BACKENDmemorymemory \sqlite \durable
YODMCP_MEMORY_DB./data/yodmcp_memory.dbSQLite path when durable
YODMCP_ATTEST_MODEsoftwaresoftware \simulated_tee \nitro \sgx
YODMCP_PLANfreefree \pro \enterprise
YODMCP_TENANT_IDdefaultSoft quota tenant key
YODMCP_SKILLS_DIR(auto)Override skills root
STRIPE_SECRET_KEYunsetEnables live Checkout Sessions

TEE honesty: nitro / sgx are provider hooks; without real TEE libraries they fall back to simulated claims. Prefer software or simulated_tee for local verify.

Quick start (local)

# 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/card
MCP client configuration (stdio)

Cursor — project .cursor/mcp.json or global MCP settings:

{
  "mcpServers": {
    "yodmcp": {
      "command": "yodmcp",
      "args": [],
      "env": {
        "YODMCP_MEMORY_BACKEND": "memory",
        "YODMCP_PLAN": "free",
        "YODMCP_ATTEST_MODE": "software"
      }
    }
  }
}

If yodmcp is not on PATH, use the module form:

{
  "mcpServers": {
    "yodmcp": {
      "command": "python",
      "args": ["-m", "yodmcp"],
      "cwd": "/absolute/path/to/YodMCP",
      "env": {
        "PYTHONPATH": "src",
        "YODMCP_MEMORY_BACKEND": "memory"
      }
    }
  }
}

Claude Desktop — same shape under mcpServers in claude_desktop_config.json.

Streamable HTTP MCP (remote clients that support URL transport):

yodmcp --http --host 0.0.0.0 --port 8000
# endpoint: http://127.0.0.1:8000/mcp

Docker

docker compose up --build
# API  :8080  A2A :9000  MCP HTTP :8000

Single API container:

docker build -t yodmcp .
docker run --rm -p 8080:8080 -e YODMCP_PLAN=free yodmcp

Verify end-to-end (no external accounts required)

# 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.py

Expected: all tests green; script prints ALL E2E CHECKS PASSED.

API smoke (with yodmcp-api running):

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/status

SDK:

python examples/sdk_quickstart.py   # requires API on :8080

MCP tools (catalog)

ToolDescription
memory_writeInsert one memory node (facts/decisions). Not for plans (plan_cache_put).
memory_readRetrieve nodes by similarity or item_id. Not for plans (plan_cache_get).
memory_deleteHard-delete one node + incident edges. Idempotent if missing.
memory_consolidatePromote importance ≥ 0.8 into semantic summaries. Does not delete sources.
memory_statsNode/edge/entity counts. Not content (memory_read).
tasks_createCreate a durable pending task handle.
tasks_getFetch one handle by id.
tasks_listList recent handles, optional status filter.
tasks_updatePatch status/progress/result. Not cancel (tasks_cancel).
tasks_cancelMark a handle cancelled (kernel state only).
tasks_statsCounts by status. Not a listing (tasks_list).
skills_listList Agent Skills + skills:// URIs (bodies are resources).
a2a_cardA2A Agent Card JSON. Not the MCP catalog (discover_capabilities).
plan_cache_get / plan_cache_put / plan_cache_deleteSemantic plan templates. Not memory facts.
cache_statsIn-process cache entry/hit totals.
attestation_recentTRACE-style provenance claims. Not the audit trail (audit_recent).
audit_recentPolicy/tool Decision-System-of-Record events.
discover_capabilitiesList MCP tools + loaded skills.
echoLiveness probe (message echoed + version).

Resources:

  • skills://{name} — skill markdown body
  • yodmcp://agent-card — agent card JSON

Skills

Built-in skills are always registered. Disk skills under skills/*/SKILL.md are loaded automatically (override via YODMCP_SKILLS_DIR). Repo ships:

  • memory-hygiene, safe-tool-use, funding-usdc, repo-bootstrap
  • Plus built-in long-horizon-planning

Monetization

Plan$/moTool calls/dayDurableTEE
Free0500——
Pro4950kyessimulated
Enterprise499unlimitedyesNitro/SGX hooks
  • Soft quotas via tool gate; upgrade messaging on exhaustion
  • Live Stripe Checkout when STRIPE_SECRET_KEY is set; otherwise checkout returns status: payment_link
Non-custodial USDC (preferred for agents)
NetworkAddress
Base0xD3d0E9eDAe3Ac7bb199a8EAA761BdA423b878438
Ethereum0xD3d0E9eDAe3Ac7bb199a8EAA761BdA423b878438
SolanaETQwWf19axArsY493UfC6bxe2BmEzmzvCb58PPnC38A

Canonical: funding/addresses.json

Project layout

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

Known limitations (read before claiming production)

  1. Plan cache uses lightweight embeddings; default similarity threshold is 0.68 (not production vector search).
  2. TEE Nitro/SGX are hooks with simulated fallback unless you wire real providers.
  3. Frontend src/yodmcp/frontend/dashboard.py still uses legacy core.runtime and is not the primary control plane — use yodmcp-api + MCP tools.
  4. Quotas are soft (in-process meter); not a distributed billing ledger.
  5. Processes do not share in-memory state; use sqlite backend + shared volume for multi-process durability.

License

Apache-2.0 · CONTRIBUTING · CHANGELOG · ARCHITECTURE · FOUNDRY · TDQS · AGENTS.md

Frequently asked questions

What is io.github.ANAMIZED/yodmcp?

Autonomous MCP Agent OS: multi-graph memory, Tasks, Skills, A2A, attestation, OpenTelemetry.

How do I install io.github.ANAMIZED/yodmcp?

Follow the installation steps in its documentation, shown on this page and in its repository.

Is io.github.ANAMIZED/yodmcp open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains io.github.ANAMIZED/yodmcp?

It is published by ANAMIZED. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.