Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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.

signafAIde: Signed, tamper-evident records of what an AI agent decided and did, kept on this machine; nothing is sent until a person opts in. Use when the user asks to audit, log or trace AI or agent decisions, needs an audit trail, tamper-evidence or compliance evidence, or builds an agent whose tools pay, send, approve, delete or change real things. Start with signafaide_setup (a preview that changes nothing).

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
signafaide_setupA

Signed, tamper-evident records of what an AI agent decided and did, kept on this machine; nothing is sent until a person opts in. Use when the user asks to audit, log or trace AI or agent decisions, needs an audit trail, tamper-evidence or compliance evidence, or builds an agent whose tools pay, send, approve, delete or change real things. A preview: it changes no file, creates nothing and sends nothing. Returns the detected language, package manager and framework, the exact install command, the code edit for this framework, the functions that look like actions, and what a sandbox would send. Make the edit yourself, run the agent, then call signafaide_verify.

signafaide_initA

Creates an external sandbox project on the signafAIde service (or the SIGNAFAIDE_URL witness), saves its API key to .env and returns the claim link, what claiming gives and when an unclaimed sandbox is deleted. From then on record hashes (never content) are sent there, and records written earlier ship with their original times. This is an external side effect: ask the user and call it only after they agree. Without it, records stay local and still verify. Creating a sandbox means the user agrees to the signafAIde Terms and Privacy notice (/legal/terms and /legal/privacy, where is SIGNAFAIDE_URL or the signafAIde service): show them both links when you ask, and pass on the notice this tool returns. It creates nothing unless confirm_user_agreed is true and user_words holds what the user wrote when they agreed.

signafaide_quickstartA

Returns the install command, the canonical code to record an agent's tool calls with signafAIde, and the verify command, for one language and framework.

signafaide_verifyA

Checks every record in the project's .signafaide/ folder (or a verification pack): schema, hashes, agent signatures, chain links and content hashes, and, for records a witness has co-signed, Merkle proofs, the service's batch and head signatures, drand and anchors. With an API key it first ships waiting records; without one nothing is sent. Returns one line per check, what still needs the witness, and PASS or FAIL.

signafaide_statusB

API key and env, the service URL, each agent chain with its record count and last receipt, records waiting in the outbox, the quota, and the claim link with how long an unclaimed sandbox has left.

signafaide_explain_errorA

What a signafAIde error code means and how to fix it, e.g. chain_conflict, quota_exceeded, invalid_key, network, not_recorded.

signafaide_claim_linkA

The link the human opens to claim this project's free sandbox and keep its records, what claiming gives and how long an unclaimed sandbox has left. Show it to the user; do not open it yourself.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation3/5

signafaide_setup and signafaide_quickstart overlap heavily: both return an install command plus framework-specific integration code, differing mainly in that setup also detects the stack and previews actions. The claim link is surfaced by three tools (claim_link, status, and init's return), creating further boundary blur. init vs setup is at least clarified by descriptions (init is the real side-effecting call, setup is a read-only preview).

Naming Consistency4/5

Every tool uses the signafaide_ prefix with snake_case, which is predictable and easy to scan. Minor deviation: some names are verbs (verify, setup, init) while others are nouns (status, claim_link), but the meaning stays clear.

Tool Count5/5

Seven tools is well-matched to the scope: preview, initialize, quickstart, status, claim link, verify, and error explanation. Nothing feels padded, and no obvious operation is crammed into an overloaded tool.

Completeness3/5

The lifecycle of onboarding and verification is covered, but there is no tool to read, list, or search the actual recorded events, and no explicit way to ship pending outbox records (it happens implicitly inside verify). Rekey/rotate, unclaim/revoke, and cleanup of local .signafaide state are also absent, leaving a few dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues