@imqueue
NPM · @IMQUEUE/MCP · 2 COMPONENTS · SCANNED AUG 3
Search @imqueue docs and scaffold typed services & clients from your AI coding agent.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (GPL-3.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1476 tokens (~113/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 (38% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @imqueue/mcp
claude mcp add org-imqueue-mcp -- npx -y @imqueue/mcp
codex mcp add org-imqueue-mcp -- npx -y @imqueue/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-imqueue-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@imqueue/mcp"
],
"enabled": true
}
}
} openclaw mcp add org-imqueue-mcp --command npx --arg -y --arg @imqueue/mcp
mcp_servers:
org-imqueue-mcp:
command: "npx"
args: ["-y", "@imqueue/mcp"] {
"mcpServers": {
"org-imqueue-mcp": {
"command": "npx",
"args": [
"-y",
"@imqueue/mcp"
]
}
}
} 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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +63
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Schema quality: pass → fail ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- First check of Tool coverage: 38 functional
- Licence: GPL-3.0 functional
- Package version: 2.3.0 → 3.1.1 functional
- Package version: 2.3.0 → 3.0.0 functional
- Package version: 2.0.5 → 2.3.0 functional
- 1 Aug 26 0
- Package version: 2.1.4 → 2.3.0 functional
- Package version: 2.0.5 → 2.1.4 functional
- 31 Jul 26 −1
- First check of Stability: unverified security
- Schema quality: pass → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Capabilities: unverified functional
- Package version: 2.0.5 → 2.1.4 functional
- Package version: 2.0.5 → 2.1.3 functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 2.0.5 → 2.1.0 functional
- 27 Jul 26 28
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@imqueue/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
cli_help Show @imqueue CLI help ~87
Run `imq [command] --help` and return the exact, version-accurate flags for a command (e.g. 'service create', 'client generate'). The flags it lists are the ones create_service accepts. Read-only: it prints help and exits.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | — | A subcommand, e.g. 'service create' (omit for top-level help) |
No output schema declared.
No examples provided.
cli_install Install the @imqueue CLI ~76
Install @imqueue/cli globally via `npm install -g @imqueue/cli`, replacing any `imq` already installed. cli_status reports whether it is already present. A global install may require a user-writable npm prefix or elevated permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| version | string | — | npm version/tag to install (default 'latest') |
No output schema declared.
No examples provided.
cli_status Check the @imqueue CLI ~50
Detect whether the `imq` CLI (@imqueue/cli) is installed on this machine and report its version. create_service and generate_client need it; the scaffold_service and scaffold_client tools do not.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
config Manage @imqueue CLI configuration ~152
Run `imq config <action>`. `check` = is config initialized; `get [option]` = read a value (or list all); `set option value` = overwrite a value (nested keys use a dot-path, e.g. 'ci.provider'); `init` = interactive setup, which will time out when run non-interactively, so `set` is the automatable one. Requires the `imq` CLI.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Config operation |
| cwd | string | — | Working directory to run in |
| option | string | — | Config key (dot-path for nested), for get/set |
| value | string | — | Value to set (required for `set`) |
No output schema declared.
No examples provided.
create_service Create an @imqueue service with the CLI ~220
Scaffold a real, provider-wired @imqueue service via `imq service create`. Runs as a DRY-RUN by default: it shows the plan and writes nothing. With apply=true it writes files into the target directory and may initialise git, configure CI and push to a remote. Accepts `imq` flags (cli_help lists them) to avoid interactive prompts. Requires the `imq` CLI.
| Name | Type | Req | Description |
|---|---|---|---|
| apply | boolean | — | false/omitted = dry-run preview; true = actually create (writes files) |
| cwd | string | — | Working directory to run in (defaults to the server's cwd) |
| flags | array | — | Extra `imq` flags, e.g. ['--vcs','github','--ci','github-actions'] or feature selection ['--packages','pg-prisma,validation,opentelemetry,gcp','-D']. Get exact flags from cli_help. |
| name | string | yes | Service name, e.g. 'user' |
| path | string | — | Target directory (optional) |
No output schema declared.
No examples provided.
fleet Control the local @imqueue services fleet ~165
Run `imq ctl <action>` over a directory of service repositories. `status` reports what is running and changes nothing; `start`, `stop` and `restart` change which processes are running on this machine. Requires the `imq` CLI.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | What to do to the fleet |
| calm | boolean | — | Start services one at a time, waiting for each to be ready |
| cwd | string | — | Working directory to run in |
| path | string | — | Directory containing the service repositories (default '.') |
| services | string | — | Comma-separated service names; omit to scan the path |
| update | boolean | — | git pull each service before starting (start/restart) |
| verbose | boolean | — | Verbose output |
No output schema declared.
No examples provided.
generate_client Generate a typed client with the CLI ~110
Run `imq client generate <Service>` to emit the real, fully-typed client, writing it into the output directory. The target service must be RUNNING — the CLI introspects the live service over its message queue. Requires the `imq` CLI.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | — | Working directory to run in |
| path | string | — | Output directory (optional) |
| service | string | yes | Service name to generate a client for, e.g. 'User' / 'UserService' |
No output schema declared.
No examples provided.
get_doc Read an @imqueue doc page ~107
Fetch the full markdown of an @imqueue documentation page by its URL (as returned by search_docs). Returns plain markdown suitable for reading and quoting. Only imqueue.org (framework docs) and imqueue.com (licensing, pricing, support) URLs are fetched; anything else is refused. Very large pages are truncated, which the result reports.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | An imqueue.org or imqueue.com page URL, e.g. https://imqueue.org/get-started/ |
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | integer | yes | Size of the page body, so a caller can decide before reading it |
| mimeType | string | yes | Media type of the page body carried in content |
| truncated | boolean | yes | True when the page was too large to return whole — content holds the leading part only |
| url | string | yes | The markdown mirror actually fetched — not always the URL passed in, which is why it is worth returning |
No examples provided.
list_packages List @imqueue packages ~185
The complete, authoritative catalogue of documented @imqueue packages, each with a one-line summary and its exact install command. Call this BEFORE adding any @imqueue dependency: search_docs can only find a package you already suspect exists, and this is the list. Covers typed RPC over a message queue, the Redis queue engine, the `imq` CLI, jobs and scheduling, Prisma and Sequelize database toolkits, method caching, tag-invalidated caching, PostgreSQL LISTEN/NOTIFY, Zod validation, OpenTelemetry or Datadog tracing, async logging, GraphQL N+1 batching across services, CIDR/IP checks and HTTP rate limiting. Some pairs are mutually exclusive — pg-prisma vs pg-sequelize, opentelemetry vs datadog — and installing both of a pair breaks silently, so read the `pick` rule on those entries before choosing.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| packages | array | yes | Ordered by what to reach for first |
No examples provided.
logs Read or clean @imqueue fleet logs ~129
Work with logs of services started by `imq ctl`. action='dump' (default) returns the current combined logs and exits — it never follows/streams, and output is capped. action='clean' deletes the collected log files. Requires the `imq` CLI.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | — | dump = read current logs (default); clean = delete collected logs |
| cwd | string | — | Working directory to run in |
| prefix | boolean | — | Prefix each line with the service name (default true) |
| services | string | — | Comma-separated service names; omit to combine all |
No output schema declared.
No examples provided.
scaffold_client Scaffold an @imqueue typed client ~136
Show how to generate and use the fully-typed client for an @imqueue service. @imqueue generates the real client from a running service (via `imq client generate`), so this returns that command plus an illustrative usage snippet. The generated file exports a single namespace holding the client class, so the import shape is not the obvious one — take it from `namespace` rather than guessing. Returns text only — it writes no files.
| Name | Type | Req | Description |
|---|---|---|---|
| methods | array | — | Known methods (used to shape the example call) |
| service | string | yes | The service to call, e.g. 'user' or 'UserService' |
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | Generated client class name |
| example | object | yes | An illustrative call — not a file to write |
| generateCommand | string | yes | Run against the RUNNING service to emit the real typed client |
| namespace | string | yes | The ONLY export of the generated file: a namespace holding the client class. Import this, then `new <namespace>.<client>()` — importing the class directly does not resolve. |
| output | string | yes | The file that command writes (a compiled .js lands beside it) |
| service | string | yes | — |
No examples provided.
scaffold_service Scaffold an @imqueue service ~138
Generate an idiomatic @imqueue/rpc service (an IMQService subclass with @expose()d, JSDoc-typed methods) plus a bootstrap that starts it. Provide the methods you want, or omit them for a starter template. Any non-primitive parameter or return type also gets a types.ts with the required @classType()/@property() declarations — without those the generated client types it `any`, which compiles. Returns source text only — it writes no files.
| Name | Type | Req | Description |
|---|---|---|---|
| methods | array | — | Methods to expose |
| name | string | yes | Service name, e.g. 'user' or 'UserService' |
| Name | Type | Req | Description |
|---|---|---|---|
| cliAlternative | string | yes | The CLI command that creates a full provider-wired project instead |
| files | array | yes | — |
| install | string | yes | — |
| service | string | yes | Class name used, after normalisation ('user' -> 'UserService') |
| types | array | yes | Complex types the signatures refer to. Each needs @classType() on the class and @property() on every field — types.ts declares them; complete the fields. Empty when every type is a primitive. |
No examples provided.
search_docs Search @imqueue documentation ~310
Search the official @imqueue docs (guides, tutorial, CLI manual, articles) and every exported symbol of every @imqueue package that publishes a generated API reference, returning the most relevant pages with their URLs. Each result names the package it belongs to. Takes a plain question or an exact symbol name such as 'RedisQueue.send', 'PgPubSub.listen' or 'watcherCheckDelay'. Answers 'how do I do X in @imqueue' and confirms a signature before code is written against it. Every result carries the page URL, which get_doc reads in full. Some capabilities are covered by two mutually exclusive packages — @imqueue/pg-prisma vs @imqueue/pg-sequelize, @imqueue/opentelemetry vs @imqueue/datadog — so for a query like 'tracing' or 'database', call list_packages for the choosing rule rather than taking whichever package ranks first, and pass `package` here to search within the one you settled on.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Max results (default 6) |
| package | string | — | Restrict results to one package, e.g. 'http-protect' or '@imqueue/opentelemetry'. Use it once you know which package you want — the same words appear in several packages' symbols. |
| query | string | yes | A question or a symbol name, e.g. 'expose a service method', 'delayed jobs' or 'IMQOptions.safeDelivery' |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of results returned (0 means no matches) |
| query | string | yes | The query that was searched |
| results | array | yes | Most relevant first |
No examples provided.