MCP quick start

Machine catalogue and restrictions

Endpoint

From any command line

A plain REST convenience layer sits beside the MCP endpoint. Same evaluator, same telemetry, same rate limits. No JSON-RPC, no client library - just GET requests with query parameters. Pass the section as a paragraph number (e.g. 211) or by id (e.g. Murder), and every other query parameter is treated as a variable assignment (Name=true|false|unknown or a numeric value).

curl "https://operome.dev/api/evaluate?section=211&KillsPerson=true"

curl "https://operome.dev/api/sections"

curl "https://operome.dev/api/evaluate?mode=machine&section=202a&WithoutAuthorisation=true&DataNotIntendedForActor=true&SpeciallySecured=true&StoredNonPerceivably=true&goal.ObtainsAccessForSelf=true&goal.OvercomesAccessProtection=true&authorization=not_authorised"

Returns {section, rule, result, derivation, facts, missing, escalations} as JSON. For the section list: {sections: [{id, ref, title_en, chapter}, ...]}.

Machine mode keeps legal attribution separate, evaluates conduct without treating an AI as a natural person, accepts structured goal facts using thegoal. prefix, and returns an enforcement decision. Goal facts cannot satisfy human subjective legal elements; those are returned asnot_assessed_for_machine. Bothblock andescalate are non-executable; only a positively authorised action with a determined negative material result can be allowed. Public API authorization assertions are unverified and cannot grant an allow; an enforced deployment must verify authority in an external capability broker.

• rule — the composite's expression string (the top-level boolean rule).
• derivation — an annotated tree rooted at the composite. Operator nodes carry op, value and satisfying_children; fact leaves carry a state of supplied_true, supplied_false, unknown_needed or unknown_moot.
• facts — the leaves grouped by relevance: supplied, unknown_needed (only when the result is unknown) and unknown_not_required. Relevance is computed generically by a pivotal test, so a fact never required is never reported as missing.
• missing — now the pivotal unknowns only (equals facts.unknown_needed), not every unsupplied variable.
• escalations — each {note, element?}, with element naming the variable it attaches to when it derives from one.

Claude Code

{
  "mcpServers": {
    "stgb-operome": {
      "transport": {
        "type": "http",
        "url": "https://operome.dev/mcp"
      }
    }
  }
}

Codex (OpenAI)

{
  "mcp": {
    "servers": {
      "stgb-operome": {
        "url": "https://operome.dev/mcp",
        "headers": { "Accept": "application/json, text/event-stream" }
      }
    }
  }
}

curl — list tools

curl -X POST 'https://operome.dev/mcp' \
  -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

curl — evaluate a section

curl -X POST 'https://operome.dev/mcp' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{
    "jsonrpc": "2.0", "id": 1, "method": "tools/call",
    "params": {
      "name": "stgb_evaluate",
      "arguments": {
        "id": "AbuseOfPersonUnderCare",
        "facts": {
          "VictimUnderEighteen": "true",
          "UnderCare": "true",
          "Torments": "true"
        }
      }
    }
  }'

Tools reference

stgb_search accepts English or German terms in any order. German titles and statutory discovery text are generated in the public StGB Operome repository from a checksum-pinned official XML snapshot at gesetze-im-internet.de, then bundled with this application. Search makes no request to the government site or another remote service. The versioned source, manifest and checksum are public. Results return both title_en and title_de. Search identifies candidate sections only. The section's encoded scope and evaluation output remain authoritative for what the Operome actually evaluates.

Request an API key

Single field, no account, no password. We email your key once. Anonymous use does not require this — it only raises your rate limit to 600 requests/min.