Developer · Remote MCP server
Upshift
Audit a site's structured data and llms.txt, match a trade to a template, and quote real prices.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.upshiftsites/mcp- Version
- 1.0.3
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-08-18
- Updated
- 2026-08-18
- Publisher
- com.upshiftsites
- Namespace
- Namespace verified by the MCP Registry via the domain upshiftsites.com · how
- Website
- mcp.upshiftsites.com/
- Repository
- github.com/samerdwykat-cmyk/upshift-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.upshiftsites.com/mcp | None |
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 200)
- Handshake
- upshift 1.0.3 · protocol 2025-06-18
- Tools discovered
- 3:
upshift_site_audit,upshift_template_match,upshift_quote - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | upshift-mcp | 1.0.3 | stdio |
How to connect Upshift
Upshift is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.upshiftsites.com/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.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: upshift-mcp version 1.0.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y upshift-mcp@1.0.3.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"upshift-mcp@1.0.3"
]
}
}
}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 |
|---|---|
| UpcloudInspect servers, storage, networks, databases and billing, and start, stop or back up servers. | Remote · HTTPLive check: ✓ handshake |
| UpgradeLensNpm/PyPI/Django dependency upgrades: security, runtime compatibility, migration, package ranking. | Remote · HTTPLive check: ✓ handshake |
| UploadcareManage Uploadcare files, groups and webhooks; upload and store files. | Remote · HTTPLive check: ✓ handshake |
| uploads.shHost files from coding agents; stage on a branch and attach to GitHub PRs. | Remote & Local · HTTP, stdioLive check: sign-in required |
| upstash MCP-SERVERManage Upstash databases and resources through the Upstash Developer API. | Local · stdio |
| 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 |