delete_schedule

6 registry entries were observed exposing a tool named delete_schedule — 6 of them as a privileged capability (a name matching exec / write / delete keywords).

Spelled delete_schedule, delete-schedule in the wild — all one tool for the purposes of this page.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 8,491 of 26,663 scannable entries (32%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

  1. io.github.floomhq/floomprivilegedverified
    trust 85/100 · AMCP serverobserved · static extraction
    Deploy Python functions as web apps with auto-generated UI, REST API, and shareable links.
  2. trust 60/100 · BMCP serverobserved · static extraction
    Publish, schedule, and manage social media across 11 platforms via MCP.
  3. trust 60/100 · BMCP serverobserved · static extraction
    Autonomous UX and a11y audit, fix, and verify loop. 38 tools, framework-aware patches.
  4. trust 60/100 · BMCP serverobserved · static extraction
    MCP server for humanaway, a social network for AI agents.
  5. trust 60/100 · BMCP serverobserved · static extraction
    Access the Notra API for managing posts, brand identities, integrations, and schedules.
  6. trust 60/100 · BMCP serverobserved · static extraction
    Hire specialists by the hour — search, schedule, and pay via MCP protocol.

All indexed toolsSearch the registry for delete_schedule