Hypha Agent Framework — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Dated implementation activity and relevant MCP role justify continued Radar monitoring.

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

Best fit

Build governed agents with MCP capability integration

What we know

Production-oriented agent framework with packages for tool contracts, MCP gateway abstractions, policy, execution and testing.

Maintenance / activity evidence

GitHub REST repository pushed_at 2026-09-04T06:52:51Z for CodeSoul-co/Hypha

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Framework can execute governed tool calls according to application integration Reported action classes: Framework can execute governed tool calls according to application integration. Complete write authority is not verified.
Application-defined providers and gateway credentials
Sensitive access: Application tools, Trace data

Risk determined by host app policy and connected MCP tools
Framework privileges are inherited from connected tools, agent configuration and runtime; do not label as stand-alone server.
Framework executes bounded tools and MCP adapters; secret references, policy approvals and sandbox/workspace configuration are deployment-specific.
Unknown vulnerabilities and client-side tool approvals were not exhaustively evaluated.

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

Popularity

447 shared-repository stars

Stars observed Oct 9, 2026.

Repository total for CodeSoul-co/Hypha; not package-specific.

All limitations / Review context

At the next review, has this exact implementation gained new releases, changed setup/security scope, or become suitable for Shortlist?

No verified blocker to PUBLIC RADAR TRACKING within the bounded first-party evidence reviewed; material permissions and mitigations are explicitly disclosed.

Risk determined by host app policy and connected MCP tools
Framework privileges are inherited from connected tools, agent configuration and runtime; do not label as stand-alone server.
Framework executes bounded tools and MCP adapters; secret references, policy approvals and sandbox/workspace configuration are deployment-specific.
Framework can execute governed tool calls according to application integration
Application-defined providers and gateway credentials
Depends on configured local process, connected account and remote APIs; review first-party privacy terms for any hosted component.
Reviewed write actions: Framework can execute governed tool calls according to application integration
Sensitive access: Application tools, Trace data
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.
Unknown vulnerabilities and client-side tool approvals were not exhaustively evaluated.
full exact tool inventory or deployment-specific access configuration
metrics, runtime/compatibility details for specific version
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Framework rather than standalone installable MCP Server
MCP integration is one portion of a broader harness
No independent release lifecycle audit; do not claim precise activity date.

Original activity observations

GitHub REST repository pushed_at 2026-09-04T06:52:51Z for CodeSoul-co/Hypha

Technical identity

github.com/CodeSoul-co/Hypha

Exact implementation source: https://github.com/CodeSoul-co/Hypha ↗
Reviewed resource type: Framework
Repository identity: CodeSoul-co/Hypha

Evidence & Sources

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

Reviewed Oct 9, 2026 · Latest source observation Oct 9, 2026

GitHub repository ↗
codesoul-co/hypha
Recorded repository material and project history.

Setup · Watchlist

Framework setup

Publisher instructions.

Source evidence observed Oct 12, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Framework workspace, not a standalone third-party MCP server. Clone the repository, install its locked packages and create .env; separately configure identity, secrets, model provider and MongoDB/Redis before starting npm run dev.
git clone https://github.com/CodeSoul-co/Hypha.git cd Hypha npm ci cp .env.example .env
Configure / authenticate
MCP100 setup guide
Edit .env with HYPHA_OWNER_EMAIL, HYPHA_OWNER_PASSWORD and a random JWT_SECRET of at least 32 characters; select HYPHA_LLM_DEFAULT_PROVIDER, HYPHA_LLM_DEFAULT_MODEL and the matching provider key. Configure required MongoDB/Redis services before npm run dev. Do not register Hypha itself as a normal stdio MCP server.
Advanced configuration · start framework
start framework · Review before use
npm run dev
Check connection
MCP100 setup guide
After starting npm run dev in the Hypha checkout, query the publisher documented liveness and readiness routes. /api/v1/health checks process liveness; /api/v1/ready requires initialized storage, model provider, memory, runtime graph and workers. These are Hypha application checks, NOT a third-party MCP client handshake.
curl -fsS http://127.0.0.1:3000/api/v1/health
curl -fsS http://127.0.0.1:3000/api/v1/ready
Remove / uninstall / revoke
Publisher instructions
Stop the Hypha app from its documented deployment working directory and remove only any corresponding project-owned MCP client entry. This project is an agent framework, not automatically a standalone MCP server.

Official Documentation & Sources

What it does

Production-oriented agent framework with packages for tool contracts, MCP gateway abstractions, policy, execution and testing.

Capability: Developer Tools
Resource type: Framework
Best fit: Build governed agents with MCP capability integration

Representative uses

Integrate MCP capabilities
Register governed tools
Design agent runtime
Trace and test agent actions

Limitations

Framework rather than standalone installable MCP Server
MCP integration is one portion of a broader harness
Risk determined by host app policy and connected MCP tools
No independent release lifecycle audit; do not claim precise activity date.

Reviewed access

Access & risk

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

Authentication: Application-defined providers and gateway credentials
Permissions: Framework can execute governed tool calls according to application integration
Data handling: Depends on configured local process, connected account and remote APIs; review first-party privacy terms for any hosted component.
Cost: unknown
Risk and cautions: Risk determined by host app policy and connected MCP tools

Access scope and cautions

Write actions: Not verified Framework can execute governed tool calls according to application integration
Sensitive access: Application tools Trace data
Risk level: moderate
Security notes: Framework privileges are inherited from connected tools, agent configuration and runtime; do not label as stand-alone server. Framework executes bounded tools and MCP adapters; secret references, policy approvals and sandbox/workspace configuration are deployment-specific.

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-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Integrate MCP capabilities; Register governed tools; Design agent runtime; Trace and test agent actions.

What setup and authentication are documented?

Recorded installation/entrypoint step: npm install @codesoul-co/hypha-mcp. Recorded transport: library. Prerequisites: Follow framework/SDK documentation. Client notes: Source docs and package may evolve; install according to confirmed release. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Application-defined providers and gateway credentials

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Framework can execute governed tool calls according to application integration. Recorded permission context: Framework can execute governed tool calls according to application integration

What data-handling boundary should I consider?

Depends on configured local process, connected account and remote APIs; review first-party privacy terms for any hosted component. Recorded sensitive-access context: Application tools; Trace data.

What limitations and risks should I check before use?

Risk determined by host app policy and connected MCP tools. Framework rather than standalone installable MCP Server. MCP integration is one portion of a broader harness. No independent release lifecycle audit; do not claim precise activity date. Framework privileges are inherited from connected tools, agent configuration and runtime; do not label as stand-alone server. Framework executes bounded tools and MCP adapters; secret references, policy approvals and sandbox/workspace configuration are deployment-specific. Unknown vulnerabilities and client-side tool approvals were not exhaustively evaluated.