Upsonic — Watchlist | MCP100 Index

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track framework and MCP adapter changes as model and tool APIs evolve

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

Best fit

Python teams building autonomous agents with prebuilt agent patterns and optional sandbox execution.

What we know

Upsonic is a Python agent framework that supports autonomous and conventional agent patterns, prebuilt agents and integrations with sandbox providers.

Maintenance / activity evidence

Observed Jun 18, 2026 (UTC)Merge pull request 618 from Upsonic/TECH-1828

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.
Depends on tools and sandbox providers enabled by the developer. Writes: Depends on configured agents/tools.
Provider-specific credentials may be required.
Sensitive access: Provider credentials, Workspace data supplied to agents

Effective permissions and data exposure depend on the model, sandbox and tools configured for the agent.

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

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

Popularity

7,955 repository stars · 6.1k package downloads / 30 days

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

All limitations / Review context

Does Upsonic's MCP tool integration remain documented and compatible with its supported agents?

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.

Effective permissions and data exposure depend on the model, sandbox and tools configured for the agent.
Depends on tools and sandbox providers enabled by the developer.
Provider-specific credentials may be required.
Depends on model and sandbox providers.
Reviewed write actions: Depends on configured agents/tools
Sensitive access: Provider credentials, Workspace data supplied to agents
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.
Provider credentials, execution isolation and data handling vary by selected integrations.

Original activity observations

2026-06-18T14:53:56Z: Merge pull request 618 from Upsonic/TECH-1828

Technical identity

github.com/upsonic/upsonic

Exact implementation source: https://github.com/upsonic/upsonic ↗
Reviewed resource type: Framework
Repository identity: Upsonic/Upsonic
Package identity: pypi:upsonic

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

Setup · Watchlist

Framework setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Upsonic is a Python agent framework.
package install · Publisher instructions
pip install upsonic
publisher setup or prerequisite · Publisher instructions
uv pip install upsonic
Configure / authenticate
MCP100 setup guide
Python agent framework. Integrate with an application and supply model provider configuration; not a client-registered stdio MCP server.
Check connection
Suggested check
Verify the published minimal agent example in your own environment; no MCP server is installed by the base package.
Remove / uninstall / revoke
MCP100 setup guide
Uninstall Upsonic from the Python environment using `python -m pip uninstall upsonic`, remove the application's agent imports and stop services built with Upsonic. It is a framework, not an MCP server registration.
Client unregistration, program uninstall, persistent-data deletion, and credential revocation must be treated separately.
Package / application uninstall · matching installation environment · MCP100 composed guide
python -m pip uninstall upsonic

Official Documentation & Sources

What it does

Upsonic is a Python agent framework that supports autonomous and conventional agent patterns, prebuilt agents and integrations with sandbox providers.

Capability: AI & Reasoning
Resource type: Framework
Industry: Software & Technology
Best fit: Python teams building autonomous agents with prebuilt agent patterns and optional sandbox execution.

Representative uses

Build autonomous agents
Use prebuilt agent patterns
Run agent tasks in sandboxes
Analyze agent workflows

Limitations

Provider credentials, execution isolation and data handling vary by selected integrations.

Reviewed access

Access & risk

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

Authentication: Provider-specific credentials may be required.
Permissions: Depends on tools and sandbox providers enabled by the developer.
Data handling: Depends on model and sandbox providers.
Cost: usage_based
Risk and cautions: Effective permissions and data exposure depend on the model, sandbox and tools configured for the agent.

Access scope and cautions

Write actions: Depends on configured agents/tools
Sensitive access: Provider credentials Workspace data supplied to agents
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?

The reviewed tasks include: Build autonomous agents; Use prebuilt agent patterns; Run agent tasks in sandboxes; Analyze agent workflows.

What setup and authentication are documented?

Recorded installation/entrypoint step: pip install upsonic. Prerequisites: Python. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Provider-specific.

Can it modify data or perform write operations?

Documented write actions include: Depends on configured agents/tools. Recorded permission boundary: Depends on tools and sandbox providers enabled by the developer.

What data-handling boundary should I consider?

Depends on model and sandbox providers. Recorded sensitive-access context: Provider credentials; Workspace data supplied to agents.

What limitations and risks should I check before use?

Effective permissions and data exposure depend on the model, sandbox and tools configured for the agent. Provider credentials, execution isolation and data handling vary by selected integrations. 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?

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