proximo MCP server

READ-ONLY: WHO changed WHAT and WHEN — guest configuration changes and every other audited action, read back from the PROVE ledger. Newest first. This is how you answer "who changed this guest" or "what has this caller done". `matched` counts entries passing your filters, `total` counts the whole ledger, and `truncated` says so when `limit` cut rows. An entry with no principal returns null plus a note: the ledger not capturing an identity is a fact about the log, never a claim that nobody was responsible. This READS the chain; `audit_verify` PROVES it is intact.

Verify the tamper-evident audit ledger's hash chain — PROVE the log is intact. Pass `expected_head` (the head() value you pinned off-box) to also catch tail truncation, a forged tail-append, or a full file replacement — a forward walk alone can't see those. Falls back to PROXIMO_AUDIT_EXPECTED_HEAD when omitted.

Call any Proximo tool by exact name, including ones not in this server's listed tools. Get the argument shape from proximo_tool_schema first. Same gates as calling it directly: dry-run PLAN, ledger entry, token ACL. A smaller doorway, not a looser one.

Search Proximo's full tool catalog by keyword. ESTATE QUESTIONS FIRST: if the question is what exists, how many, what changed, or when something last happened, call proximo_recall instead — it answers from local memory in one call, with no search and no schema lookup, and it stamps how old the answer is. Come here for everything else. The facade is resident; 906 more tools on this server are searchable but not. Search for what you want ("guest power", "ceph pool", "firewall"), then call proximo_tool_schema on a result to get its arguments, then proximo_read (read-only tools) or proximo_call to run it. All terms must match.

READ-ONLY: run a read-only Proximo tool by exact name; refuses anything that can mutate (use proximo_call for those). Same flow: get the shape from proximo_tool_schema first.

READ-ONLY: the estate map from local Tier-1 memory — NOT a live PVE read. Returns total/by_kind/by_status/guest_summary counts (trust guest_summary for guest-count questions; all counting is server-side) plus lean entity rows, stamped {source:'memory', as_of, age_seconds}: the data is as old as the stamp says. With `since`, also diffs: appeared, status_changed, and not_seen_since (last observed before the window — a fact, not a claim the entity is gone). journal=N adds the newest N diagnosis digests ("when did this last happen") — findings summaries only, never raw diagnostic output. Memory is on by default (PROXIMO_MEMORY=0 opts out), fed opportunistically by list reads and diagnose/doctor runs, derived and rebuildable. For live state use pve_list_guests / pve_cluster_resources.

Full description + JSON input schema for one tool found via proximo_find_tools.