# VoteShip (remote · voteship.app)

Manage feature requests, votes, roadmaps, and changelogs from any MCP client.

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

## Components

- remote · `voteship.app`: 83/100 (this document), [markdown](https://verifymcp.io/servers/mattkilmer-voteship/voteship.md), [page](https://verifymcp.io/servers/mattkilmer-voteship/voteship)
- npm · `@voteship/mcp-server`: 86/100, [markdown](https://verifymcp.io/servers/mattkilmer-voteship/voteship-mcp-server.md), [page](https://verifymcp.io/servers/mattkilmer-voteship/voteship-mcp-server)

## Channel facts

- Endpoint: `https://voteship.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.3`

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

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (upvote_post).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 593 tokens (~98/item across 6 items; 4 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the VoteShip MCP server?

VoteShip is a hosted endpoint at https://voteship.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 mattkilmer-voteship 'https://voteship.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "mattkilmer-voteship": {
      "url": "https://voteship.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mattkilmer-voteship": {
      "type": "http",
      "url": "https://voteship.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mattkilmer-voteship]
url = "https://voteship.app/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add mattkilmer-voteship --url 'https://voteship.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mattkilmer-voteship:
    url: "https://voteship.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mattkilmer-voteship": {
      "Transport": "http",
      "Url": "https://voteship.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mattkilmer-voteship -t streamable-http -u 'https://voteship.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "mattkilmer-voteship": {
      "type": "http",
      "url": "https://voteship.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-09-21 (score 83, +1)

- [security] Stability: 0.97 → pass

### 2026-09-19 (score 82, +1)

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

### 2026-09-17 (score 81, +1)

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

### 2026-09-15 (score 80, +1)

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

### 2026-09-13 (score 79, +1)

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

### 2026-09-10 (score 78, +1)

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

### 2026-09-08 (score 77, +1)

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

### 2026-09-06 (score 76, +1)

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

## MCP tools (4)

### `submit_feature_request` (~164 tokens)

Submit a feature request

Use this when the user wants to send new product feedback to a public VoteShip board without administering the project. Submit a feature request to any public VoteShip board. No API key needed. The post is created as PENDING and requires board owner approval. Include metadata.source to identify your agent.

Input parameters:

- `description` (string): Detailed description of the feature request
- `email` (string): Submitter's email (for follow-up notifications)
- `project_slug` (string): Project slug (e.g. 'my-app'). Optional if VOTESHIP_PROJECT_SLUG env var is set.
- `source` (string): Name of the agent or app submitting this request (stored in metadata.source)
- `title` (string, required): Feature request title (max 200 chars)

Output parameters:

- `result`: The VoteShip API result for this operation

### `browse_board` (~94 tokens)

Browse a feature board

Use this when the user wants to inspect, compare, or interact with approved requests on a public VoteShip board. View approved feature requests on a public VoteShip board. No API key needed. Returns posts sorted by vote count and renders an interactive board in MCP Apps clients.

Input parameters:

- `project_slug` (string): Project slug (e.g. 'my-app'). Optional if VOTESHIP_PROJECT_SLUG env var is set.

Output parameters:

- `boardUrl` (string)
- `posts` (array)
- `projectSlug` (string)

### `upvote_post` (~81 tokens)

Toggle a feature-request vote

Use this when the user explicitly wants to add or remove their agent identity's vote on a known VoteShip post. Vote or unvote on a feature request (toggles). Uses a deterministic anonymous ID so the same agent on the same machine has a consistent identity. No API key needed.

Input parameters:

- `post_id` (string, required): The post ID to vote on

Output parameters:

- `result`: The VoteShip API result for this operation

### `add_public_comment` (~98 tokens)

Comment on a public request

Use this when the user wants to add public context or a follow-up to a known VoteShip feature request. Add a comment to a feature request on a public VoteShip board. No API key needed. Requires an author name.

Input parameters:

- `author_name` (string, required): Display name for the comment author
- `body` (string, required): Comment text (max 5000 chars)
- `post_id` (string, required): The post ID to comment on

Output parameters:

- `result`: The VoteShip API result for this operation

## Diagnostics

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

## Score history

- 2026-09-21: 83
- 2026-09-20: 82
- 2026-09-19: 82
- 2026-09-18: 81
- 2026-09-17: 81
- 2026-09-16: 80
- 2026-09-15: 80
- 2026-09-14: 79
- 2026-09-13: 79
- 2026-09-12: 78
- 2026-09-11: 78
- 2026-09-10: 78
- 2026-09-09: 77
- 2026-09-08: 77
- 2026-09-07: 76
- 2026-09-06: 76
- 2026-09-05: 75
- 2026-09-04: 75
- 2026-09-03: 74
- 2026-09-02: 74
- 2026-09-01: 73
- 2026-08-31: 73
- 2026-08-30: 72
- 2026-08-29: 72
- 2026-08-28: 71
- 2026-08-27: 71
- 2026-08-26: 71
- 2026-08-25: 69
- 2026-08-24: 68
- 2026-08-23: 68

## Common questions

### What is the VoteShip MCP server?

VoteShip is an MCP server listed in the public MCP registry as io.github.MattKilmer/voteship. Manage feature requests, votes, roadmaps, and changelogs from any MCP client. This page covers its hosted endpoint (https://voteship.app/mcp).

### Is the VoteShip MCP server safe to use?

VoteShip scores 83 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 VoteShip MCP server expose?

VoteShip exposes 4 tools: submit_feature_request, browse_board, upvote_post, add_public_comment. Their descriptions and schemas cost roughly 437 tokens of context every time the server is loaded.

### Does the VoteShip MCP server require authentication?

No. We connected to VoteShip without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the VoteShip MCP server still maintained?

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

## Links

- Remote endpoint: https://voteship.app/mcp
- Repository: https://github.com/MattKilmer/voteship-agent-toolkit
- Website: https://voteship.app/developers
- Changelog RSS feed: https://verifymcp.io/servers/mattkilmer-voteship/voteship.xml
- Changelog JSON feed: https://verifymcp.io/servers/mattkilmer-voteship/voteship.json
- HTML version of this page: https://verifymcp.io/servers/mattkilmer-voteship/voteship