Who it is for
Healthcare integration engineers operating a Redox environment.
AI Connectors · Developer Tools
Redox MCP
Configure and monitor a Redox healthcare integration environment
Overview
What Redox MCP does
Redox moves clinical data between healthcare systems, sitting between hospital record systems and the applications that need to read from or write to them. The connector is a management surface for that environment: configuring it, monitoring it, and automating work an integration team otherwise does by hand.
The publisher describes it as open and model-agnostic, usable from any MCP client without installing software and without handing over control of the data. A hundred and two tools are published, one of the larger counts in the catalogue and consistent with an integration platform where each connection type, destination, and log stream is a distinct object. A Redox account is required.
Tool surface
A hundred and two tools are claimed and the endpoint would not name one of them, so the surface of what carries clinical data stays closed to outside inspection.
Availability
Where Redox MCP is listed
Redox MCP is listed in the Claude connectors directory only. Redox Inc has no app under the same domain in the ChatGPT directory; 392 of the 3,150 products here are on both marketplaces, and this is not one of them.
The MCP server behind a Claude connector is usually the same server a ChatGPT app would need, so the absence is a distribution decision rather than a technical one.
Claude listing
In the Claude connectors directory
Redox MCP publishes 102 tools to Claude, a deeper surface than 98.6% of the 1,253 Claude-listed connectors, the top decile.
The median Claude-listed connector filed under Developer Tools publishes 13, so this one runs 89 tools above its bucket's median and ranks 3rd of 95 by tool count.
It falls in the 51+ tools band, which holds 9.6% of the Claude directory.
Redox MCP publishes a remote MCP endpoint. Claude connects to it over HTTP; there is nothing to install locally.
Every connector in the Claude directory is remote, all 1,253 of them, so transport is not a differentiator there.
- Publisher
- Redox Inc
- Verification
- Community-listed (61.5% of the Claude directory)
- Filed under
- Developer Tools
- Endpoint
-
https://api.redoxengine.com/mcp - Documentation
- Publisher setup docs
- Published tools
- 102 · 51+ tools band
- Depth rank in Developer Tools
- 3 of 95
- Snapshot
- August 2026
Redox MCP is community-listed in the Claude directory, the tier 770 of 1,253 connectors sit in (61.5%). It is the default for a self-published server, and says nothing either way about quality.
In the publisher's words
How Redox Inc describes it
Redox Engine’s MCP server is an open, model-agnostic gateway that lets your technically sophisticated healthcare integration team manage, configure, monitor, and automate your Redox environment through any AI client you already trust. You can access the MCP server without downloading software, locking into a proprietary model, or giving up control over your data.
Quoted from the connector's own Claude directory listing as captured in August 2026. Node8 did not write it and does not vouch for it.
Nearby
Other Developer Tools connectors
Runway (runway.team)
Mobile release coordination and build distribution in Runway
Claude
Agent Community
Member lookup and .agent name pre-registration
ChatGPT
Agent Ready
Scores how readable a site is to AI agents
ChatGPT
Aiven MCP
Provision and manage Aiven data services
Claude · ChatGPT
Armature
Inspect MCP server activity and agent sessions
ChatGPT
Twilio Developer Kit
Twilio API selection and implementation guidance
ChatGPT
This is an independent catalogue entry compiled by Node8 from Redox MCP's public marketplace listing as it stood in August 2026. Listing facts come from the marketplaces; the comparisons against the rest of the directory and any live-endpoint measurements are Node8's. Node8 is not affiliated with Redox Inc, and inclusion here is not an endorsement.
Want your company reachable inside ChatGPT and Claude?
Node8 builds MCP servers end to end: deciding which tools are worth exposing, the authentication and permission model, the review submissions, and the onboarding that gets them used. One server serves ChatGPT, Claude, and Microsoft Copilot.