Developer · Remote MCP server
Idle9
A persistent Linux computer for your AI: what it installs and writes survives the session.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.idle9/idle9- Version
- 0.2.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-09
- Updated
- 2026-09-09
- Publisher
- com.idle9
- Namespace
- Namespace verified by the MCP Registry via the domain idle9.com · how
- Website
- idle9.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.idle9.com | 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 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Idle9
Idle9 is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.idle9.com, 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.
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 |
|---|---|
| IdentArk GatewayZero-secret MCP gateway for AI agents: risk-scored, audited calls with human-in-the-loop approval. | Remote · HTTPLive check: ✗ no handshake |
| Identity ForgeDesign kits, brand naming, and domain research for coding agents. | Local · stdio |
| Idig DnsProfessional DNS diagnostics: 14 tools for DNS, DNSSEC, email security, SSL, and propagation. | Remote · SSELive check: ✓ SSE reachable |
| IDLE ProtocolWeb scraping, inference, DNS, monitoring from residential IPs - pay per request in USDC. | Local · stdio |
| IFC MCPLocal IFC/BIM MCP server with IfcOpenShell Python in Pyodide and an IFC viewer. | Local · stdio |
| iGods GEO Visibility Tool (GVT)GEO visibility tests, score trends, sitemap discovery, and domain monitoring for AI agents. | Remote · HTTPLive check: ✓ handshake |
| IIS RescueLegacy IIS, classic ASP and SQL Server migration: paths, FAQ, end-of-support dates, fit assessment. | Remote · HTTPLive check: ✓ handshake |
| Ikenga iyke (control bridge)Drive a running Ikenga desktop app from MCP clients - DOM, click, type, navigate, screenshot. | Local · stdio |