status-check
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | MCP listener host | 0.0.0.0 |
| PORT | No | MCP listener port | 3000 |
| TICK_MS | No | How often the worker looks for due providers (each provider is polled every 60 s) | 15000 |
| USER_AGENT | No | Sent to status pages. Add a contact URL if you run a public instance. | status-check/0.1 |
| CACHE_TTL_MS | No | The MCP server answers current-state questions from an in-memory snapshot reloaded at most this often | 15000 |
| DATABASE_URL | Yes | Postgres connection string (required). The worker and the MCP server share one Postgres database. | |
| ALLOWED_HOSTS | No | Hostnames the MCP server answers to (DNS-rebinding protection) | |
| POLL_CONCURRENCY | No | Parallel requests per tick | 16 |
| REQUEST_TIMEOUT_MS | No | Per-request timeout | 10000 |
| MCP_USE_ANONYMIZED_TELEMETRY | No | mcp-use's own anonymous telemetry, off unless you set true | false |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues