devops-status-mcp-server
by cyanheads
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOGS_DIR | No | Directory for log files (Node.js only). | <project-root>/logs |
| OTEL_ENABLED | No | Enable OpenTelemetry instrumentation. | false |
| MCP_AUTH_MODE | No | Auth mode: none, jwt, or oauth. | none |
| MCP_HTTP_PORT | No | Port for HTTP server. | 3010 |
| MCP_LOG_LEVEL | No | Log level (RFC 5424). | info |
| MCP_TRANSPORT_TYPE | No | Transport: stdio or http. | stdio |
| DEVOPS_STATUS_CACHE_TTL_MS | No | In-memory cache TTL for vendor status reads (all backends) in milliseconds. | 60000 |
| DEVOPS_STATUS_DNS_TIMEOUT_MS | No | Default timeout_ms for devops_check_dns (per domain+resolver query, milliseconds). A caller-passed timeout_ms overrides it. | 3000 |
| DEVOPS_STATUS_CERT_TIMEOUT_MS | No | Default timeout_ms for devops_check_certs (per-domain TLS handshake, milliseconds). A caller-passed timeout_ms overrides it. | 5000 |
| DEVOPS_STATUS_FETCH_TIMEOUT_MS | No | Per-request timeout for vendor status API calls (all backends) in milliseconds. | 8000 |
| DEVOPS_STATUS_ALLOW_PRIVATE_TARGETS | No | When true, disables SSRF guards for user-supplied URLs and domains. For trusted local/intranet deployments only. | false |
| DEVOPS_STATUS_DISABLE_ACTIVE_PROBES | No | When true, omits the arbitrary-target probe tools from the registered tool surface; the five vendor-registry/incident tools remain. For shared/public multi-tenant instances. | false |
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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cyanheads/devops-status-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server