mcp-live-telemetry
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesA | List every simulated machine with its latest reading and state. Returns { count, devices: [{ id, name, state, temperature_c, vibration_mm_s, timestamp }] }. Read only. Use this first to discover valid device ids for the other tools. |
| get_telemetryA | Return time ordered sensor readings for one device across a time window. Inputs: device_id (required), start and end (epoch ms, optional, default last 15 minutes), step_ms (default 30000), limit and offset for pagination, response_format. Returns { device_id, start, end, step_ms, total, count, offset, has_more, next_offset?, readings: [{ timestamp, temperature_c, vibration_mm_s, state }] }. Read only. |
| get_anomaliesA | Detect threshold crossings (temperature or vibration) over a time window. Inputs: device_id (optional, omit to scan all devices), start and end (epoch ms, optional, default last 15 minutes), step_ms (default 30000), response_format. Returns { count, window, anomalies: [{ id, device_id, metric, started_at, ended_at, peak_value, threshold, sample_count }] }. A healthy machine returns no anomalies. Read only. |
| simulate_faultA | Inject a fault on a device so it becomes visible to get_telemetry and get_anomalies. Inputs: device_id (required), fault_type ('overheat' | 'vibration' | 'combined', default 'overheat'), duration_seconds (default 300). The fault is treated as having started two minutes ago so it appears immediately in recent telemetry. Returns { fault: { id, device_id, type, started_at, ends_at, duration_ms }, message }. This tool mutates simulator state; it is not read only. |
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/Younes-Alaoui-Ismaili/mcp-live-telemetry'
If you have feedback or need assistance with the MCP directory API, please join our Discord server