# Twin Me Up (pypi · twin-me-up)

A personal work twin for every AI agent: your confirmed guidance and explicit grants, enforced.

- Trust score: 50/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `twin-me-up`: 50/100 (this document), [markdown](https://verifymcp.io/servers/gitdakky-twin-me-up/twin-me-up.md), [page](https://verifymcp.io/servers/gitdakky-twin-me-up/twin-me-up)

## Channel facts

- Registry: `pypi`
- Package: `twin-me-up`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-05.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 4 of 36 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to GitDakky/twin-me-up).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 20 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the Twin Me Up MCP server?

Twin Me Up runs locally as a PyPI package, launched with uvx twin-me-up. 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 gitdakky-twin-me-up -- uvx twin-me-up
```

### Cursor

```json
{
  "mcpServers": {
    "gitdakky-twin-me-up": {
      "command": "uvx",
      "args": [
        "twin-me-up"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "gitdakky-twin-me-up": {
      "command": "uvx",
      "args": [
        "twin-me-up"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add gitdakky-twin-me-up -- uvx twin-me-up
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gitdakky-twin-me-up": {
      "type": "local",
      "command": [
        "uvx",
        "twin-me-up"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add gitdakky-twin-me-up --command uvx --arg twin-me-up
```

### Hermes

```yaml
mcp_servers:
  gitdakky-twin-me-up:
    command: "uvx"
    args: ["twin-me-up"]
```

### Netclaw

```json
{
  "McpServers": {
    "gitdakky-twin-me-up": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "twin-me-up"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add gitdakky-twin-me-up -t stdio -c uvx -a twin-me-up
```

### Other

```json
{
  "mcpServers": {
    "gitdakky-twin-me-up": {
      "command": "uvx",
      "args": [
        "twin-me-up"
      ]
    }
  }
}
```

## 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-03 (score 50, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 35, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-29 (score 50, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-25 (score 35, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-23 (score 50, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-21 (score 35, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-17 (score 50, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-16 (score 35, −15)

- [security regression] Malware scan: pass → unverified

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/gitdakky-twin-me-up/twin-me-up#diagnostics

## Score history

- 2026-11-05: 50
- 2026-11-04: 50
- 2026-11-03: 50
- 2026-11-02: 35
- 2026-11-01: 50
- 2026-10-31: 50
- 2026-10-30: 50
- 2026-10-29: 50
- 2026-10-28: 35
- 2026-10-27: 35
- 2026-10-26: 35
- 2026-10-25: 35
- 2026-10-24: 50
- 2026-10-23: 50
- 2026-10-22: 35
- 2026-10-21: 35
- 2026-10-20: 50
- 2026-10-19: 50
- 2026-10-18: 50
- 2026-10-17: 50
- 2026-10-16: 35
- 2026-10-15: 50
- 2026-10-14: 50

## Common questions

### What is the Twin Me Up MCP server?

Twin Me Up is an MCP server listed in the public MCP registry as io.github.GitDakky/twin-me-up. A personal work twin for every AI agent: your confirmed guidance and explicit grants, enforced. This page covers its PyPI package (twin-me-up).

### Is the Twin Me Up MCP server safe to use?

Twin Me Up scores 50 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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.

### Is the Twin Me Up MCP server still maintained?

Twin Me Up is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Twin Me Up MCP server under?

Twin Me Up declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/twin-me-up/
- Socket report: https://socket.dev/pypi/package/twin-me-up
- Repository: https://github.com/GitDakky/twin-me-up
- Changelog RSS feed: https://verifymcp.io/servers/gitdakky-twin-me-up/twin-me-up.xml
- Changelog JSON feed: https://verifymcp.io/servers/gitdakky-twin-me-up/twin-me-up.json
- HTML version of this page: https://verifymcp.io/servers/gitdakky-twin-me-up/twin-me-up