Bragproof

← Reports

@adamhancock/bullmq-mcp

Starts with no setup1.0.7npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 1 of 2 tools tried
Contacts while installing and starting: nothing

20tools listed
0hosts contacted
0files written
0.2 sto start
118dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y @adamhancock/bullmq-mcp@1.0.7

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

2 tools that take no input and look read-only were called once with nothing. 1 returned a result.

list_connectionsReturned a result under 0.1 s · 24 characters
list_queuesNo usable answer tool reported an error: Error: No active connection. Use 'connect' first.

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

connect id, url, host, port, password, db
Connect to Redis instance. Can use REDIS_URL environment variable if set. When running in Docker, localhost will automatically redirect to host.docker.internal.
disconnect
Disconnect from current Redis instance
list_connections
List all saved connections
switch_connection id
Switch to a different connection
stats queue
Get queue statistics
15 more tools
get_jobs queue, status, start, end
Get jobs from queue by status
get_job queue, jobId
Get a specific job by ID
add_job queue, name, data, opts
Add a new job to the queue
remove_job queue, jobId
Remove a job from the queue
retry_job queue, jobId
Retry a failed job
promote_job queue, jobId
Promote a delayed job
clean_queue queue, grace, limit, status
Clean jobs from queue
pause_queue queue
Pause queue processing
resume_queue queue
Resume queue processing
get_job_logs queue, jobId
Get logs for a job
add_job_log queue, jobId, message
Add a log entry to a job
list_queues pattern
List all queues in the current connection
drain_queue queue
Remove all jobs from a queue
move_failed_jobs_to_dlq queue, jobName, beforeTimestamp, dlqKey, ttlDays, dryRun
Move failed jobs to a dead letter queue with TTL. Designed for cleaning up old failed jobs that have been manually resolved.
query_dead_letter_queue dlqKey, jobName, limit
Query jobs in the dead letter queue

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseMIT
Needsnot stated
Sourcegithub.com/adamhancock/bullmq-mcp
Install scriptsmsgpackr-extract declare them. This runner does not run them.
Tarballsha512-SF17931BVeAjApKD2Ybvh33NBaMr4TyjH4zeZSlEmWk32wW0uydPpbQS19RWPo7EEdaASVoymY03x+RgL+2S3Q==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@adamhancock/bullmq-mcp.svg)](https://bragproof.smaverk.com/r/%40adamhancock/bullmq-mcp)

New version out? Ask for a fresh report.