Watchlist tracking
Reviewed for relevance and future tracking value.
MCP100 Assessment
Watchlist / Tracking
Why we’re tracking it
Follow runtime isolation, registry, and deployment support because ToolHive is infrastructure
Reviewed · Documentation review; complete setup workflow not independently tested
Best fit
Teams deploying and governing MCP servers with isolation, registry and policy controls.
What we know
An open-source MCP platform with isolated runtimes, registry, gateway, policy, identity and observability features.
Maintenance / activity evidence
- Observed (UTC)Update github actions ( 6747)
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.
- Policy- and server-specific. Writes: Depends on wrapped servers.
- Configurable identity/OIDC/OAuth
- Sensitive access: MCP credentials, Tool traffic
- A governance platform can concentrate many MCP credentials and capabilities; provenance, identity and network controls are central.
Full authority, access and evidence limits are available in Review context and Access & risk.
Popularity
2,238 repository stars
Stars observed Oct 6, 2026.
All limitations / Review context
Which server lifecycle and policy controls are supported in the next 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.
- A governance platform can concentrate many MCP credentials and capabilities; provenance, identity and network controls are central.
- Policy- and server-specific.
- Configurable identity/OIDC/OAuth
- MCP traffic and credentials may pass through the platform.
- Reviewed write actions: Depends on wrapped servers
- Sensitive access: MCP credentials, Tool traffic
- 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.
- Deployment differs across CLI/UI/Kubernetes modes.
- Effective risk depends on the servers registered behind the gateway.
Original activity observations
- 2026-10-05T12:29:34Z: Update github actions ( 6747)
Technical identity
github.com/stacklok/toolhive- Exact implementation source
- https://github.com/stacklok/toolhive ↗
- Reviewed resource type
- Gateway
- Repository identity
- stacklok/toolhive
Evidence & Sources
- Evidence basis
- Recorded source evidence
- Setup runtime verification
- Not independently runtime-tested by MCP100 for this setup workflow.
Reviewed · Latest source observation
- GitHub repository ↗
stacklok/toolhive
Recorded repository material and project history.
- Evidence source ↗
docs.stacklok.com/toolhive/
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 .
Additional setup details required — see the specific gaps below.
Install / connect
Publisher instructionsToolHive is an MCP server manager. Choose the manager CLI/desktop/Kubernetes installation from official ToolHive docs; a provider MCP registration is not the same as installing ToolHive.
publisher documented · Publisher instructions
brew install thvConfigure / authenticate
MCP100 setup guideInstall ToolHive CLI per official platform-specific guide, start only the downstream MCP servers you choose and attach clients. ToolHive manages individual MCP servers; it is not a single downstream server.
Check connection
Suggested checkRun `thv list` to inspect managed server state; connect the target through chosen MCP client and verify tools/list.
Remove / uninstall / revoke
Publisher instructionsPublisher exact commands: `thv list`, `thv stop --all` if you intentionally stop every server, or stop one target; `thv rm <SERVER_NAME>` removes the chosen managed MCP. Then `brew uninstall thv` only if Homebrew installed the CLI. Do not erase config/data or stop all without user approval.
Client unregistration, program uninstall, persistent-data deletion, and credential revocation must be treated separately.
Remove managed server · ToolHive only · Publisher instructions
thv rm <SERVER_NAME>
What it does
An open-source MCP platform with isolated runtimes, registry, gateway, policy, identity and observability features.
- Capability
- Cloud & DevOps
- Resource type
- Gateway
- Industry
- Software & Technology
- Best fit
- Teams deploying and governing MCP servers with isolation, registry and policy controls.
Representative uses
- Run MCP servers in isolated containers
- Curate trusted servers
- Expose governed gateway endpoints
- Operate MCP on Kubernetes
Limitations
- Deployment differs across CLI/UI/Kubernetes modes.
- Effective risk depends on the servers registered behind the gateway.
Reviewed access
Access & risk
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
- Authentication
- Configurable identity/OIDC/OAuth
- Permissions
- Policy- and server-specific.
- Data handling
- MCP traffic and credentials may pass through the platform.
- Cost
- free
- Risk and cautions
- A governance platform can concentrate many MCP credentials and capabilities; provenance, identity and network controls are central.
Access scope and cautions
- Write actions
- Depends on wrapped servers
- Sensitive access
- MCP credentials Tool traffic
- Risk level
- moderate
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?
What authentication is documented?
Can it modify data or perform write operations?
What data-handling boundary should I consider?
What limitations and risks should I check before use?
Is this an official MCP?
Stacklok is listed as First-party MCP in MCP100’s current evidence.