Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Upshift

REMOTE · MCP.UPSHIFTSITES.COM · 2 COMPONENTS · SCANNED SEP 22

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

+1 this week 73 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

remote · mcp.upshiftsites.com

# add to Claude Code
claude mcp add --transport http com-upshiftsites-mcp 'https://mcp.upshiftsites.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-upshiftsites-mcp": {
      "url": "https://mcp.upshiftsites.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-upshiftsites-mcp": {
      "type": "http",
      "url": "https://mcp.upshiftsites.com/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add com-upshiftsites-mcp --url 'https://mcp.upshiftsites.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-upshiftsites-mcp:
    url: "https://mcp.upshiftsites.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-upshiftsites-mcp": {
      "Transport": "http",
      "Url": "https://mcp.upshiftsites.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-upshiftsites-mcp -t streamable-http -u 'https://mcp.upshiftsites.com/mcp'
// mcp.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 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.

  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +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.

  • 12 Sept 26 +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.

  • 10 Sept 26 +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.

  • 8 Sept 26 +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.

  • 6 Sept 26 +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.

  • 4 Sept 26 +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.

  • 2 Sept 26 +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.

Diagnostics

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 · Probed https://mcp.upshiftsites.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=upshiftsites.com CN=WE1,O=Google Trust Services,C=US 17 Aug 2026 15 Nov 2026 ECDSA 256 ECDSA-SHA256 acb47c0f81b8dea713699869f261b7ed
SANs: upshiftsites.com, mcp.upshiftsites.com, *.mcp.upshiftsites.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.upshiftsites.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
upshiftsites.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.upshiftsites.com/mcp Verified 200
http (plaintext) http://mcp.upshiftsites.com/mcp Inconclusive 405
MCP tools · 3 exposed · ~516 tokens

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 →

Tool Tokens
upshift_quote ~194

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.

NameTypeReqDescription
job_typestringyes'mcp' for MCP server work, 'website' for website work.
scopestringOptional 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.
NameTypeReqDescription
jobTypestringyes
notestringyes
offersarrayyes

No examples provided.

upshift_site_audit ~158

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.

NameTypeReqDescription
urlstringyesAbsolute http(s) URL of the page to audit, e.g. https://example.com
NameTypeReqDescription
findingsarrayyes
reachablebooleanyes
scorenumberyes
structuredDataobjectyes
summarystringyes
urlstringyes

No examples provided.

upshift_template_match ~164

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.

NameTypeReqDescription
industrystringyesThe trade or industry, e.g. "roofing", "collision repair", "med spa".
needsstringOptional: what the business needs, e.g. "online booking, before/after photos".
NameTypeReqDescription
matchesarrayyes
querystringyes

No examples provided.

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.