Skip to content
AgentsIndex

mcp.run

Enterprise AI connectivity with governed access and audit controls.

Best for
Enterprise IT teams who need governed AI access across many internal apps.

What we checked

Pages last read
AI answers
Too few read

58 buyer-question answers read, November 2026

What is mcp.run?

Mcp.run is an enterprise AI connectivity platform for IT teams that runs a standards-compliant MCP gateway and management layer between apps and AI tools. It combines The Whole Org Chart, Audit & Control, and Advanced Security to govern access across internal systems. The platform is self-hosted and cloud-ready, integrates with OIDC-compatible identity providers, and includes Continuous Updates, Audit Usage, and 1-click Deactivation.

mcp.run now redirects to a different product

mcp.run was a hosted registry of "servlets" (portable, sandboxed WebAssembly tools) that AI agents could call over MCP, built by Dylibso — the company behind the Chicory WebAssembly runtime (1,135 GitHub stars) and the Extism plugin framework. The Internet Archive shows the real mcp.run web app still running on 7 September 2025 [2]. By 1 February 2026 the same URL returns an HTTP 301 to turbomcp.ai, and it still does as of the most recent capture on 13 September 2026 [1]. We confirmed the redirect is live today: fetching mcp.run now serves Turbo MCP's homepage directly. Turbo MCP is a different product aimed at a different buyer — a self-hosted MCP gateway for enterprise IT, not a public tool registry.

What Turbo MCP is, per the vendor

Turbo MCP describes itself as a "standards-compliant, self-hosted MCP gateway and management platform" for organizations, not individual developers [4]. Per its features page, it centralizes an org's MCP servers behind one URL with automatic OAuth/Dynamic Client Registration, gives admins an approval workflow for which servers teams can use (RBAC-gated registration and testing before approval), and adds an audit log with a "kill-switch" to cut an agent's access to data without disrupting the underlying human account [5]. It ships as a single-container deployment meant to run on Kubernetes, a PaaS, or VMs behind the customer's own firewall — the pitch is that agent traffic never leaves the buyer's infrastructure.

No public pricing, no self-serve signup

Every primary call to action on turbomcp.ai — "Run Turbo MCP," "Book a Demo" — routes to a contact form or demo-booking page; there is no plan list, no per-seat or per-server number anywhere on the site, and no trial or self-serve signup path ([6], turbomcp.ai/book-a-demo). /pricing, /docs, and /security all return HTTP 404. This is a normal shape for enterprise infrastructure software sold by demo, but it means a buyer cannot scope cost or read technical documentation before talking to sales.

The public storefront looks unfinished

Turbo MCP's own changelog page [8] lists four version entries dated September–December 2024, before turbomcp.ai was even registered (the domain's registration date is 23 July 2025, confirmed via RDAP at rdap.identitydigital.services). The listed features — task templates, mobile app optimization, an analytics dashboard with "interactive charts" — don't describe an MCP gateway at all; this reads as unedited placeholder copy left over from the page's Framer template, not a real release history. The GitHub organization "turbomcp" exists but has zero public repositories [10], and we could not find any company name, founder, or press coverage tied to Turbo MCP independent of the marketing site itself. Whether Turbo MCP is a Dylibso rebrand or a separate party that took over the domain is not established — Dylibso's own site (dylibso.ai) is now a single-page logo splash with no product links or mention of mcp.run or Turbo MCP.

What happened to the original mcp.run registry

Dylibso's own GitHub organization confirms the original product's fate. dylibso/mcp.run-servlets — described as "Official servlets for mcp.run published by @dylibso" — is now archived (GitHub API returns "archived": true; last push 20 November 2025, no archive date is exposed by GitHub's API) [11]. A related client library, dylibso/mcpx4j ("Java client library for mcp.run"), is not archived and was last pushed 31 October 2025, but its listed homepage — docs.mcp.run — no longer resolves at all [12]. Taken together, the registry, its documentation, and its official tool library all stopped moving within weeks of each other in late 2025, consistent with the domain being repointed to Turbo MCP shortly after.

mcp.run alternatives

Sources

Based on mcp.run's own pages, not a hands-on trial. Checked against mcp.run on .

  1. web.archive.org/web/20260913181258/https://mcp.run
  2. web.archive.org/web/20250907083105/https://www.mcp.run
  3. web.archive.org/web/20260201120420/https://mcp.run
  4. turbomcp.ai
  5. turbomcp.ai/features
  6. turbomcp.ai/contact
  7. turbomcp.ai/docs
  8. turbomcp.ai/changelog
  9. rdap.identitydigital.services/rdap/domain/turbomcp.ai
  10. github.com/turbomcp
  11. api.github.com/repos/dylibso/mcp.run-servlets
  12. api.github.com/repos/dylibso/mcpx4j
  13. dylibso.ai

Questions about mcp.run

How much does mcp.run cost?
mcp.run gives its price on request. From its own pages, checked 1 November 2026.
Is mcp.run open source, and can you host it yourself?
You can host mcp.run yourself.

How we check every listing

mcp.run price history

We have read the price once so far, on 1 November 2026: price on request.

PricePlanFirst seenLast seenReadingsSource
Price on request1 November 20261 November 20261

From our research on 1 November 2026. A date is when we read the page, not when the price changed.

Similar in Agent tools and integrations

See all in Agent tools and integrations

From our research

All research

Is mcp.run yours?

Free, and the page then carries the verified owner mark. You confirm it with an email at mcp.run. Claim this listing

Report an error if a fact is wrong.