Since
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SINCE_HOME | No | Override the default config directory (~/.since) for every Since process. The MCP server reads from this directory, so it must match the daemon's SINCE_HOME. |
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 |
|---|---|
| sinceA | What changed in the watched sources since you last acknowledged. Returns a ranked, token-budgeted plain-text digest, most important first; every line ends with a handle for get(). Does not move your cursor: after handling the events (including any |
| getB | Drill into a handle from a since() digest: since://evt/ = one event with all changed fields; since://rec// = the record's current (or last known) fields; since://batch/-?source= = events left out of the digest (follow the |
| ackA | Mark all events up to and including |
| statusB | Health of each source (last success, current error, record count) and of the collecting daemon. |
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 4 tools
Each tool has a distinct role in the workflow: since() produces a digest, get() retrieves details from handles, ack() advances the cursor, and status() reports source health. The descriptions clearly delineate boundaries, and the complementary read-then-ack pattern prevents confusion.
All names are single lowercase words, which is readable, but they mix parts of speech: since is a preposition, get and ack are verbs, and status is a noun. There is no consistent verb_noun or action-oriented pattern.
Four tools perfectly match the narrow purpose of tracking changes: read digest, drill into details, acknowledge, and check health. Each tool is necessary and there is no redundancy or bloat.
The surface covers the full lifecycle: discovering changes (since), inspecting them (get), marking them handled (ack), and monitoring source health (status). No CRUD operations are needed for this read-only monitoring domain, so there are no obvious gaps.