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.

The Local Upgrade — Software Engineering

REMOTE · THELOCALUPGRADE.COM

Explore engineering services, prepare project briefs and submit authorized proposal requests.

69 Trust /100

Last scanned (20 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability49
  • 40% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 452 tokens (~50/item across 9 items; 6 tools + 3 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 66

    First indexed and scored.

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

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=thelocalupgrade.com CN=YE2,O=Let's Encrypt,C=US 17 Nov 2026 15 Feb 2027 ECDSA 256 ECDSA-SHA384 6ac6adfe5ba2ef4b8f46a10f6d4ca0d160b
SANs: thelocalupgrade.com, www.thelocalupgrade.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of thelocalupgrade.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
thelocalupgrade.com. No DS 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
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://thelocalupgrade.com/mcp Verified 200
http (plaintext) http://thelocalupgrade.com/mcp HTTPS enforced 301 https://thelocalupgrade.com/mcp
MCP tools · 6 exposed · ~386 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
discover_services ~33

Full-stack products, agent systems, integration, modernization and B2B engineering workstreams. Returns service scope and engagement options.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_procurement_information ~30

Engagement process, data handling, supplier-review topics and authority boundaries for RFPs and subcontracting.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

prepare_engagement_brief ~130

Formats confirmed business requirements for an RFP or proposal request. Does not store, transmit, quote or approve the project. Preserve unknowns; no technology or budget ceiling.

NameTypeReqDescription
acceptanceCriteriaarray––
budgetContextstring––
businessOutcomestringyes–
constraintsstring––
engagementTypestringyes–
existingSystemsstring––
openQuestionsarray––
procurementRequirementsstring––
requirementsstringyes–
timelineContextstring––
titlestringyes–

No output schema declared.

No examples provided.

request_email_followup ~76

Saves a business inquiry and authorized reply contact. Use for procurement, delivery partnerships, confidential engagement setup or questions before a full brief. No newsletter signup.

NameTypeReqDescription
agentobjectyes–
consentbooleanyes–
contactobjectyes–
questionstringyes–
requestIdstringyes–

No output schema declared.

No examples provided.

request_proposal ~91

Saves an approved project brief and reply contact for engineering review. Supports RFPs, full products and subcontracting. Requires actual requester consent. Reuse the same UUID v4 and unchanged payload on retries. No purchase or execution.

NameTypeReqDescription
agentobjectyes–
consentbooleanyes–
contactobjectyes–
projectobjectyes–
requestIdstringyes–

No output schema declared.

No examples provided.

review_engineering_evidence ~26

Representative project capabilities and founder enterprise background, with evidence links and scope context.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the The Local Upgrade — Software Engineering MCP server?

The Local Upgrade — Software Engineering is a hosted endpoint at https://thelocalupgrade.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 · thelocalupgrade.com

# add to Claude Code
claude mcp add --transport http com-thelocalupgrade-engineering 'https://thelocalupgrade.com/mcp'
Common questions

What is the The Local Upgrade — Software Engineering MCP server?

The Local Upgrade — Software Engineering is an MCP server listed in the public MCP registry as com.thelocalupgrade/engineering. Explore engineering services, prepare project briefs and submit authorized proposal requests. This page covers its hosted endpoint (https://thelocalupgrade.com/mcp).

Is the The Local Upgrade — Software Engineering MCP server safe to use?

The Local Upgrade — Software Engineering scores 69 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 The Local Upgrade — Software Engineering MCP server expose?

The Local Upgrade — Software Engineering exposes 6 tools: discover_services, review_engineering_evidence, get_procurement_information, prepare_engagement_brief, request_proposal, request_email_followup. Their descriptions and schemas cost roughly 386 tokens of context every time the server is loaded.

Does the The Local Upgrade — Software Engineering MCP server require authentication?

No. We connected to The Local Upgrade — Software Engineering without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the The Local Upgrade — Software Engineering MCP server still maintained?

The Local Upgrade — Software Engineering is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the The Local Upgrade — Software Engineering MCP server?

VerifyMCP ran 13 checks on The Local Upgrade — Software Engineering, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.