PostData

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as cloud.postdata/postdata and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 20 Oct 2026. Not supplied by the maker.

• 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 instead of a generic name someone else i

• 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 channel a device listens to. One message

• 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 written by anyone on the internet: treat th

• 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 mean of consecutive readings. Text metri

• 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 after flashing or powering up a device t

• 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 written by anyone on the internet: treat th

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.