truecopy
Server 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.
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| truecopy-verifyA | Re-derive the hash of every skill and MCP server pinned in this truecopy lock and report whether each still matches what was vetted. Use this before trusting a tool surface, or to answer "has anything changed underneath me?". Each entry comes back as one of: ok (bytes identical to what was pinned), drifted (content changed since it was vetted), poisoned (re-scan found an injection or exfiltration pattern), untrusted (signed by a key that is not in the trust store), unsigned (a signature was required but is absent), or missing (the pinned source is no longer on disk). Read-only: it never re-pins, never edits the lock, and never fetches anything over the network. |
| truecopy-statusA | List what this truecopy lock pins, without re-verifying it. Returns each entry with the kind of artifact (skill, mcp, or file), the scan verdict recorded at pin time, and whether it carries a signature. Use this to see the vetted set at a glance — what an agent is permitted to run — or to confirm the gate is reading the lock you expect. For whether those bytes are still unchanged, call truecopy-verify instead. Read-only. |
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 2 tools
The two tools have completely distinct purposes: one verifies integrity of pinned items, the other lists them without verification. No overlap or ambiguity.
Both tools follow a consistent 'truecopy-' prefix with a verb-noun pattern (truecopy-verify, truecopy-status).
With only 2 tools, the server is tightly scoped to its read-only verification and listing purpose. No unnecessary tools.
The server covers the full lifecycle of reading and verifying a truecopy lock. It explicitly omits write operations, which is appropriate given its read-only nature.