@micropage-sh/mcp

What changed

Changed 2026-10-12 15:30 UTC

1 description rewritten.

--- pinned/get_deploy_status
+++ observed/get_deploy_status
  {
    "annotations": {
      "destructiveHint": false,
-   "description": "Report the progress of a publish: the build status, the deploy events since after_event_id (queued, built, uploaded, domain wiring, completed or failed), whether it is done, and the live URL.\n\nCall it after publish_build or publish_post, passing the build and after_event_id they returned, and keep calling it with the returned after_event_id until done is true. With after_event_id, only a deploy event after it ends the wait: a site rebuild after a post change is queued (up to about 3 minutes unless the account is Pro+) and reports waiting_for_start until it begins. It waits up to wait_seconds (default 20, max 45) per call, sending progress notifications meanwhile. possibly_stuck flags a publish with no events for far longer than a deploy takes.\n\nWhen it reports success: Right after deployment.completed the URL can still serve the previous version for up to a minute while Cloudflare's edge caches refresh, and page paths redirect (308) to a trailing slash, so fetch with redirects followed (curl -L). Read-only; it never starts or cancels a deploy.",
+   "description": "Report the progress of a publish: the build status, the deploy events since after_event_id (queued, built, uploaded, domain wiring, completed or failed), whether it is done, and the live URL.\n\nCall it after publish_build or publish_post, passing the build and after_event_id they returned, and keep calling it with the returned after_event_id until done is true. With after_event_id, only a deploy event after it ends the wait: a site rebuild after a post change is queued (up to about 3 minutes unless the account is Pro+) and reports waiting_for_start until it begins. It waits up to wait_seconds (default 20, max 45) per call, sending progress notifications meanwhile. possibly_stuck flags a publish with no events for far longer than a deploy takes. When a newer build of the project takes the deploy over (build.superseded), it follows that build and returns it as `build`; keep calling with that build from then on.\n\nWhen it reports success: Right after deployment.completed the URL can still serve the previous version for up to a minute while Cloudflare's edge caches refresh, and page paths redirect (308) to a trailing slash, so fetch with redirects followed (curl -L). Read-only; it never starts or cancels a deploy.",
    "inputSchema": {
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "additionalProperties": false,
-               "description": "e.g. build.enqueued, deployment.started, deployment.domain_wiring, deployment.completed, build.failed.",
+               "description": "e.g. build.enqueued, deployment.started, deployment.domain_wiring, deployment.completed, build.failed, or build.superseded (a newer build took this deploy over, or nothing further will deploy).",
                "type": "string"
              }
            },
+       "superseded": {
+         "description": "Builds whose deploy was taken over by a newer build during this call, in order. When a newer build of the project took over, this call followed it, so `build` is the last one followed; empty when nothing was superseded.",
+         "items": {
+           "additionalProperties": false,
+           "properties": {
+             "build_id": {
+               "type": "number"
+             },
+             "reason": {
+               "description": "publish or live_build_changed.",
+               "type": [
+                 "string",
+                 "null"
+               ]
+             },
+             "superseded_by_build_id": {
+               "type": [
+                 "number",
+                 "null"
+               ]
+             }
+           },
+           "required": [
+             "build_id",
+             "superseded_by_build_id",
+             "reason"
+           ],
+           "type": "object"
+         },
+         "type": "array"
+       },
        "waiting_for_start": {
          "description": "True when after_event_id was given but the deploy has not started yet: a site rebuild after a post change is queued (up to about 3 minutes unless the account is Pro+) and only then shows events.",
          "type": "boolean"
+       "superseded",
        "live_url",
        "next"
      ],

Current tools

Watch this server yourself

If you run this server, put the proxy in front of it. It pins these exact fingerprints on first connect and stops the session if they move.

npx -y mcp-pin@0.2.3 -- <your @micropage-sh/mcp command>

Or subscribe to this page's RSS feed to be told when it changes.

Badge

The badge states one fact about time and nothing else. It never claims a server is safe.

[![mcp-pin](https://mcp-pin.gautamkhosla.com/badge/b71b488ce0461719.svg)](https://mcp-pin.gautamkhosla.com/servers/b71b488ce0461719.html)