Other · Remote MCP server
Untangle
Bioprocess design: generate purification routes, simulate fermentation and separations, run TEA.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
bio.untangle/untangle- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-29
- Updated
- 2026-08-29
- Publisher
- bio.untangle
- Namespace
- Namespace verified by the MCP Registry via the domain untangle.bio · how
- Website
- untangle.bio
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.untangle.bio/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 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 Untangle
Untangle is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.untangle.bio/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.
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
Site checks
The website's own root, untangle.bio, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More other servers
| Server | Runs |
|---|---|
| Unreal Engine MCPAutomate the Unreal Editor (UE 5.0-5.8): levels, Blueprints, UI, materials, VFX and more. | Local · stdio |
| UnRemind.meContext-aware reminders that surface when your situation matches, not at a fixed time. | Remote · HTTPLive check: sign-in required |
| UnRemind.me SubmitSend a reminder to anyone with a public UnRemind.me page. No account or token. | Remote · HTTPLive check: ✓ handshake |
| UnshiftTurn Claude or ChatGPT into a website builder that ships a real site to a live URL you own. | Remote · HTTPLive check: sign-in required |
| UntappdMCP server exposing Untappd API tools for AI agents - full v4 read API coverage. | Local · stdio |
| unuluAI agent website builder. Create and publish link-in-bio sites via MCP or REST API. | Remote · HTTPLive check: ✓ handshake |
| Unyly GatewayOne connector for 15,000+ MCP servers plus your team's private MCPs, from any AI client. | Remote · HTTPLive check: sign-in required |
| UpdatesCorduroy Labs studio updates over MCP: list_updates and get_update, backed by the site's JSON Feed. | Remote · HTTPLive check: ✓ handshake |