# io.github.renl/proceed-mcp (npm · @meshimize/proceed-mcp)

Preview Telegram approval broker for MCP clients; live first use unverified.

- Trust score: 24/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@meshimize/proceed-mcp`: 24/100 (this document), [markdown](https://verifymcp.io/servers/renl-proceed-mcp/meshimize-proceed-mcp.md), [page](https://verifymcp.io/servers/renl-proceed-mcp/meshimize-proceed-mcp)

## Channel facts

- Registry: `npm`
- Package: `@meshimize/proceed-mcp`
- Version: `0.1.0-preview.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**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks 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 we can run it.

## Install

### How do I install the io.github.renl/proceed-mcp server?

io.github.renl/proceed-mcp runs locally as an npm package, launched with npx -y @meshimize/proceed-mcp mcp --owner, plus the required operator-owner-id and operator-state-dir, which you supply. The registry lists a positional argument for this package that follows one we could not fill in, so it is left out of this command rather than placed in the wrong position. Check the registry entry for what the server needs. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add renl-proceed-mcp -- npx -y @meshimize/proceed-mcp mcp --owner
```

The registry lists a positional argument for this package that follows one we could not fill in, so it is left out of this command rather than placed in the wrong position. Check the registry entry for what the server needs. Incomplete: the registry marks operator-owner-id and operator-state-dir as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Cursor

```json
{
  "mcpServers": {
    "renl-proceed-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@meshimize/proceed-mcp",
        "mcp",
        "--owner"
      ]
    }
  }
}
```

The registry lists a positional argument for this package that follows one we could not fill in, so it is left out of this command rather than placed in the wrong position. Check the registry entry for what the server needs. Incomplete: the registry marks operator-owner-id and operator-state-dir as required and gives no value we can show, so they are not in this command. Add them before you run it.

### VS Code

```json
{
  "servers": {
    "renl-proceed-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@meshimize/proceed-mcp",
        "mcp",
        "--owner"
      ]
    }
  }
}
```

The registry lists a positional argument for this package that follows one we could not fill in, so it is left out of this command rather than placed in the wrong position. Check the registry entry for what the server needs. Incomplete: the registry marks operator-owner-id and operator-state-dir as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Codex

```bash
codex mcp add renl-proceed-mcp -- npx -y @meshimize/proceed-mcp mcp --owner
```

The registry lists a positional argument for this package that follows one we could not fill in, so it is left out of this command rather than placed in the wrong position. Check the registry entry for what the server needs. Incomplete: the registry marks operator-owner-id and operator-state-dir as required and gives no value we can show, so they are not in this command. Add them before you run it.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "renl-proceed-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@meshimize/proceed-mcp",
        "mcp",
        "--owner"
      ],
      "enabled": true
    }
  }
}
```

The registry lists a positional argument for this package that follows one we could not fill in, so it is left out of this command rather than placed in the wrong position. Check the registry entry for what the server needs. Incomplete: the registry marks operator-owner-id and operator-state-dir as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Hermes

```yaml
mcp_servers:
  renl-proceed-mcp:
    command: "npx"
    args: ["-y", "@meshimize/proceed-mcp", "mcp", "--owner"]
```

The registry lists a positional argument for this package that follows one we could not fill in, so it is left out of this command rather than placed in the wrong position. Check the registry entry for what the server needs. Incomplete: the registry marks operator-owner-id and operator-state-dir as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Netclaw

```json
{
  "McpServers": {
    "renl-proceed-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@meshimize/proceed-mcp",
        "mcp",
        "--owner"
      ]
    }
  }
}
```

The registry lists a positional argument for this package that follows one we could not fill in, so it is left out of this command rather than placed in the wrong position. Check the registry entry for what the server needs. Incomplete: the registry marks operator-owner-id and operator-state-dir as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Other

```json
{
  "mcpServers": {
    "renl-proceed-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@meshimize/proceed-mcp",
        "mcp",
        "--owner"
      ]
    }
  }
}
```

The registry lists a positional argument for this package that follows one we could not fill in, so it is left out of this command rather than placed in the wrong position. Check the registry entry for what the server needs. Incomplete: the registry marks operator-owner-id and operator-state-dir as required and gives no value we can show, so they are not in this command. Add them before you run it.

## 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-05 (score 24)

First indexed and scored.

## 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, Dependencies. The full working is on the page: https://verifymcp.io/servers/renl-proceed-mcp/meshimize-proceed-mcp#diagnostics

## Score history

- 2026-11-05: 24

## Common questions

### What is the io.github.renl/proceed-mcp server?

io.github.renl/proceed-mcp is listed in the public MCP registry as io.github.renl/proceed-mcp. Preview Telegram approval broker for MCP clients; live first use unverified. This page covers its npm package (@meshimize/proceed-mcp).

### Is the io.github.renl/proceed-mcp server safe to use?

io.github.renl/proceed-mcp scores 24 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.renl/proceed-mcp server still maintained?

io.github.renl/proceed-mcp 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 io.github.renl/proceed-mcp server under?

io.github.renl/proceed-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.renl/proceed-mcp server?

VerifyMCP ran 8 checks on io.github.renl/proceed-mcp, covering Known CVEs, Install scripts, Dependency health, Source repository and 4 more. 6 items could not be completed, a gap on our side rather than a finding about io.github.renl/proceed-mcp: Malware scan, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@meshimize/proceed-mcp
- Socket report: https://socket.dev/npm/package/@meshimize/proceed-mcp
- Repository: https://github.com/renl/proceed-mcp
- Changelog RSS feed: https://verifymcp.io/servers/renl-proceed-mcp/meshimize-proceed-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/renl-proceed-mcp/meshimize-proceed-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/renl-proceed-mcp/meshimize-proceed-mcp.json
- HTML version of this page: https://verifymcp.io/servers/renl-proceed-mcp/meshimize-proceed-mcp