Ephemora Cell MCP
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 | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| clockA | Returns the current UTC time (ISO-8601 with milliseconds) and the Unix epoch in milliseconds. Reads only the WASI real-time clock inside the sandbox - no filesystem, no network, no environment access; the call is fuel-metered and reported via _meta.execution. |
| echoA | Echoes the tool arguments back as JSON. Demonstrates the Ephemora Cell MCP stdin/stdout contract: receives {"params": ...} on stdin and writes a single JSON value to stdout. |
| get-policyA | Returns the effective sandbox policy for Cell tools ("Verified. Not claimed."): fuel budget, memory limit, threads, preopens (configured), network policy and the security baseline incl. wasmtime version. Pass {"tool": ""} for one tool or no arguments for the whole registry. |
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 3 tools
Each tool has a clearly distinct purpose: clock reports time, echo echos input, and get-policy returns sandbox configuration. There is no meaningful overlap or ambiguity between them.
All names are lowercase and readable, but they mix a noun command (clock), a bare verb command (echo), and a hyphenated verb-noun command (get-policy). A uniform verb_noun pattern would be more consistent.
Three tools is minimal but each one serves a distinct purpose in the apparent sandbox/contract demo scope. The set feels slightly thin but not unreasonably so.
For a focused introspection and contract-demonstration server, the core surfaces are covered: time, I/O behavior, and policy. There are minor gaps like no policy mutation or execution tool, but no obvious dead ends within the stated purpose.