OpenConnector — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow credential-handling and hosted-connector changes because the service brokers external access

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

Best fit

Operating durable authenticated app connections behind MCP and HTTP interfaces.

What we know

OpenConnector is a connector runtime for durable app connections. It manages API/OAuth credentials and exposes provider actions through MCP and HTTP/OpenAPI interfaces.

Maintenance / activity evidence

Observed Oct 5, 2026 (UTC)fix(fxmacrodata): align pagination and redact escaped keys ( 654)

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

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Can call actions exposed by configured providers. Writes: Depends on provider actions enabled.
Stores/uses provider OAuth or API credentials.
Sensitive access: OAuth tokens, API keys, Connected application data

The gateway centralizes third-party credentials and can invoke state-changing provider actions; scopes should be minimized per connector.

Security source · repository notice ↗Security source · policy file ↗

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

Popularity

5,950 repository stars

Stars observed Oct 6, 2026.

All limitations / Review context

Have credential storage, OAuth scope, and connector behavior changed since this review?

The official policy and README describe credential and OAuth handling by the connector; the bounded assessment found no separate public-tracking blocker, but records the data-handling scope as an uncertainty rather than claiming installation safety.

The gateway centralizes third-party credentials and can invoke state-changing provider actions; scopes should be minimized per connector.
Can call actions exposed by configured providers.
Stores/uses provider OAuth or API credentials.
Provider data and action payloads pass through the connector runtime.
Reviewed write actions: Depends on provider actions enabled
Sensitive access: OAuth tokens, API keys, Connected application data
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
The connector brokers API keys/OAuth credentials and logs operational data according to its documented design; no independent data-handling audit was performed.
No independent runtime, installation, or comprehensive security audit was performed.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
Self-hosted OAuth providers require client credentials.
Effective permissions depend on each connected service and selected actions.

Original activity observations

2026-10-05T14:56:33Z: fix(fxmacrodata): align pagination and redact escaped keys ( 654)

Technical identity

github.com/oomol-lab/open-connector

Exact implementation source: https://github.com/oomol-lab/open-connector ↗
Reviewed resource type: Gateway
Repository identity: oomol-lab/open-connector
Service endpoint: http://localhost:3000/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 6, 2026

GitHub repository ↗
oomol-lab/open-connector
Recorded repository material and project history.

Setup · Watchlist

Self-hosted gateway service setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
OpenConnector is a self-hosted connector gateway with optional vendor-hosted OAuth service.
self hosted install or run · Publisher instructions
git clone https://github.com/oomol-lab/open-connector.git cd open-connector docker compose up
Configure / authenticate
Publisher instructions
OpenConnector self-hosted OAuth/API-key gateway: Docker Compose starts runtime; OOMOL managed hosted option is separate. Protect secrets and test no-auth action first.
Check connection
Suggested check
Publisher documents a no-auth Action as a safe runtime smoke check.
Remove / uninstall / revoke
MCP100 setup guide
From only OpenConnector deployment folder; unregister the gateway from MCP host, retain DB state/volumes unless explicitly purging.
Distinguish client registration removal from software uninstall, persistent data deletion and provider OAuth/API-key revocation.
docker compose down

Official Documentation & Sources

What it does

OpenConnector is a connector runtime for durable app connections. It manages API/OAuth credentials and exposes provider actions through MCP and HTTP/OpenAPI interfaces.

Capability: Productivity & Collaboration
Resource type: Gateway
Best fit: Operating durable authenticated app connections behind MCP and HTTP interfaces.

Representative uses

Connect OAuth/API-key services
Run provider actions
Inspect action schemas and policies
Operate connectors from a web console

Limitations

Self-hosted OAuth providers require client credentials.
Effective permissions depend on each connected service and selected actions.

Reviewed access

Access & risk

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

Authentication: Stores/uses provider OAuth or API credentials.
Permissions: Can call actions exposed by configured providers.
Data handling: Provider data and action payloads pass through the connector runtime.
Cost: usage_based
Risk and cautions: The gateway centralizes third-party credentials and can invoke state-changing provider actions; scopes should be minimized per connector.

Access scope and cautions

Write actions: Depends on provider actions enabled
Sensitive access: OAuth tokens API keys Connected application data
Risk level: high

FAQ

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

Which tasks are documented for this implementation?

The reviewed tasks include: Connect OAuth/API-key services; Run provider actions; Inspect action schemas and policies; Operate connectors from a web console.

What setup and authentication are documented?

A complete connection procedure is not verified. Recorded endpoint: http://localhost:3000/mcp. Recorded transport: streamable_http. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Provider-specific OAuth/API credentials.

Can it modify data or perform write operations?

Documented write actions include: Depends on provider actions enabled. Recorded permission boundary: Can call actions exposed by configured providers.

What data-handling boundary should I consider?

Provider data and action payloads pass through the connector runtime. Recorded sensitive-access context: OAuth tokens; API keys; Connected application data.

What limitations and risks should I check before use?

The gateway centralizes third-party credentials and can invoke state-changing provider actions; scopes should be minimized per connector. Self-hosted OAuth providers require client credentials. Effective permissions depend on each connected service and selected actions. The connector brokers API keys/OAuth credentials and logs operational data according to its documented design; no independent data-handling audit was performed. No independent runtime, installation, or comprehensive security audit was performed.

What cost model is recorded?

The reviewed cost model is usage 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.

Is this an official MCP?

OOMOL is listed as First-party MCP in MCP100’s current evidence.