Developer · Remote MCP server
UpToCode
Evidence-backed architecture-quality analysis for Python agent applications.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.DDYRich72/uptocode- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- PyPI
- Published
- 2026-07-20
- Updated
- 2026-07-20
- Publisher
- DDYRich72 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/DDYRich72) · how
- Website
- github.com/DDYRich72/UpToCode#readme
- Repository
- github.com/DDYRich72/UpToCode
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://uptocode-mcp-1015314816960.us-central1.run.app/mcp | Authorization |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | uptocode | 1.0.0 | stdio |
How to connect UpToCode
UpToCode is a remote MCP server: there is nothing to install. Its endpoint is https://uptocode-mcp-1015314816960.us-central1.run.app/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization. Clients that accept custom headers set it with the server's URL.
It can also run locally from a Python package published to PyPI: uptocode version 1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx uptocode.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"uptocode": {
"command": "uvx",
"args": [
"uptocode"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Uptimebolt MCP ServerAI-powered infrastructure monitoring - health, incidents, predictions, RCA, deploy safety. | Local · stdio |
| UptimelyUptime monitoring: monitors, incidents, alerts, maintenance, on-call, status pages and telemetry. | Remote · HTTPLive check: sign-in required |
| uptimemonitoring.comAgent-native uptime monitoring. Create, inspect, and assert monitor health. Free 50-monitor tier. | Remote · HTTPLive check: sign-in required |
| Uptimerobot MCPUptime, port, TLS and DNS checks for any site - no API key. | Local · stdio |
| UptyBotsUptime monitoring: create and manage HTTP, API, SSL, ping, port and domain checks. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| URL to Clean Markdown for LLMs & RAGFetch URLs and return clean Markdown for RAG - nav, ads and boilerplate stripped. | Remote · HTTPLive check: sign-in required |
| UrlhausURLhaus MCP - wraps abuse.ch URLhaus malware URL database (free, no auth) | Remote · HTTPLive check: ✓ handshake |
| URLpipeRead any page with its JavaScript run: Markdown, screenshots, metadata, console errors, Lighthouse. | Remote · HTTPLive check: ✓ handshake |