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.

Mind Upload AI meta harness

REMOTE · MCP.MINDUPLOAD.APP · 3 COMPONENTS

Your AI mind directs coding agents; work reviewed against your memories: Claude Code, Codex, Cursor

+4 this week 81 Trust /100

Last scanned (16 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 21 Nov 2026.

Category AI and Machine Learning

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 Security89
Transport & Reachability100
Schema Quality & AI Usability56
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1926 tokens (~240/item across 8 items; 8 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 Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 74% of tool parameters carry a description.Partial
  • 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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 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.

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 12 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “consult_mind” rewrote its description, which is the text the model reads security
    • Tool “review_work” rewrote its description, which is the text the model reads security
    • Schema quality: 276 → 240 ▲ functional
  • 11 Nov 26 +1

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

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 Nov 2026 · Probed https://mcp.mindupload.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mindupload.app CN=WE1,O=Google Trust Services,C=US 5 Nov 2026 3 Feb 2027 ECDSA 256 ECDSA-SHA256 dd7f1408acbe1cd13da841500d0dbc8
SANs: mindupload.app, mcp.mindupload.app, *.mcp.mindupload.app
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.mindupload.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
mindupload.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://mcp.mindupload.app/.well-known/oauth-protected-resource/mcp", scope="mindupload:consult"

Bearer realm="OAuth", resource_metadata="https://mcp.mindupload.app/.well-known/oauth-protected-resource/mcp", scope="mindupload:consult"

Protected resource metadata

Document https://mcp.mindupload.app/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://mcp.mindupload.app/mcp
Authorisation server https://mcp.mindupload.app

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.mindupload.app/mcp Verified 200
http (plaintext) http://mcp.mindupload.app/mcp HTTPS enforced 301 https://mcp.mindupload.app/mcp
MCP tools · 8 exposed · ~1,513 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
connection_status ~32

Show which Mind Upload account approval and consciousnesses this connection uses, its status, and how to disconnect or revoke it.

Input schema present but exposes no named parameters.

NameTypeReqDescription
statusstringyes–

No examples provided.

consult_mind ~440

Ask the owner's Mind Upload consciousness, an AI built from the owner's own memories, values and way of thinking, how they would approach this task. Call it before any task that will change files or run a commit, push, release, deploy, migration or deletion, and again when a consequential decision changes the plan. It can add what the owner stored in Mind Upload and your instructions do not hold: their priorities, the tradeoffs they accept, past mistakes and what “done” means to them. Put the goal, constraints, options and your proposed approach in one question; it cannot read your files, so share screenshots, recordings or audio as evidence files (evidence_files, or share_evidence and then evidence_ids). On success it returns decision, a reply in that consciousness's own words and in the language of the question, and consciousness, naming who answered, plus the analysis status of each evidence file or media link. The reply is advice, not permission. Skip it only for questions that change nothing.

NameTypeReqDescription
clone_idstring–Only when the owner approved several consciousnesses: the clone_id the owner chose.
decision_idstringyesNew for each distinct question; reuse the same value only to retry an identical call.
evidence_idsarray–Ids from share_evidence whose files you uploaded; the consciousness reads their analysis. Not with media_evidence or learn.
learnboolean–True only when the owner wants their mind to learn from this exchange. Needs the owner's learning permission; what it learns waits for the owner's review unless they auto-keep. Not with evidence file…
media_evidencearray–Optional HTTPS links the user authorized to screenshots, audio or video of the result. Not with evidence files in one call. The reply's media_analysis says whether each link was analyzed, refused or…
questionstringyesThe goal, constraints, options and proposed approach, and the decision that needs the owner's judgment.
task_idstringyesStable identifier for the whole task. Reuse it across consult_mind and review_work so later calls include earlier exchanges.
NameTypeReqDescription
decisionstring––
reviewstring––
statusstringyes–

No examples provided.

disconnect ~27

End this Mind Upload connection and the owner approval behind it. Only when the owner asks to disconnect.

Input schema present but exposes no named parameters.

NameTypeReqDescription
statusstringyes–

No examples provided.

list_pending_memories ~67

List memories waiting for the owner's review, so the owner can go through them with you. Needs the "review pending memories" permission.

NameTypeReqDescription
clone_idstring–Only when the owner approved several consciousnesses: the clone_id the owner chose.
pageinteger––
NameTypeReqDescription
statusstringyes–

No examples provided.

remember ~81

Save a note, decision or fact into the owner's consciousness, when the owner asks. It waits for their review unless they auto-keep. Needs the "save memories" permission.

NameTypeReqDescription
clone_idstring–Only when the owner approved several consciousnesses: the clone_id the owner chose.
source_labelstring––
textstringyes–
NameTypeReqDescription
statusstringyes–

No examples provided.

review_pending_memory ~107

Approve, reject or rewrite one pending memory, only as the owner decides. Needs the "review pending memories" permission.

NameTypeReqDescription
clone_idstring–Only when the owner approved several consciousnesses: the clone_id the owner chose.
decisionstringyes–
expected_content_revisionstringyesThe content_revision list_pending_memories returned for this memory.
textstring–Only with decision update: the rewritten memory.
text_idstringyes–
NameTypeReqDescription
statusstringyes–

No examples provided.

review_work ~643

Before you tell the user that a task which changed files, or ran a commit, push, release, deploy, migration or deletion, is done, call review_work with the original request, the diff excerpts and the test output you observed; if review_work is unavailable or fails, say plainly that no Mind Upload review ran. It asks the owner's Mind Upload consciousness to review the work against the original request, the evidence you supply, and the rules and past mistakes it remembers. Supply the original request, the actual result or diff excerpts, and the verification output you observed; it cannot read files or run tests, so a claim that tests passed is not evidence. Share screenshots, recordings or audio of the result as evidence files (evidence_files, or share_evidence and then evidence_ids), not inside the evidence text. user_request, work and evidence share one size limit with the review instructions the connector adds: about 6,400 characters together after JSON escaping, less with media links. An oversized call is refused before anything is sent. On success it returns review, findings by severity in the language of the user request, naming what it finds missing or wrong, and consciousness, naming who answered, plus the analysis status of each evidence file or media link. That reply is an opinion, not approval: investigate each finding, fix what is real, and review the changed work under a new review_id. Call it once per finished task, and again after material fixes.

NameTypeReqDescription
clone_idstring–Only when the owner approved several consciousnesses: the clone_id the owner chose.
evidencestringyesVerification you observed: commands with their output, observations and known limitations. Paste output; a statement that tests passed is not evidence. Redact secrets first. Shares one size limit wit…
evidence_idsarray–Ids from share_evidence whose files you uploaded; the consciousness reads their analysis. Not with media_evidence or learn.
learnboolean–True only when the owner wants their mind to learn from this exchange. Needs the owner's learning permission; what it learns waits for the owner's review unless they auto-keep. Not with evidence file…
media_evidencearray–Optional HTTPS links the user authorized to screenshots, audio or video of the result. Not with evidence files in one call. The reply's media_analysis says whether each link was analyzed, refused or…
phasestring–completion before reporting the task done; plan or progress only at a risky checkpoint.
review_idstringyesNew for each changed version of the work or evidence; reuse the same value only to retry an identical call.
task_idstringyesStable identifier for the whole task. Reuse it across consult_mind and review_work so later calls include earlier exchanges.
user_requeststringyesThe user's original request and acceptance criteria, in their words where possible. Shares one size limit with work and evidence.
workstringyesWhat you actually changed or produced: focused result or diff excerpts and the scope you claim. Shares one size limit with user_request and evidence.
NameTypeReqDescription
decisionstring––
reviewstring––
statusstringyes–

No examples provided.

share_evidence ~116

Share a screenshot, recording or audio clip of the work privately with the owner's consciousness. Returns an evidence_id and an upload URL: upload the file's bytes with your shell, then pass evidence_ids to review_work or consult_mind. Analyzed for that task only, never kept as a memory.

NameTypeReqDescription
clone_idstring–Only when the owner approved several consciousnesses: the clone_id the owner chose.
content_typestringyes–
file_size_bytesintegeryes–
filenamestringyes–
NameTypeReqDescription
statusstringyes–

No examples provided.

Install

How do I install the Mind Upload AI meta harness MCP server?

Mind Upload AI meta harness is a hosted endpoint at https://mcp.mindupload.app/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.mindupload.app

# add to Claude Code
claude mcp add --transport http voidborn-industries-mindupload 'https://mcp.mindupload.app/mcp'
Common questions

What is the Mind Upload AI meta harness MCP server?

Mind Upload AI meta harness is an MCP server listed in the public MCP registry as io.github.Voidborn-Industries/mindupload. Your AI mind directs coding agents; work reviewed against your memories: Claude Code, Codex, Cursor. This page covers its hosted endpoint (https://mcp.mindupload.app/mcp).

Is the Mind Upload AI meta harness MCP server safe to use?

Mind Upload AI meta harness scores 81 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 Mind Upload AI meta harness MCP server expose?

Mind Upload AI meta harness exposes 8 tools: consult_mind, review_work, share_evidence, remember, list_pending_memories, and 3 more. Their descriptions and schemas cost roughly 1,513 tokens of context every time the server is loaded.

Does the Mind Upload AI meta harness MCP server require authentication?

Yes. Mind Upload AI meta harness asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Mind Upload AI meta harness MCP server still maintained?

Mind Upload AI meta harness 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 Mind Upload AI meta harness MCP server?

VerifyMCP ran 13 checks on Mind Upload AI meta harness, 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.