Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.taltal-beep/mcp-server-celery

PYPI · MCP-SERVER-CELERY

Read-only Celery debugging: workers, queue depths and stuck-task diagnosis.

Available components

−15 this week 64 Trust /100

Last scanned (20 hours ago)

Scores higher than 60% of PyPI servers

Category Monitoring and Observability

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs uv_build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 4 of 52 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to taltal-beep/mcp-server-celery). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 15 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 138 tokens (~69/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 +1
    • Known CVEs: partial → pass ▲ security
    • Dependency health: partial → 0.97 functional
  • 29 Oct 26 −16
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: pass → partial ▼ security
    • Dependency health: 0.97 → partial functional
  • 27 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 26 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 22 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 19 Oct 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Analysed pypi/mcp-server-celery@0.1.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo taltal-beep/mcp-server-celery
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/taltal-beep/mcp-server-celery/.github/workflows/release.yml@refs/tags/v0.1.0
Rekor log index 3327154240
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:1ad6317cc184a6180594522315c95ab321c6121fda851c3c362935068027d5c2

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted uv_build

Background: Why install scripts are a supply-chain risk →

Dependencies 52 packages
Packages resolved 52
Stale 3
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~114 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
list_workers ~46

List workers that reply to broadcast, with pool, concurrency, uptime and the queues each consumes.

NameTypeReqDescription
timeout––Seconds to wait for worker replies. Defaults to CELERY_INSPECT_TIMEOUT.

Structured output declared, but exposes no named fields.

No examples provided.

queue_depths ~68

Count waiting messages per queue and show which workers consume each one. Works on RabbitMQ and Redis.

NameTypeReqDescription
queues––Queue names to check. Defaults to configured queues plus every queue a worker consumes.
timeout––Seconds to wait for worker replies. Defaults to CELERY_INSPECT_TIMEOUT.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the io.github.taltal-beep/mcp-server-celery server?

io.github.taltal-beep/mcp-server-celery runs locally as a PyPI package, launched with uvx mcp-server-celery. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-server-celery

# add to Claude Code
claude mcp add taltal-beep-mcp-server-celery -- uvx mcp-server-celery
Common questions

What is the io.github.taltal-beep/mcp-server-celery server?

io.github.taltal-beep/mcp-server-celery is listed in the public MCP registry as io.github.taltal-beep/mcp-server-celery. Read-only Celery debugging: workers, queue depths and stuck-task diagnosis. This page covers its PyPI package (mcp-server-celery).

Is the io.github.taltal-beep/mcp-server-celery server safe to use?

io.github.taltal-beep/mcp-server-celery scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.taltal-beep/mcp-server-celery server expose?

io.github.taltal-beep/mcp-server-celery exposes 2 tools: list_workers, queue_depths. Their descriptions and schemas cost roughly 114 tokens of context every time the server is loaded.

Is the io.github.taltal-beep/mcp-server-celery server still maintained?

io.github.taltal-beep/mcp-server-celery is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.taltal-beep/mcp-server-celery server under?

io.github.taltal-beep/mcp-server-celery declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.