agentprivacy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VTA_MODE | No | Set to '1' to hide development-only tools (e.g., compare_plain). | |
| AGENTPRIVACY_GUIDE_SITE | No | Directory of the agent privacy guide site (defaults to the package's site directory). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| guide_searchA | Search the guide (the baked fedwiki federation, 20 sites). Returns an ORDERED WALK of pages — BM25 over the baked lexical index, then link-graph expansion — each step with its site, slug, lattice vertex and PSI element. The agent reads the bake, never the live farm, so a walk is reproducible. |
| guide_pageA | One page by slug (site optional — identity is the slug, never the host): its text, weave (links), lattice vertex + six-bit posture, PSI element and public URL. |
| guide_neighboursD | Linked pages (outgoing and backlinks) of a page, each with the NAMED LATTICE MOVE from this page to it: succ · neg · bnot · flip · jump ×k (dimensions), per the 64-vertex sovereignty lattice. |
| lattice_moveA | Apply a lattice operator to a vertex (0-63): succ (the wheel, +1 mod 64), neg (Swordsman reflection, 64−x), bnot (Mage antipode, 63−x), "flip " (one bit), or "to " (names the move). Returns the resulting vertex, its six bits (d1 protection … d6 value), dimensions, stratum, and a derived reading. |
| key_deriveC | Law L5 — a κ is never trusted, only re-derived. Canonical form (keys sorted recursively, no whitespace, kappa excluded) → sha256 → compare with the stamped κ. Accepts a City Key JSON or a sigil PNG (the image carries the key). Returns verdict, derived κ, prior, the 64 glyphs, lit and walked vertices. |
| key_evolveA | Append a walk to a City Key — pure and deterministic. Walk = an array of {site?, slug} steps (or slugs), a pathway.v1, or a star-chart constellation. Each step is resolved against the bake to its vertex and PSI element; the evolved key gains walks[], prior = κ of the key it grew from, and a fresh κ. UNSIGNED — a Swordsman signs (Rung 1). Omit key to start from the default key. |
| sigil_renderC | Draw the key's sigil — 64 glyphs, one per vertex, lit by the RE-DERIVED κ (never the stamped claim), coloured by the key's palette by stratum; lit vertices ring coral, walked vertices ring cyan — as a PNG that CARRIES the key (tEXt cityKey), importable on soulbis.com/star, /lattice, /sigil. Returns the image; writes it to |
| key_verifyA | Verify a signed VTA record (kind agentprivacy.vta/1: bearer public key, κ, prior, at, walks, vrcs, ed25519 sig) — and, when the key is given, that the record names THIS key (L5: κ re-derived from the key equals the signed κ). Accepts the record as JSON or a sigil PNG carrying a cityKeySig chunk. With |
| card_verifyA | Verify an AgentCard as agentprivacy /ceremony signs it (ed25519 over the card payload; participantId = ap-<16 hex of the public key>). Returns participantId, did:key, displayName, trustTier, Drake Orb tier. This is the identity mages.city admits with; the board never re-issues it. |
| compare_plainB | The ∩ of two keys (walked + lit vertices, shared PSI elements) computed IN THE OPEN by reading both keys. Development only: Rung 3 replaces it with DH-PSI, and it is hidden when VTA_MODE=1. |
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 10 tools
Each tool targets a distinct operation: key derivation, guide search/page/neighbours, lattice moves, key evolution, sigil rendering, key and card verification, and a dev-only comparison. The descriptions clearly separate overlapping functions like key_derive vs key_verify.
Most tools follow noun_verb (key_derive, guide_search, lattice_move), but guide_page and guide_neighbours are noun_noun and compare_plain is verb_adj. The mix is still readable but not uniformly consistent.
10 tools is well-scoped for the domain: 5 key-related, 3 guide-related, 1 lattice, 1 card verification. Each tool earns its place without redundancy.
Covers key lifecycle (derive, evolve, verify, render), guide exploration (search, page, neighbours), and lattice operations. Missing explicit signing, but that is described as an external Swordsman step, and dev-only compare_plain is clearly marked.