histor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HISTOR_PROFILE | No | Set to 'prod' to run in production mode; requires Postgres configuration. Default is development mode. | |
| HISTOR_CRAWL_LIMIT | No | Limit for crawling endpoints when running the crawl command (e.g., 40). | |
| HISTOR_PUBLIC_BASE | No | Public base URL of the service. Required when HISTOR_PROFILE=prod. | |
| HISTOR_OPERATOR_TOKEN | No | Token for operator access. Required when HISTOR_PROFILE=prod. | |
| HISTOR_POSTGRES_PASSWORD | No | Password for the Postgres database. Required when HISTOR_PROFILE=prod. |
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 |
|---|---|
| histor_changesB | The newest tool-definition changes HISTOR observed at remote MCP endpoints in the official registry: which tools were added, removed or modified, any outside address (host, e-mail, IP) that newly appeared, and a link to each full diff. |
| histor_checkA | Send an MCP endpoint (or registry name) and the tools/list you received, or its MTL/1 digest. Returns, signed: whether HISTOR observed the same set there, since when, earlier sets, the WARDEN pattern matches for it, and the stored advisory classifier verdict if HISTOR has one (any language; one model's opinion, not a log label). Says what was advertised, never that a server is safe. |
| histor_serverC | HISTOR's observation record for one MCP endpoint (or every endpoint of a registry name): tool-set digest, tool count, first pinned, last observed, unchanged since, change count and last status, with links to the full record and its labels. |
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 targets a distinct aspect of MCP endpoint observation: a global recent-changes feed, a verification check against a supplied tools list, and a stored per-endpoint record. The check and server tools overlap somewhat in returning historical observation details, but the need to supply a digest versus retrieving a record distinguishes them.
All three tools share the consistent 'histor_' prefix followed by a single noun/verb, with no mixing of styles (e.g., histor_changes, histor_check, histor_server). The pattern is predictable and readable.
Three tools is well-scoped for a focused, read-only history/monitoring service, with each tool covering a distinct workflow (recent changes, verification, record lookup). No bloat or thinness.
The surface covers the core read-only operations: global change feed, endpoint record retrieval, and verification of a supplied tools list. Minor gaps exist—no direct per-endpoint change listing or endpoint/registry enumeration tool—but agents can work around these via the global changes feed or record links.