iptime-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IPTIME_ROUTERS | No | JSON array of router profiles for multi-router configuration. Use username_env and password_env to reference environment variable names containing credentials. The referenced credential environment variables must also be set. | |
| IPTIME_ROUTER_ID | No | Profile name exposed as router_id. | default |
| IPTIME_ROUTER_URL | No | Router base URL using http or https. Required for single-router configuration. | |
| IPTIME_TIMEOUT_MS | No | Request timeout in milliseconds, clamped to 1000-60000. | 12000 |
| IPTIME_ROUTER_PASSWORD | No | Router administrator password. Required for login in single-router configuration. | |
| IPTIME_ROUTER_USERNAME | No | Router administrator username. Required for login in single-router configuration. | |
| IPTIME_TLS_FINGERPRINT | No | SHA-256 certificate fingerprint, with or without colons, checked in addition to normal TLS validation. | |
| IPTIME_ALLOW_INSECURE_REMOTE_HTTP | No | Allows plain HTTP when the hostname resolves to a public address. Set to 'true' to enable. | 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| iptime_statusA | Detect the router interface, authenticate if configured, and read product/system status. |
| iptime_loginA | Authenticate using credentials from the MCP environment. Credentials are never accepted as tool arguments. |
| iptime_logoutA | End the router admin session. |
| iptime_capabilitiesA | Discover which catalogued operations this model and firmware actually expose. |
| iptime_list_operationsA | List the fixed, auditable operation catalog. This does not contact the router. |
| iptime_readA | Run a read-only operation from iptime_list_operations. |
| iptime_backup_configB | Download the current router configuration to a new local .config file. Existing files are never overwritten. |
| iptime_plan_changeA | Create an expiring immutable plan for a router change. No setting is changed by this tool. |
| iptime_plan_firmware_upgradeA | Hash a local firmware file and create a critical-risk upgrade plan. No upload occurs yet. |
| iptime_plan_config_restoreB | Hash a local ipTIME configuration backup and create a critical-risk restore plan. |
| iptime_apply_changeA | Apply exactly one pending plan. No confirmation token or repeated plan id is required. |
| iptime_cancel_changeB | Cancel a pending change plan. |
| iptime_list_plansB | List plans and their current state. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| configuration | Configured router profiles with all credentials omitted |
| operation-catalog | Fixed router operation catalog and risk classification |
TDQS
Scored across 13 tools
Most tools are clearly separated by lifecycle stage: plan, apply, cancel, list, and read-only discovery. Minor overlap exists between iptime_plan_change and the specialized firmware/config plan tools, and between iptime_read, iptime_status, iptime_capabilities, and iptime_list_operations, but descriptions make the boundaries understandable.
All tool names use a consistent iptime_ prefix and snake_case, which makes the set predictable. Most follow verb_noun patterns, with minor deviations such as iptime_status, iptime_login, iptime_logout, iptime_capabilities, and iptime_read.
The server has 13 tools, which is well within a focused and manageable range. Each tool appears to earn its place by covering a distinct part of the safe planning, authentication, discovery, and read-only operation lifecycle.
The surface covers the important router-management lifecycle: discovery, authentication, read operations, backup, planning, applying, cancelling, and listing plans, including critical firmware and restore flows. Minor gaps may exist around explicit plan inspection or firmware upload visibility, but core workflows appear covered.