UpToCode
PYPI · UPTOCODE · 2 COMPONENTS · SCANNED SEP 21
Evidence-backed architecture-quality analysis for Python agent applications.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security49
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 5 of 45 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 62 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 590 tokens (~53/item across 11 items; 10 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 70% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the UpToCode MCP server?
UpToCode runs locally as a PyPI package, launched with uvx uptocode. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · uptocode
claude mcp add ddyrich72-uptocode -- uvx uptocode
{
"mcpServers": {
"ddyrich72-uptocode": {
"command": "uvx",
"args": [
"uptocode"
]
}
}
} {
"servers": {
"ddyrich72-uptocode": {
"command": "uvx",
"args": [
"uptocode"
]
}
}
} codex mcp add ddyrich72-uptocode -- uvx uptocode
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ddyrich72-uptocode": {
"type": "local",
"command": [
"uvx",
"uptocode"
],
"enabled": true
}
}
} openclaw mcp add ddyrich72-uptocode --command uvx --arg uptocode
mcp_servers:
ddyrich72-uptocode:
command: "uvx"
args: ["uptocode"] {
"McpServers": {
"ddyrich72-uptocode": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"uptocode"
]
}
}
} assistant mcp add ddyrich72-uptocode -t stdio -c uvx -a uptocode
{
"mcpServers": {
"ddyrich72-uptocode": {
"command": "uvx",
"args": [
"uptocode"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 16 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 14 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed pypi/uptocode@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 45 packages
| Packages resolved | 45 |
|---|---|
| Stale | 5 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_diff ~65
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| diff | string | yes | Unified diff with file headers, hunks, and context (maximum 4 MiB). |
| judgment | boolean | – | Enable optional bounded model judgment; false keeps analysis offline. |
| send_code | boolean | – | Explicit consent to send redacted excerpts when judgment is enabled. |
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_warnings | array | – | – |
| coverage | – | – | – |
| findings | array | – | – |
| generated_at | string | – | – |
| judgment_status | string | – | – |
| judgment_usage | – | – | – |
| metadata | – | – | – |
| redactions | – | – | – |
| rule_results | array | – | – |
| scan_root | string | yes | – |
| schema_version | string | – | – |
| suppressions | integer | – | – |
| tool_version | string | – | – |
No examples provided.
audit_file ~58
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| judgment | boolean | – | Enable optional bounded model judgment; false keeps analysis offline. |
| path | string | yes | Local path that must resolve inside the configured workspace root. |
| send_code | boolean | – | Explicit consent to send redacted excerpts when judgment is enabled. |
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_warnings | array | – | – |
| coverage | – | – | – |
| findings | array | – | – |
| generated_at | string | – | – |
| judgment_status | string | – | – |
| judgment_usage | – | – | – |
| metadata | – | – | – |
| redactions | – | – | – |
| rule_results | array | – | – |
| scan_root | string | yes | – |
| schema_version | string | – | – |
| suppressions | integer | – | – |
| tool_version | string | – | – |
No examples provided.
audit_repo ~58
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| judgment | boolean | – | Enable optional bounded model judgment; false keeps analysis offline. |
| path | string | yes | Local path that must resolve inside the configured workspace root. |
| send_code | boolean | – | Explicit consent to send redacted excerpts when judgment is enabled. |
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_warnings | array | – | – |
| coverage | – | – | – |
| findings | array | – | – |
| generated_at | string | – | – |
| judgment_status | string | – | – |
| judgment_usage | – | – | – |
| metadata | – | – | – |
| redactions | – | – | – |
| rule_results | array | – | – |
| scan_root | string | yes | – |
| schema_version | string | – | – |
| suppressions | integer | – | – |
| tool_version | string | – | – |
No examples provided.
audit_source ~91
Audit one explicitly submitted Python source document.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | – | Contained relative Python filename used only for report locations. |
| judgment | boolean | – | Enable optional bounded model judgment; false keeps analysis offline. |
| send_code | boolean | – | Explicit consent to send redacted excerpts when judgment is enabled. |
| source | string | yes | One explicitly submitted UTF-8 Python source document (maximum 1 MiB). |
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_warnings | array | – | – |
| coverage | – | – | – |
| findings | array | – | – |
| generated_at | string | – | – |
| judgment_status | string | – | – |
| judgment_usage | – | – | – |
| metadata | – | – | – |
| redactions | – | – | – |
| rule_results | array | – | – |
| scan_root | string | yes | – |
| schema_version | string | – | – |
| suppressions | integer | – | – |
| tool_version | string | – | – |
No examples provided.
check_loop ~42
Check a bounded Python loop or Runner invocation for AA001.
| Name | Type | Req | Description |
|---|---|---|---|
| snippet | string | yes | One explicitly submitted UTF-8 Python source document (maximum 1 MiB). |
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_warnings | array | – | – |
| findings | array | – | – |
| redactions | – | – | – |
No examples provided.
check_tool_schema ~43
Validate a strict function-tool descriptor and JSON Schema 2020-12 input.
| Name | Type | Req | Description |
|---|---|---|---|
| schema_json | string | yes | Strict JSON document for the named UpToCode contract. |
| Name | Type | Req | Description |
|---|---|---|---|
| issues | array | yes | – |
| judgment_status | string | – | – |
| valid | boolean | yes | – |
No examples provided.
generate_fixplan ~56
Generate a non-mutating remediation plan from approved findings.
| Name | Type | Req | Description |
|---|---|---|---|
| manifest_json | string | yes | Strict JSON document for the named UpToCode contract. |
| report_json | string | yes | Strict JSON document for the named UpToCode contract. |
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | – |
No examples provided.
get_rule ~36
Return trusted metadata for one rule identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | UpToCode rule identifier in AA001 through AA012 form. |
| Name | Type | Req | Description |
|---|---|---|---|
| error_code | – | – | – |
| message | – | – | – |
| rule | – | – | – |
No examples provided.
list_rules ~18
Return the complete trusted UpToCode rule catalog.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| rules | array | yes | – |
No examples provided.
review_findings ~83
Create an immutable review manifest from explicit finding decisions.
| Name | Type | Req | Description |
|---|---|---|---|
| approve | – | – | Finding fingerprints or rule identifiers to decide. |
| approve_all | boolean | – | Approve every finding in the exact supplied Report 2.0 document. |
| reject | – | – | Finding fingerprints or rule identifiers to decide. |
| report_json | string | yes | Strict JSON document for the named UpToCode contract. |
| Name | Type | Req | Description |
|---|---|---|---|
| created_at | string | – | – |
| decisions | array | yes | – |
| report_fingerprint | string | yes | – |
| schema_version | string | – | – |
No examples provided.
What is the UpToCode MCP server?
UpToCode is an MCP server listed in the public MCP registry as io.github.DDYRich72/uptocode. Evidence-backed architecture-quality analysis for Python agent applications. This page covers its PyPI package (uptocode).
Is the UpToCode MCP server safe to use?
UpToCode scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the UpToCode MCP server expose?
UpToCode exposes 10 tools: audit_source, check_tool_schema, check_loop, list_rules, get_rule, and 5 more. Their descriptions and schemas cost roughly 550 tokens of context every time the server is loaded.
Is the UpToCode MCP server still maintained?
UpToCode is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.