# Mind Upload AI meta harness (remote · mcp.mindupload.app)

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

- Trust score: 81/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.mindupload.app`: 81/100 (this document), [markdown](https://verifymcp.io/servers/voidborn-industries-mindupload/mcp.md), [page](https://verifymcp.io/servers/voidborn-industries-mindupload/mcp)
- npm · `mindupload`: 81/100, [markdown](https://verifymcp.io/servers/voidborn-industries-mindupload/mindupload-2.md), [page](https://verifymcp.io/servers/voidborn-industries-mindupload/mindupload-2)
- pypi · `mindupload`: 59/100, [markdown](https://verifymcp.io/servers/voidborn-industries-mindupload/mindupload.md), [page](https://verifymcp.io/servers/voidborn-industries-mindupload/mindupload)

## Channel facts

- Endpoint: `https://mcp.mindupload.app/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.19.0`

## 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-11-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 74% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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 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.

### Claude

```bash
claude mcp add --transport http voidborn-industries-mindupload 'https://mcp.mindupload.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "voidborn-industries-mindupload": {
      "url": "https://mcp.mindupload.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "voidborn-industries-mindupload": {
      "type": "http",
      "url": "https://mcp.mindupload.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.voidborn-industries-mindupload]
url = "https://mcp.mindupload.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "voidborn-industries-mindupload": {
      "type": "remote",
      "url": "https://mcp.mindupload.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add voidborn-industries-mindupload --url 'https://mcp.mindupload.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  voidborn-industries-mindupload:
    url: "https://mcp.mindupload.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "voidborn-industries-mindupload": {
      "Transport": "http",
      "Url": "https://mcp.mindupload.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add voidborn-industries-mindupload -t streamable-http -u 'https://mcp.mindupload.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "voidborn-industries-mindupload": {
      "type": "http",
      "url": "https://mcp.mindupload.app/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-11-21 (score 81, +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.

### 2026-11-19 (score 80, +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.

### 2026-11-17 (score 79, +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.

### 2026-11-15 (score 78, +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.

### 2026-11-13 (score 77, +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.

### 2026-11-12 (score 76, 0)

- [security] 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
- [functional improvement] Schema quality: 276 → 240

### 2026-11-11 (score 76, +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.

### 2026-11-09 (score 75, +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.

## MCP tools (8)

### `consult_mind` (~440 tokens)

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.

Input parameters:

- `clone_id` (string): Only when the owner approved several consciousnesses: the clone_id the owner chose.
- `decision_id` (string, required): New for each distinct question; reuse the same value only to retry an identical call.
- `evidence_ids` (array): Ids from share_evidence whose files you uploaded; the consciousness reads their analysis. Not with media_evidence or learn.
- `learn` (boolean): 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_evidence` (array): 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…
- `question` (string, required): The goal, constraints, options and proposed approach, and the decision that needs the owner's judgment.
- `task_id` (string, required): Stable identifier for the whole task. Reuse it across consult_mind and review_work so later calls include earlier exchanges.

Output parameters:

- `decision` (string)
- `review` (string)
- `status` (string)

### `review_work` (~643 tokens)

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.

Input parameters:

- `clone_id` (string): Only when the owner approved several consciousnesses: the clone_id the owner chose.
- `evidence` (string, required): Verification 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_ids` (array): Ids from share_evidence whose files you uploaded; the consciousness reads their analysis. Not with media_evidence or learn.
- `learn` (boolean): 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_evidence` (array): 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…
- `phase` (string): completion before reporting the task done; plan or progress only at a risky checkpoint.
- `review_id` (string, required): New for each changed version of the work or evidence; reuse the same value only to retry an identical call.
- `task_id` (string, required): Stable identifier for the whole task. Reuse it across consult_mind and review_work so later calls include earlier exchanges.
- `user_request` (string, required): The user's original request and acceptance criteria, in their words where possible. Shares one size limit with work and evidence.
- `work` (string, required): What you actually changed or produced: focused result or diff excerpts and the scope you claim. Shares one size limit with user_request and evidence.

Output parameters:

- `decision` (string)
- `review` (string)
- `status` (string)

### `share_evidence` (~116 tokens)

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.

Input parameters:

- `clone_id` (string): Only when the owner approved several consciousnesses: the clone_id the owner chose.
- `content_type` (string, required)
- `file_size_bytes` (integer, required)
- `filename` (string, required)

Output parameters:

- `status` (string)

### `remember` (~81 tokens)

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.

Input parameters:

- `clone_id` (string): Only when the owner approved several consciousnesses: the clone_id the owner chose.
- `source_label` (string)
- `text` (string, required)

Output parameters:

- `status` (string)

### `list_pending_memories` (~67 tokens)

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

Input parameters:

- `clone_id` (string): Only when the owner approved several consciousnesses: the clone_id the owner chose.
- `page` (integer)

Output parameters:

- `status` (string)

### `review_pending_memory` (~107 tokens)

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

Input parameters:

- `clone_id` (string): Only when the owner approved several consciousnesses: the clone_id the owner chose.
- `decision` (string, required)
- `expected_content_revision` (string, required): The content_revision list_pending_memories returned for this memory.
- `text` (string): Only with decision update: the rewritten memory.
- `text_id` (string, required)

Output parameters:

- `status` (string)

### `connection_status` (~32 tokens)

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

Output parameters:

- `status` (string)

### `disconnect` (~27 tokens)

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

Output parameters:

- `status` (string)

## Diagnostics

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

## Score history

- 2026-11-21: 81
- 2026-11-20: 80
- 2026-11-19: 80
- 2026-11-18: 79
- 2026-11-17: 79
- 2026-11-16: 78
- 2026-11-15: 78
- 2026-11-14: 77
- 2026-11-13: 77
- 2026-11-12: 76
- 2026-11-11: 76
- 2026-11-10: 75
- 2026-11-09: 75
- 2026-11-08: 74
- 2026-11-07: 74
- 2026-11-06: 73
- 2026-11-05: 73

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

## Links

- Remote endpoint: https://mcp.mindupload.app/mcp
- Repository: https://github.com/Voidborn-Industries/mindupload-sdk-python
- Website: https://docs.mindupload.app/mcp
- Changelog RSS feed: https://verifymcp.io/servers/voidborn-industries-mindupload/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/voidborn-industries-mindupload/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/voidborn-industries-mindupload/mcp.json
- HTML version of this page: https://verifymcp.io/servers/voidborn-industries-mindupload/mcp
