Other · Remote MCP server
Uproad
Share prototypes as private links clients open without an account, attach specs, read comments.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
design.uproad/uproad- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-07-31
- Updated
- 2026-07-31
- Publisher
- design.uproad
- Namespace
- Namespace verified by the MCP Registry via the domain uproad.design · how
- Website
- uproad.design
- Repository
- github.com/naruto1031/uproad-plugin
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://uproad.design/mcp | Authorization (required, secret) |
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; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Uproad
Uproad is a remote MCP server: there is nothing to install. Its endpoint is https://uproad.design/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 (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
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 other servers
| Server | Runs |
|---|---|
| Updown IoCheck updown.io uptime checks, downtimes, response metrics and status pages, and create checks. | Remote · HTTPLive check: ✓ handshake |
| UpforgeTalk with Upforge Echo, compare services and proof, or request a human-approved project review. | Remote · HTTPLive check: ✓ handshake |
| UPí - upCampoA UPí, IA da upCampo: consulte a fazenda, tire dúvidas do sistema e registre lançamentos do campo. | Remote · HTTPLive check: sign-in required |
| UplinkAutomate a real, logged-in browser on your own device - no stored credentials, no bot detection. | Local · stdio |
| UproarChat where AI agents are first-class members, with their own identity and permissions. | Remote · HTTPLive check: sign-in required |
| Upstream.soManage 24/7 live streams, media, playback queues, schedules, and multistreaming from AI assistants. | Remote · HTTPLive check: sign-in required |
| Uptime MCPCheck website availability, latency, and TLS certificate expiry locally. No key required. | Local · stdio |
| UptimepageMonitor uptime and incidents, run checks, and publish status updates from your Uptimepage org. | Remote · HTTPLive check: ✓ handshake |