mcp server
tempmd
Publish artifacts to one stable public temp.md link that updates in place. No account needed.
Description as published by the maintainer. Source
- version 0.4.0
- active
active — Registry entry last updated 2026-07-24.
What this server can do
8 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_temp_status(temp_id, update_token)- Inspect lifecycle, expiry, restore eligibility, ownership, moderation, and settings. Required: temp_id.
list_temps- List Temps owned by the account API key supplied in the MCP Authorization header.
publish_temp(files, title, spa_mode, idempotency_key)- Publish an inline text or base64 bundle to a stable public URL. Send index.html as the main page. Repeated identical calls are idempotent. If the MCP connection uses a temp.md account API key, the Temp is owned by that account immediately. Required: files.
recover_update_token(temp_id)- Rotate every prior scoped update token and return one replacement. Requires an owning account API key in the MCP Authorization header. Required: temp_id.
restore_temp(temp_id, update_token)- Reactivate an expired Temp during its restore grace period without changing its URL. Required: temp_id.
set_comments(enabled, temp_id, update_token)- Toggle pinned visitor feedback on a Temp. Required: temp_id, enabled.
snapshot_temp(label, temp_id, update_token)- Create a fixed snapshot URL for the current Version while the canonical URL continues to track the latest Version. Required: temp_id.
update_temp(files, title, temp_id, spa_mode, update_token, idempotency_key)- Atomically publish a new inline bundle behind the same canonical URL. The previous Version stays live if this call fails. Required: temp_id, files.
Last successful function declaration observed on . Source: https://api.temp.md/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://api.temp.md/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.4.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-24 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-24 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 8 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | api.temp.md | |
| mcp endpoint status | ok | The server listed 8 functions when asked. | as of probe | api.temp.md |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json