Is the Workers Notdown App Handoff Publish MCP server down?

mcp-registry/dev.workers.notdown-app.handoff/publish · v0.2.0

Also listed as mcp-registry/dev.workers.notdown-app.handoff/human-approval-decision-gate-and-shareable-result-page-publisher, mcp-registry/dev.workers.notdown-app.handoff/publish-shareable-result-page

As of 2026-10-20 00:54 UTC, the Workers Notdown App Handoff Publish MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 26.2 hours.

Give your agent one stable URL to publish a result or keep a page updated every run. One call.

claude mcp add --transport http workers-notdown-app-handoff-publish-mcp- https://handoff.notdown-app.workers.dev/mcp/{key}

{
  "mcpServers": {
    "workers-notdown-app-handoff-publish-mcp-": {
      "type": "http",
      "url": "https://handoff.notdown-app.workers.dev/mcp/{key}"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (69/100)

What to fix (4)

Auto-fix: 6 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.workers.notdown-app.handoff%2Fpublish/fixes

{
  "name": "delete_page",
  "description": "Delete a page you published, by id.",
  "inputSchema": {
    "type": "object",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}

{
  "name": "get_decision",
  "description": "Read the current state of a decision gate you created with request_decision. Returns status (pending / resolved / timed_out), the chosen answer (once answered or auto-resolved), and timing. Poll this to find out what the human decided; if status is still 'pending' no one has answered yet and it hasn't expired.",
  "inputSchema": {
    "type": "object",
    "required": [
      "gate_id"
    ],
    "properties": {
      "gate_id": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "list_decisions",
  "description": "List the decision gates you have created, newest first, with their status and answers.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "limit": {
        "type": "number"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.workers.notdown-app.handoff/publish"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.workers.notdown-app.handoff/publish"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~1,311 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.81% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• request_decision ~501 tokens
• publish_page ~366 tokens
• update_page ~164 tokens
• get_decision ~125 tokens
• list_decisions ~56 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.workers.notdown-app.handoff%2Fpublish.svg)](https://glimind.com/server/mcp-registry%2Fdev.workers.notdown-app.handoff%2Fpublish?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fdev.workers.notdown-app.handoff%2Fpublish?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.workers.notdown-app.handoff%2Fpublish.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.workers.notdown-app.handoff%2Fpublish.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.workers.notdown-app.handoff%2Fpublish?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:2d1d51d76227d65d…, first seen 2026-10-17, included at leaf 4654 of 29,786. Version history · verify what your client received.

Tools (7)

• delete_page
• get_decision
• list_decisions
• list_pages
• publish_page
• request_decision
• update_page

Compare: most reliable files servers · most reliable knowledge servers · most reliable productivity servers · most reliable communication servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Workers Notdown App Handoff Publish MCP server down right now?

As of 2026-10-20 00:54 UTC, the Workers Notdown App Handoff Publish MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 26.2 hours.

How many tools does Workers Notdown App Handoff Publish MCP server provide?

Workers Notdown App Handoff Publish MCP server advertises 7 tools, including delete_page, get_decision, list_decisions, list_pages, publish_page.

How do I install Workers Notdown App Handoff Publish MCP server?

Point your MCP client at this streamable-http endpoint: https://handoff.notdown-app.workers.dev/mcp/{key}

Is the Workers Notdown App Handoff Publish MCP server safe to connect to an AI agent?

Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Workers Notdown App Handoff Publish MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.