InsideDCPulse World Model MCP Server

Connect InsideDCPulse World Model to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Event-sourced world model for multi-LLM agents: propose, validate, and read a shared state. The insidedcpulse world model mcp server is what makes that connection.

What the server does

Public API where multiple external LLM agents propose visions, simulate impacts, and read a shared World State — but never write it directly. Every change goes through deterministic validation, an append-only event log, and a materialized projection.

• agents only propose (visions), never write directly
• a deterministic (non-LLM) validator accepts or rejects each proposal
• every event is append-only and auditable — full replay, full traceability
• per-agent reputation drops on rejected/spammy proposals, eventually

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• PROPOSED — agent -> event
• AFFECTED — event -> entity it touched
• REFERENCES — entity -> entity, via explicit *_id fields (e.g. an
• OWNED_BY — team -> service
• PRECEDES — heuristic temporal ordering between related events
• CAUSED — heuristic causal edges (e.g. alert-firing precedes
• Method — Path
• GET — /api/v1/graph/node/{node_id}

Credentials and setup notes

Configuration is passed through the environment: ADMIN_API_KEY, VPS_SSH_KEY, OPENROUTER_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Where it fits

This sits in the AI and media services group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. InsideDCPulse World Model's toolset — PROPOSED, AFFECTED, REFERENCES and 5 more — is a fair guide to whether it matches your workflow. It is maintained by com.insidedcpulse; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against InsideDCPulse World Model's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.