# Postdata MCP server

Source: https://glimind.com/server/mcp-registry%2Fcloud.postdata%2Fpostdata
Registry id: `mcp-registry/cloud.postdata/postdata`
Status: live (checked 2026-10-26T20:33:24.733Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 1620
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "postdata-mcp-server": {
      "type": "http",
      "url": "https://api.postdata.cloud/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http postdata-mcp-server https://api.postdata.cloud/mcp
```

## Tools (6)

- `get_history`: Numeric history for a device over the last N hours (up to 2208, ~92 days): min/max/mean/first/last per metric, and a downsampled series where each point is the 
- `get_latest`: The most recent reading from a device, when it arrived (unix seconds) and how long ago, plus its chart URL. Device names, metric names and metric values are wri
- `list_recent_devices`: The 20 most recently active public devices with their latest readings. Handy for examples of real payloads. Device names, metric names and metric values are wri
- `new_device_name`: Get an unused device name (like amber-otter-4821) with its ingest, read, live-stream and chart URLs. Names are public and first come, first served, so use this 
- `publish_reading`: Store one reading for a device, exactly as POST /add/{device} would. Useful for testing a dashboard or integration before hardware exists, or for writing to a c
- `wait_for_reading`: Wait until a device sends a new reading, then return it. "New" means after the moment of this call, or after the unix time in "after" if given. Call this right 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.