Developer · Remote MCP server
Ink MCP
Deploy and manage applications, databases, domains, and git repos.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ink.ml/ink- Version
- 1.0.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-03-05
- Updated
- 2026-03-05
- Publisher
- ink.ml
- Namespace
- Namespace verified by the MCP Registry via the domain ml.ink · how
- Repository
- github.com/mldotink/mcp.git
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.ml.ink/ | 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 Ink MCP
Ink MCP is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.ml.ink/, 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 |
|---|---|
| ingressward MCP-SERVERBlock prompt injection, evasive spacing, and obscene content before it reaches your LLM. | Local · stdio |
| InhaltAn open-source headless CMS for managing content models and entries. | Local · stdio |
| Inite BrainOpen-source bitemporal memory layer for LLM agents - knowledge graph with conflict resolution. | Remote · HTTP |
| InjectshieldPrompt-injection firewall for AI agents - scan untrusted text before LLM calls. | Local · stdio |
| InkogSecurity co-pilot for AI agents. Scan for vulnerabilities, audit MCP servers, verify governance. | Local · stdio |
| InlayMake any website discoverable by AI agents via MCP, llms.txt, and structured data. | Remote · HTTP, SSE |
| InsAIts - AI Communication Security MonitorRuntime AI-to-AI security monitor. 23 anomaly types, OWASP MCP Top 10 coverage. | Local · stdio |
| InsForgeMCP server for InsForge BaaS - database, storage, edge functions, and deployments. | Remote & Local · HTTP, stdioLive check: sign-in required |