Is mcp-registry/io.github.molt2meet-org/molt2meet/approve_physical_task_completion working right now?

10
grade F · down
success (real usage)
—
calls observed
—
p50 latency
728ms
data basis
probe-liveness

Working alternatives

See all live alternatives to mcp-registry/io.github.molt2meet-org/molt2meet/approve_physical_task_completion →

FAQ

Is mcp-registry/io.github.molt2meet-org/molt2meet/approve_physical_task_completion working right now?

As of the latest check, mcp-registry/io.github.molt2meet-org/molt2meet/approve_physical_task_completion has a Glimind reliability score of 10/100 (grade F) and its current verdict is "down" — recommendation: avoid. Glimind tracks this live from safe liveness probes plus privacy-clean real-usage outcomes.

How reliable is mcp-registry/io.github.molt2meet-org/molt2meet/approve_physical_task_completion?

mcp-registry/io.github.molt2meet-org/molt2meet/approve_physical_task_completion scores 10/100 (grade F) on the Glimind reliability standard. The score is neutral and unconflicted — Glimind sells no tools.

What should I do if mcp-registry/io.github.molt2meet-org/molt2meet/approve_physical_task_completion is down or failing?

Tool is down — don't retry now; switch to a live alternative or back off for minutes. Use a timeout around 2184ms. Live alternatives that do a similar job: mcp-registry/io.github.ccstt-dev/callable/review_task, mcp-registry/io.github.tlkc888-jenkins/joy/approve_job, mcp-registry/io.github.corsur/swarm-tips/shillbot_approve_task, mcp-registry/network.tenzro/tenzro/complete_task.

What are the best alternatives to mcp-registry/io.github.molt2meet-org/molt2meet/approve_physical_task_completion?

Working alternatives ranked by capability similarity and live health: mcp-registry/io.github.ccstt-dev/callable/review_task, mcp-registry/io.github.tlkc888-jenkins/joy/approve_job, mcp-registry/io.github.corsur/swarm-tips/shillbot_approve_task, mcp-registry/network.tenzro/tenzro/complete_task. See each one's live status on Glimind.

How do I call mcp-registry/io.github.molt2meet-org/molt2meet/approve_physical_task_completion reliably?

Before calling, check mcp-registry/io.github.molt2meet-org/molt2meet/approve_physical_task_completion with Glimind (MCP: prepare_tool_call, or GET https://glimind.com/v1/prepare/mcp-registry%2Fio.github.molt2meet-org%2Fmolt2meet%2Fapprove_physical_task_completion) to get a known-good input shape, the expected output, a suggested timeout (~2184ms), and a live fallback.

Embed this badge

Show live reliability in your README or status page:

Glimind reliability badge

[![Glimind reliability](https://glimind.com/v1/badge/mcp-registry%2Fio.github.molt2meet-org%2Fmolt2meet%2Fapprove_physical_task_completion.svg)](https://glimind.com/tool/mcp-registry%2Fio.github.molt2meet-org%2Fmolt2meet%2Fapprove_physical_task_completion)

Get the data

Agents: query https://glimind.com/mcp (MCP) or GET https://glimind.com/v1/health/mcp-registry%2Fio.github.molt2meet-org%2Fmolt2meet%2Fapprove_physical_task_completion. Install the SDK to contribute outcomes (privacy-preserving) and sharpen this rating — free key · docs.

Rating methodology is transparent and neutral — Glimind sells no tools and runs no integrations; it only measures. Updated 2026-06-30T06:31:57.130Z.