Developer · Remote MCP server
Toolmesh
Self-hosted MCP gateway. Turn any REST API into MCP tools via YAML (DADL). Authz, audit, policies.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.DunkelCloud/toolmesh- Version
- 0.4.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-24
- Updated
- 2026-09-24
- Publisher
- DunkelCloud (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/DunkelCloud) · how
- Repository
- github.com/DunkelCloud/ToolMesh
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://{host}:8123/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.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
How to connect Toolmesh
Toolmesh is a remote MCP server: there is nothing to install. Its endpoint is https://{host}:8123/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.
The URL contains placeholders to fill in before connecting: {host}.
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, not tested here. 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 |
|---|---|
| ToolbeltA collaborative substrate over your data: vector, knowledge graph, SQL, geospatial, streaming. | Remote · HTTPLive check: sign-in required |
| ToolcOptimizing compiler for agent tools: many MCP servers or REST APIs in, one lean endpoint out. | Local · stdio |
| ToolforteExact IBAN, VAT, cron, regex answers; HTML/URL to hosted PDF or screenshot; agent memory; workflows. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| ToolgovernWraps the toolgovern CLI as a single generic MCP tool for agent-tool policy validation. | Local · stdio |
| ToolPipe MCP Server238+ dev tools via MCP: JSON, QR, PDF, DNS, hash, UUID, code review, JWT, SSL, WHOIS, and more. | Remote · HTTPLive check: ✗ no handshake |
| ToolrouteRoute AI agent tasks to MCP server and LLM, scored on 132+ real benchmark executions. | Local · stdio |
| Tools MCPMCP tools: WCAG contrast, JP char/X-weight count, WebP convert, JSON-LD, llms.txt. | Local · stdio |
| ToolTrust ScannerScans MCP servers for prompt injection, data exfiltration, and privilege escalation. | Local · stdio |