# Upshift (remote · mcp.upshiftsites.com)

Audit a site's structured data and llms.txt, match a trade to a template, and quote real prices.

- Trust score: 73/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.upshiftsites.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-upshiftsites-mcp/mcp.md), [page](https://verifymcp.io/servers/com-upshiftsites-mcp/mcp)
- npm · `upshift-mcp`: 83/100, [markdown](https://verifymcp.io/servers/com-upshiftsites-mcp/upshift-mcp.md), [page](https://verifymcp.io/servers/com-upshiftsites-mcp/upshift-mcp)

## Channel facts

- Endpoint: `https://mcp.upshiftsites.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 647 tokens (~215/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Upshift MCP server?

Upshift is a hosted endpoint at https://mcp.upshiftsites.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-upshiftsites-mcp 'https://mcp.upshiftsites.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-upshiftsites-mcp": {
      "url": "https://mcp.upshiftsites.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-upshiftsites-mcp": {
      "type": "http",
      "url": "https://mcp.upshiftsites.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-upshiftsites-mcp]
url = "https://mcp.upshiftsites.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-upshiftsites-mcp": {
      "type": "remote",
      "url": "https://mcp.upshiftsites.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-upshiftsites-mcp --url 'https://mcp.upshiftsites.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-upshiftsites-mcp:
    url: "https://mcp.upshiftsites.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-upshiftsites-mcp": {
      "Transport": "http",
      "Url": "https://mcp.upshiftsites.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-upshiftsites-mcp -t streamable-http -u 'https://mcp.upshiftsites.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-upshiftsites-mcp": {
      "type": "http",
      "url": "https://mcp.upshiftsites.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-16 (score 73, 0)

- [security] Stability: 0.97 → pass

### 2026-09-15 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-02 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `upshift_site_audit` (~158 tokens)

Audit a website for machine legibility

Fetch a live website and report how legible it is to search engines and AI assistants: structured data (JSON-LD), llms.txt, robots.txt, title and meta description, headings, image alt text, HTTPS and document weight. Returns findings with severity and a 0-100 score. Use this to check a real site before recommending changes to it. Makes one outbound request to the URL given, so it only sees what a fetch can establish — never rendering or browser metrics. Refuses private, loopback and link-local addresses, and reports a page as unreachable rather than scoring the error body.

Input parameters:

- `url` (string, required): Absolute http(s) URL of the page to audit, e.g. https://example.com

Output parameters:

- `findings` (array)
- `reachable` (boolean)
- `score` (number)
- `structuredData` (object)
- `summary` (string)
- `url` (string)

### `upshift_template_match` (~164 tokens)

Find the website template for a trade

Given an industry or trade (and optionally what the business needs), rank Upshift's 14 website template lines and return the best three, each with a live demo link, the store link, real prices, and the words that made it match. Use when someone asks what a website for a given trade should look like or cost. Answers from a catalog held in the server, so it makes no network call and returns no matches — rather than a forced one — when the trade is outside the 14 lines.

Input parameters:

- `industry` (string, required): The trade or industry, e.g. "roofing", "collision repair", "med spa".
- `needs` (string): Optional: what the business needs, e.g. "online booking, before/after photos".

Output parameters:

- `matches` (array)
- `query` (string)

### `upshift_quote` (~194 tokens)

Price a job

Return Upshift's real prices. job_type 'mcp' covers MCP server work (registry listing, live tool preview, spec upgrade, full build); 'website' covers website templates and done-for-you launches. These are the actual listed prices, not estimates. Use when someone asks what a job costs, what a tier includes, or how long it takes. The figures are generated from the live store catalog, so this cannot quote a price that is not sold; it makes no network call and the same arguments always return the same answer.

Input parameters:

- `job_type` (string, required): 'mcp' for MCP server work, 'website' for website work.
- `scope` (string): Optional free text about the situation, used to pick which tier to lead with and to explain why, e.g. "we have a server on stdio" or "roofing company, no site". Never changes the prices themselves.

Output parameters:

- `jobType` (string)
- `note` (string)
- `offers` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-upshiftsites-mcp/mcp#diagnostics

## Score history

- 2026-09-21: 73
- 2026-09-20: 73
- 2026-09-19: 73
- 2026-09-18: 73
- 2026-09-17: 73
- 2026-09-16: 73
- 2026-09-15: 73
- 2026-09-14: 72
- 2026-09-13: 72
- 2026-09-12: 72
- 2026-09-11: 71
- 2026-09-10: 71
- 2026-09-09: 70
- 2026-09-08: 70
- 2026-09-07: 69
- 2026-09-06: 69
- 2026-09-05: 68
- 2026-09-04: 68
- 2026-09-03: 67
- 2026-09-02: 67
- 2026-09-01: 66
- 2026-08-31: 66
- 2026-08-30: 65
- 2026-08-29: 65
- 2026-08-28: 65
- 2026-08-27: 64
- 2026-08-26: 64
- 2026-08-25: 62
- 2026-08-24: 61
- 2026-08-23: 61

## Common questions

### What is the Upshift MCP server?

Upshift is an MCP server listed in the public MCP registry as com.upshiftsites/mcp. Audit a site's structured data and llms.txt, match a trade to a template, and quote real prices. This page covers its hosted endpoint (https://mcp.upshiftsites.com/mcp).

### Is the Upshift MCP server safe to use?

Upshift scores 73 out of 100 on VerifyMCP. 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 Upshift MCP server expose?

Upshift exposes 3 tools: upshift_site_audit, upshift_template_match, upshift_quote. Their descriptions and schemas cost roughly 516 tokens of context every time the server is loaded.

### Does the Upshift MCP server require authentication?

No. We connected to Upshift without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Upshift MCP server still maintained?

Upshift 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.

## Links

- Remote endpoint: https://mcp.upshiftsites.com/mcp
- Repository: https://github.com/samerdwykat-cmyk/upshift-mcp
- Website: https://mcp.upshiftsites.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-upshiftsites-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-upshiftsites-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-upshiftsites-mcp/mcp