Developer · Remote MCP server
@imqueue
Search @imqueue docs and scaffold typed services & clients from your AI coding agent.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
org.imqueue/mcp- Version
- 3.7.9
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-18
- Updated
- 2026-09-18
- Publisher
- org.imqueue
- Namespace
- Namespace verified by the MCP Registry via the domain imqueue.org · how
- Website
- imqueue.org/mcp/
- Repository
- github.com/imqueue/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.imqueue.org/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- imqueue 3.7.9 · protocol 2025-06-18
- Tools discovered
- 7:
search_docs,get_doc,list_packages,package_status,scaffold_service,scaffold_client,local_install_guide - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @imqueue/mcp | 3.7.9 | stdio |
How to connect @imqueue
@imqueue is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.imqueue.org/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @imqueue/mcp version 3.7.9. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @imqueue/mcp@3.7.9.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@imqueue/mcp@3.7.9"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| .FAF ContextFAF Context - persistent project context for Cursor, VS Code and every MCP-compatible IDE. | Local · stdio |
| .NET Debugger for MCPGive an AI agent a real.NET debugger: breakpoints, stepping, locals, expression evaluation. | Local · stdio |
| .NET MCP ServerAI assistant access to.NET SDK for projects, packages, building, testing, and development tools. | Local · stdio |
| .promptsPrompts, the home to all your AI prompts, everywhere you need them. | Remote · HTTPLive check: sign-in required |
| 🐴 GulltopprResolve any EVM contract ABI (even unverified, via decompilation), read, simulate, prepare txs. | Remote · HTTPLive check: ✓ handshake |
| 11agents Cloud MCPCloud MCP for project data, analytics, research, content planning, media generation, and growth. | Remote · HTTPLive check: ✗ no handshake |
| 1Claw VaultHSM-backed vault secrets for AI agents (JIT fetch) plus prompt-injection and threat scanning. | Local · stdio |
| 1lev1Track partnership work, log mission hours, and see what needs your approval on 1lev1.com. | Remote · HTTPLive check: ✓ handshake |