two-minds-one-lock
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRACER_LOCK_LENGTH | No | Lock code length (default likely 4). | |
| TRACER_LOCK_ALPHABET | No | Alphabet of glyphs used in the lock. | |
| TRACER_LOCK_MAX_ATTEMPTS | No | Maximum number of attempts before lockout. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| observe_systemA | Read the lock before acting: the glyph alphabet, the code length, your remaining attempt budget, the diagnostics legend, and your probe history. Call this first -- it costs nothing. |
| probeA | Reconnaissance. Test a candidate code -- a string of glyphs from the alphabet, exactly code_length long. Returns ALIGNED (correct glyph in the correct slot) and DISPLACED (correct glyph in the wrong slot) counts. Costs one attempt. A probe NEVER opens the lock; it only gathers information. Probe to deduce the secret. |
| submit_solutionA | Commit to a final answer. Opens the lock if 'answer' is exactly the secret code; otherwise costs one attempt and returns only a rejection -- no diagnostics. Submitting before you have deduced the code wastes the budget. Probe first; submit once confident. |
| get_statusA | Lightweight check: attempts remaining, whether you are locked out, whether the lock is open, and how many probes/submits you have spent. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/presspausegarage/two-minds-one-lock'
If you have feedback or need assistance with the MCP directory API, please join our Discord server