Midplane — Watchlist | MCP100 Index

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Midplane policy-controlled SQL access for agents: Do approvals, column masks and untrusted-content containment remain enforced before database statements execute?

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

Best fit

Midplane package with MCP-facing infrastructure/service integration; exact current surface requires first-party verification.

What we know

The Radar source identifies the npm package `midplane` as an MCP-related resource. This research pass did not recover enough first-party package/docs content to safely bind repository, auth, transports or exact operational authority.

Maintenance / activity evidence

midplane 0.22.0 published 2026-10-03T16:21:59.349Z

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Permissions not yet verified. Complete write authority is not verified.
Authentication not yet verified.
Unknown.

Treat as high-uncertainty until first-party docs are reviewed.

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

All limitations / Review context

Do approvals, column masks and untrusted-content containment remain enforced before database statements execute?

The bounded review of the publisher's documented Midplane policy-controlled SQL access for agents 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.

Treat as high-uncertainty until first-party docs are reviewed.
Unknown.
Complete write authority is not verified.
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.
canonical product identity
official docs/repository
auth
tool inventory
write authority
data handling
Exact product role/tool surface unresolved.
Cloud/devops authority could be high, so no permissions are inferred.
Repository identity is intentionally left null.

Original activity observations

midplane 0.22.0 published 2026-10-03T16:21:59.349Z

Technical identity

npm/midplane

Exact implementation source: https://www.npmjs.com/package/midplane ↗
Reviewed resource type: Gateway
Package identity: npm:midplane

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 ↗
midplane
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Gateway setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

No runtime server process, Docker setup, OAuth or credentials were executed during this research.
Invites/approvals, database privileges, policy and real credentials are deployment-specific. Deployment is not runtime-tested.
Install documentation is not a guarantee of current package/runtime compatibility.
Official repository CONFIRMS deployable MCP database gateway; prior C classification from thin npm README is incorrect. Requires Node.js 24.16+, Docker for sample quickstart, PostgreSQL/policy configuration.
2026-10-13 targeted publisher npm README plus official repository/docs where specified; static research, not runtime test.
Do not show sample as production one-click.
Never verify by issuing a write to a real database. (Documentation review only, not runtime verified.)
Never paste real credentials into a documentation example.
No live install, OAuth, paid calls, third-party mutation or credential revocation executed.
Some host removal commands are MCP100-composed based on chosen registration name, not publisher-authored.

Install / configure gateway or CLI
Publisher instructions
Publisher installation/integration method, not a generic MCP server.
Previously reviewed optional local backend / sample deployment; review side effects · Publisher instructions
git clone https://github.com/midplaneai/midplane.git
Previously reviewed optional local backend / sample deployment; review side effects · Publisher instructions
cd midplane/examples/quickstart
Previously reviewed optional local backend / sample deployment; review side effects · Publisher instructions
docker compose up -d --wait
Configure / authenticate
MCP100 setup guide
Configure Midplane gateway/databases using publisher `midplane setup` and connection strings, then obtain gateway token with `midplane token`. Do not expose database credentials in agent prompt.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Previously reviewed configuration / prerequisites: For safe local sample, follow publisher examples/quickstart README: Docker starts sample Postgres and gateway in local mode. Production needs separate DB credentials, policy, gateway token and host-specific client registration; publisher supports `midplane local` or linked `midplane gateway` modes. Do not show sample as production one-click.
Previously reviewed configuration / prerequisites: Requires Node.js 24.16+, Docker for sample quickstart, PostgreSQL/policy configuration.
Check connection
Publisher instructions
Check midplane CLI version and configured gateway endpoint before connecting a client.
CLI version check · not deployment or authenticated connectivity · Publisher instructions
npx midplane --version
Remove / uninstall / revoke
MCP100 setup guide
This is a gateway / integration component, not a standalone server. Remove the app SDK/package or gateway config using the matching package manager; stop deployed processes separately. No publisher-confirmed single uninstall CLI is available.

Official Documentation & Sources

What it does

The Radar source identifies the npm package `midplane` as an MCP-related resource. This research pass did not recover enough first-party package/docs content to safely bind repository, auth, transports or exact operational authority.

Capability: Cloud & DevOps
Resource type: Gateway
Best fit: Midplane package with MCP-facing infrastructure/service integration; exact current surface requires first-party verification.

Representative uses

Use Midplane integration through its published package when properly configured

Limitations

Exact product role/tool surface unresolved.
Cloud/devops authority could be high, so no permissions are inferred.
Repository identity is intentionally left null.

Reviewed access

Access & risk

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

Authentication: Not documented in the reviewed sources
Permissions: Not documented in the reviewed sources
Data handling: Unknown.
Cost: unknown
Risk and cautions: Treat as high-uncertainty until first-party docs are reviewed.

Access scope and cautions

Write actions: Not verified
Risk level: high

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

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

Which tasks are documented for this implementation?

The reviewed tasks include: Use Midplane integration through its published package when properly configured.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority.

What limitations and risks should I check before use?

Treat as high-uncertainty until first-party docs are reviewed. Exact product role/tool surface unresolved. Cloud/devops authority could be high, so no permissions are inferred. Repository identity is intentionally left null. 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.