org.imqueue/mcp

Est-ce que org.imqueue/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « org.imqueue/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 7 outils

• get_doc≈ 764 tokens

  Fetch the markdown of an @imqueue documentation page by its URL (as returned by search_docs). Returns plain markdown suitable for reading and quoting. Pass a URL with a #fragment — which is what search_docs returns for a section result — to get just that section plus the heading path above it; pass the URL without one to read the whole page. 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis
    An imqueue.org or imqueue.com page URL, e.g. https://imqueue.org/get-started/

  Exemple d'appel

  {"name": "get_doc", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "bytes": 1, "section": {}, "markdown": "texte", "mimeType": "texte", "truncated": true, "fragmentMiss": {}}}

• list_packages≈ 804 tokens

  The complete, authoritative catalogue of documented @imqueue packages, each with its current version, licence, minimum Node version, 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. For one package's release history, links and the framework-wide Node and Redis requirements, use package_status.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_packages", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"packages": [], "framework": {}, "factsUnavailable": true}}

• local_install_guide≈ 376 tokens

  Return the setup instructions for running the full @imqueue MCP server on your own machine. The local server adds the CLI-backed tools, which act on your project files and running services and so cannot be offered by a hosted server. Returns instructions only — it installs nothing.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "local_install_guide", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"clientConfig": {}, "claudeCodeCommand": "texte"}}

• package_status≈ 654 tokens

  The current version, licence, minimum Node version and last release date of any published @imqueue package — or of all of them. Use it when the user asks which version of an @imqueue package is current, what licence it is under, or which Node or Redis version it needs. Covers every published package, including @imqueue/cli and @imqueue/mcp, and also returns the framework-wide licence, Node and Redis requirements, with a `licenseNote` that states the licence terms in a sentence. The facts are read from the npm registry by imqueue.org, and the result says when. Pass `package` for one entry, with or without the @imqueue/ scope; omit it for all of them.

  Paramètres, retour & exemple (1)

  Paramètres

  • package · string · optionnel
    One package, with or without the scope: 'rpc', '@imqueue/rpc'. Omit for every package.

  Exemple d'appel

  {"name": "package_status", "arguments": {"package": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"source": "texte", "packages": [], "framework": {}, "generated": "texte"}}

• scaffold_client≈ 781 tokens

  READ-ONLY: returns text and writes nothing to disk, and does NOT run the command it shows you. Explains 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 exact 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. Use generate_client (local install only) if you want the command actually run.

  Paramètres, retour & exemple (2)

  Paramètres

  • methods · array · optionnel
    Known methods (used to shape the example call)
  • service · string · requis
    The service to call, e.g. 'user' or 'UserService'

  Exemple d'appel

  {"name": "scaffold_client", "arguments": {"service": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"client": "texte", "output": "texte", "example": {}, "service": "texte", "namespace": "texte", "generateCommand": "texte"}}

• scaffold_service≈ 761 tokens

  READ-ONLY: returns generated source code as text and writes nothing to disk, creates no project and runs no command. Generates 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. Use create_service (local install only) if you want files actually written.

  Paramètres, retour & exemple (2)

  Paramètres

  • name · string · requis
    Service name, e.g. 'user' or 'UserService'
  • methods · array · optionnel
    Methods to expose

  Exemple d'appel

  {"name": "scaffold_service", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"files": [], "types": [], "install": "texte", "service": "texte", "cliAlternative": "texte"}}

• search_docs≈ 750 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    Max results (default 6)
  • query · string · requis
    A question or a symbol name, e.g. 'expose a service method', 'delayed jobs' or 'IMQOptions.safeDelivery'
  • package · string · optionnel
    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.

  Exemple d'appel

  {"name": "search_docs", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"count": 1, "query": "texte", "results": [], "advisories": []}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.imqueue.org/mcp