ContextForge — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track governance, discovery, and observability features as an MCP gateway

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

Best fit

Centralizing MCP servers behind a governed gateway, registry and virtual-server layer.

What we know

ContextForge is an MCP gateway/registry that can aggregate tools, register servers, create virtual MCP servers and expose stdio-backed tools through remote transports.

Maintenance / activity evidence

Observed Oct 5, 2026 (UTC)chore: migrate Tailwind CSS v3 to v4 and fix npm CVEs ( 7135)

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 expose and aggregate the authority of registered MCP servers. Writes: Administrative gateway configuration; Upstream tools may perform writes.
Requires configured gateway secrets/tokens for secure deployment.
Sensitive access: Gateway secrets, Upstream MCP credentials, Tool payloads

The gateway aggregates multiple MCPs and their credentials, making authentication, secret storage and least-privilege configuration central security concerns.

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

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

Popularity

4,579 repository stars · 28.9k package downloads / 30 days

Stars observed Oct 6, 2026. Downloads observed Oct 6, 2026.

All limitations / Review context

Which federation and governance features are supported by the current ContextForge release?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

The gateway aggregates multiple MCPs and their credentials, making authentication, secret storage and least-privilege configuration central security concerns.
Can expose and aggregate the authority of registered MCP servers.
Requires configured gateway secrets/tokens for secure deployment.
Tool requests/responses and credentials may transit the gateway.
Reviewed write actions: Administrative gateway configuration; Upstream tools may perform writes
Sensitive access: Gateway secrets, Upstream MCP credentials, Tool payloads
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
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.
A gateway concentrates credentials and tool authority.
Secure deployment requires generated secrets and token configuration.

Original activity observations

2026-10-05T15:31:28Z: chore: migrate Tailwind CSS v3 to v4 and fix npm CVEs ( 7135)

Technical identity

github.com/ibm/mcp-context-forge

Exact implementation source: https://github.com/ibm/mcp-context-forge ↗
Reviewed resource type: Gateway
Repository identity: IBM/mcp-context-forge
Package identity: pypi:mcp-contextforge-gateway

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 ↗
ibm/mcp-context-forge
Recorded repository material and project history.
Includes references whose attribution is not established.
Evidence source ↗
pypi.org/project/mcp-contextforge-gateway/
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Self-hosted gateway service setup

Publisher instructions.

Source evidence observed Oct 13, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-specific setup path. Follow prerequisites, then register or connect to your MCP host.
publisher documented install or connect · Publisher instructions
uvx mcp-contextforge-gateway
Configure / authenticate
Publisher instructions
Follow IBM official quick start to configure JWT_SECRET_KEY and admin credentials before running gateway. Direct mode defaults to http://localhost:4444.
generate and update secrets · Publisher instructions · Review before use
```
python3 -m mcpgateway.scripts.init_secrets --patch-env .env
```
Check connection
Suggested check
Use published ContextForge health and admin API checks, then verify a registered downstream MCP server tool is discoverable.
Remove / uninstall / revoke
MCP100 setup guide
Remove gateway MCP registrations from clients and stop the gateway container/service separately; preserve configured backend data unless deliberately removing.

Official Documentation & Sources

What it does

ContextForge is an MCP gateway/registry that can aggregate tools, register servers, create virtual MCP servers and expose stdio-backed tools through remote transports.

Capability: Developer Tools
Resource type: Gateway
Industry: Software & Technology
Best fit: Centralizing MCP servers behind a governed gateway, registry and virtual-server layer.

Representative uses

Register and manage MCP servers
Create virtual server groupings
Expose stdio servers through remote transport
Operate gateway/admin workflows

Limitations

A gateway concentrates credentials and tool authority.
Secure deployment requires generated secrets and token configuration.

Reviewed access

Access & risk

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

Authentication: Requires configured gateway secrets/tokens for secure deployment.
Permissions: Can expose and aggregate the authority of registered MCP servers.
Data handling: Tool requests/responses and credentials may transit the gateway.
Cost: free
Risk and cautions: The gateway aggregates multiple MCPs and their credentials, making authentication, secret storage and least-privilege configuration central security concerns.

Access scope and cautions

Write actions: Administrative gateway configuration Upstream tools may perform writes
Sensitive access: Gateway secrets Upstream MCP credentials Tool payloads
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: Register and manage MCP servers; Create virtual server groupings; Expose stdio servers through remote transport; Operate gateway/admin workflows.

What setup and authentication are documented?

Recorded installation/entrypoint step: uvx --from mcp-contextforge-gateway mcpgateway --host 0.0.0.0 --port 4444. Recorded transport: sse, streamable_http. Prerequisites: Python/uvx or container environment. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Gateway token/secret configuration is documented.

Can it modify data or perform write operations?

Documented write actions include: Administrative gateway configuration; Upstream tools may perform writes. Recorded permission boundary: Can expose and aggregate the authority of registered MCP servers.

What data-handling boundary should I consider?

Tool requests/responses and credentials may transit the gateway. Recorded sensitive-access context: Gateway secrets; Upstream MCP credentials; Tool payloads.

What limitations and risks should I check before use?

The gateway aggregates multiple MCPs and their credentials, making authentication, secret storage and least-privilege configuration central security concerns. A gateway concentrates credentials and tool authority. Secure deployment requires generated secrets and token configuration. No independent runtime, installation, or comprehensive security audit was performed.

Is this an official MCP?

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