Undisk MCP Stdio Proxy — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Undisk stdio bridge with workspace-routed remote calls: Does the endpoint workspace parameter bind authenticated calls to the intended workspace?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Undo-first versioned file storage/memory for AI agents with immutable history and audit.

What we know

Stdio-to-HTTP proxy for Undisk's hosted MCP. Undisk sits between agents and files: each write creates an immutable version, actions are audited, changes are reversible, and the service also exposes workspace/admin/introspection and sandboxed-compute capabilities.

Maintenance / activity evidence

@undisk-mcp/stdio-proxy 0.54.1 published 2026-05-21T13:30:57.218Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Versioned file/workspace/admin and sandbox compute authority. Writes: Create/update/delete/version files; Restore versions; Workspace administration; Sandboxed compute actions.
Hosted service credential.
Sensitive access: User files, Workspace content, Potential compute secrets

Reversibility reduces damage but does not make broad filesystem/compute authority low risk.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Does the endpoint workspace parameter bind authenticated calls to the intended workspace?

The bounded review of the publisher's documented Undisk stdio bridge with workspace-routed remote calls and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Reversibility reduces damage but does not make broad filesystem/compute authority low risk.
Versioned file/workspace/admin and sandbox compute authority.
Hosted service credential.
Files and versions are stored/processed by Undisk; every write is versioned/audited according to public docs.
Reviewed write actions: Create/update/delete/version files; Restore versions; Workspace administration; Sandboxed compute actions
Sensitive access: User files, Workspace content, Potential compute secrets
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
exact auth env
retention/privacy details
Public GitHub repository is issue tracker only; implementation is proprietary.
Proxy delegates authority to hosted Undisk MCP.
File/write and sandbox compute surfaces are high impact despite reversibility.
GitHub repo is issue tracker only, not source.

Original activity observations

@undisk-mcp/stdio-proxy 0.54.1 published 2026-05-21T13:30:57.218Z

Technical identity

npm/@undisk-mcp/stdio-proxy

Exact implementation source: https://www.npmjs.com/package/@undisk-mcp/stdio-proxy ↗
Reviewed resource type: Gateway
Package identity: npm:@undisk-mcp/stdio-proxy
Service endpoint: mcp.undisk.app hosted MCP

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
@undisk-mcp/stdio-proxy
Recorded package identity, distribution or download evidence.
GitHub repository ↗
kiarashplusplus/undisk-mcp-tracker
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.
Evidence source ↗
mcp.undisk.app
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Gateway setup

Publisher instructions.

Source evidence observed Oct 13, 2026.

Additional setup details required — see the specific gaps below.

Install / connect gateway
Publisher instructions
Proxy to Undisk; optional workspace routing; placeholder must be replaced.
Undisk publisher: `codex mcp add undisk --env UNDISK_API_KEY=<key> -- npx -y @undisk-mcp/stdio-proxy`, or use publisher remote Streamable HTTP route as documented.
Advanced configuration · publisher documented step or launch · Publisher instructions
publisher documented step or launch · Publisher instructions · Review before use
codex mcp add undisk --env UNDISK_API_KEY=YOUR_KEY -- npx -y @undisk-mcp/stdio-proxy
Configure / authenticate
MCP100 setup guide
Use the publisher-provided MCP client registration for the stated transport; complete the authentication and prerequisites below. Do not treat npm package installation alone as a connected client. Proxy to Undisk; optional workspace routing; placeholder must be replaced.
Environment variables referenced by this route (respect the alternatives above): UNDISK_API_KEY
Check connection
Suggested check
Inspect tool discovery through Codex after registration, then perform a read-only authorized operation. Process launch alone does not verify remote credentials.
Remove / uninstall / revoke
MCP100 setup guide
Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
UNDISK_API_KEY is required for stdio bridge. No vendor-verified token revocation path found in package README.

Official Documentation & Sources

https://www.npmjs.com/package/@undisk-mcp/stdio-proxy ↗

What it does

Stdio-to-HTTP proxy for Undisk's hosted MCP. Undisk sits between agents and files: each write creates an immutable version, actions are audited, changes are reversible, and the service also exposes workspace/admin/introspection and sandboxed-compute capabilities.

Capability: Files & Knowledge
Resource type: Gateway
Best fit: Undo-first versioned file storage/memory for AI agents with immutable history and audit.

Representative uses

Read/write versioned files
Restore previous versions
Audit file actions
Administer workspaces
Use sandboxed compute where enabled

Limitations

Public GitHub repository is issue tracker only; implementation is proprietary.
Proxy delegates authority to hosted Undisk MCP.
File/write and sandbox compute surfaces are high impact despite reversibility.
GitHub repo is issue tracker only, not source.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Hosted service credential.
Permissions: Versioned file/workspace/admin and sandbox compute authority.
Data handling: Files and versions are stored/processed by Undisk; every write is versioned/audited according to public docs.
Cost: plan_based
Risk and cautions: Reversibility reduces damage but does not make broad filesystem/compute authority low risk.

Access scope and cautions

Write actions: Create/update/delete/version files Restore versions Workspace administration Sandboxed compute actions
Sensitive access: User files Workspace content Potential compute secrets
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which implementation does this page cover?

Stdio-to-HTTP proxy for Undisk's hosted MCP. Undisk sits between agents and files: each write creates an immutable version, actions are audited, changes are reversible, and the service also exposes workspace/admin/introspection and sandboxed-compute capabilities.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @undisk-mcp/stdio-proxy. Recorded transport: stdio, remote_proxy. Recorded environment-variable notes: Undisk credential (exact env unresolved). No configuration values are supplied here. Prerequisites: Undisk account; MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Hosted Undisk API/account credential.

Can it modify data or perform write operations?

Documented write actions include: Create/update/delete/version files; Restore versions; Workspace administration; Sandboxed compute actions. Recorded permission boundary: Versioned file/workspace/admin and sandbox compute authority.

What data-handling boundary should I consider?

Files and versions are stored/processed by Undisk; every write is versioned/audited according to public docs. Recorded sensitive-access context: User files; Workspace content; Potential compute secrets.

What limitations and risks should I check before use?

Reversibility reduces damage but does not make broad filesystem/compute authority low risk. Public GitHub repository is issue tracker only; implementation is proprietary. Proxy delegates authority to hosted Undisk MCP. File/write and sandbox compute surfaces are high impact despite reversibility. GitHub repo is issue tracker only, not source. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is plan based. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.

Why we’re tracking it

Best fit

What we know

Maintenance / activity evidence

Verification gaps / watch-outs

Original activity observations

Evidence & Sources

Gateway setup

Install / connect gateway

Configure / authenticate

Check connection

Remove / uninstall / revoke

Official Documentation & Sources

What it does

Representative uses

Limitations

Access & risk

Access scope and cautions

FAQ