Proofpane
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Proofpane Daemon: local-machine tools (bash, fs, etc.) exposed via MCP. All calls are governed by the Proofpane Orchestrator policies the user has configured.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bashC | Execute a bash command in the project directory. Output is captured and truncated. |
| readB | Read a file from the project directory. Path traversal is blocked. |
| writeB | Write content to a file (overwrites). Parent directories are created. |
| editB | Replace one occurrence of old_string with new_string in a file. |
| globC | Find files matching a glob pattern under the project. |
| grepB | Search for a regex pattern in files (uses system grep -r -n). |
| listdirC | List contents of a directory. |
| search_compliance_docsA | Search the Proofpane governance / compliance document corpus via the cloud RAG service. Returns the top N matching chunks with source + relevance score. Default collection + retrieval method come from this agent's rag_config (configured in the Proofpane UI); override per-call with the |
| ingest_to_ragA | Upload a LOCAL file into the Proofpane governance RAG corpus. The cloud parses it (PDF / DOCX / HTML / text), DLP-scrubs secrets, chunks + embeds it, and audits the ingest. After this, the file's contents are searchable with search_compliance_docs on the returned collection. Use when the user wants a local document made available for governed retrieval / Q&A. |
| session_searchA | Search + recall past Hermes conversations (governed). Discovery: pass |
| skills_listA | List available Hermes skills (name + description + category), governed. Optional |
| skill_viewB | Read a skill's full SKILL.md (and linked reference/template/script files via |
| skill_manageA | Create / edit / patch / delete a skill, or write/remove a skill's linked file (governed — every write is policy-gated + audited). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
The tool set splits into clearly separate families: project file ops (read/write/edit/bash/glob/grep/listdir), governed skill management (skill_manage/skills_list/skill_view), session recall, and RAG ingest/search. Within each family the boundaries are sharp, though bash overlaps with every filesystem tool by nature, and listdir vs glob is a minor gray area; skill_view vs read is also mildly adjacent.
Conventions are mixed: bare verbs/nouns (bash, read, write, edit, glob, grep, listdir) sit alongside noun_verb pairs (skill_manage, skill_view, skills_list, session_search) and verb_noun RAG tools (ingest_to_rag, search_compliance_docs). Every name is readable, but the skill family flips order (skill_manage vs skills_list) and there is no single predictable pattern.
13 tools is squarely in the well-scoped range, and each one earns its place by covering a distinct capability (working the repo, managing skills, recalling sessions, ingesting/searching governed docs). Nothing looks redundant or speculative.
The surface is nearly complete: file read/write/edit/search/exec, full skill lifecycle (create/edit/patch/delete/list/view), session recall, and RAG ingest + search. The main gaps are no dedicated delete/rename/move file tool and session recall being search-only, both workable via bash.