Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/tommypj/mcp-job-queueInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/tommypj/mcp-job-queue/job-queue)<a href="https://agentmods.dev/mcp/tommypj/mcp-job-queue/job-queue"><img src="https://agentmods.dev/badge/mcp/tommypj/mcp-job-queue/job-queue/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/tommypj/mcp-job-queue/job-queue"><img src="https://agentmods.dev/badge/mcp/tommypj/mcp-job-queue/job-queue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
job-queue scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"job-queue": {
"command": "node",
"args": [
"--experimental-sqlite",
"/absolute/path/to/mcp-job-queue/dist/server.js"
],
"env": {
"JOBQ_DB_PATH": "/absolute/path/to/queue.db",
"JOBQ_ARTIFACT_DIR": "/absolute/path/to/artifacts"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 13 lines scan A fb8c8cdf7b4a
job-queue is an MCP server published in the GitHub repository tommypj/mcp-job-queue (0 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
bunqueue
MCP server "bunqueue" as configured in egeominotti/bunqueue. Launched with bun run src/mcp/index.ts. Needs 2 environment variables to run.
jobd
MCP server "jobd" as configured in musharna/jobd. Runs locally from the jobd[mcp] Python package.
mcp-queue-doctor
Diagnoses pg-boss and graphile-worker job queues: retry storms, stuck workers, missed schedules. Runs locally from the mcp-queue-doctor npm package.
mcp-trustlayer
MCP server "mcp-trustlayer" as configured in neelbarm/mcp-trustlayer. Runs locally from the mcp-trustlayer Python package.
memocall
Recall past Claude Code conversations from any project as clean, compact Markdown. Runs locally from the memocall npm package.
mcp-bash-server
MCP server "mcp-bash-server" as configured in uditk2/mcp-bash-server. Runs locally from the mcp-bash-server Python package.