VoteShip
REMOTE · VOTESHIP.APP · 2 COMPONENTS
Manage feature requests, votes, roadmaps, and changelogs from any MCP client.
Available components
Last scanned (9 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Project Management
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (upvote_post). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 593 tokens (~98/item across 6 items; 4 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
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 →
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.
- 7 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 22 Aug 26 0
First indexed and scored.
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 7 Nov 2026 · Probed https://voteship.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=voteship.app | CN=YR2,O=Let's Encrypt,C=US | 21 Oct 2026 | 19 Jan 2027 | RSA 2048 | SHA256-RSA | 6ab5a2eedb554b9d850f08d43353c751b68 |
| SANs: voteship.app | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of voteship.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| voteship.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://voteship.app/mcp | Verified | 200 | |
| http (plaintext) | http://voteship.app/mcp | HTTPS enforced | 308 | https://voteship.app/mcp |
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 →
add_public_comment Comment on a public request ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| author_name | string | yes | Display name for the comment author |
| body | string | yes | Comment text (max 5000 chars) |
| post_id | string | yes | The post ID to comment on |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The VoteShip API result for this operation |
No examples provided.
browse_board Browse a feature board ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project_slug | string | – | Project slug (e.g. 'my-app'). Optional if VOTESHIP_PROJECT_SLUG env var is set. |
| Name | Type | Req | Description |
|---|---|---|---|
| boardUrl | string | yes | – |
| posts | array | yes | – |
| projectSlug | string | yes | – |
No examples provided.
submit_feature_request Submit a feature request ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Detailed description of the feature request |
| 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 | yes | Feature request title (max 200 chars) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The VoteShip API result for this operation |
No examples provided.
upvote_post Toggle a feature-request vote ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | string | yes | The post ID to vote on |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | – | The VoteShip API result for this operation |
No examples provided.
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.
remote · voteship.app
claude mcp add --transport http mattkilmer-voteship 'https://voteship.app/mcp'
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 82 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 7 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 VoteShip MCP server?
VerifyMCP ran 14 checks on VoteShip, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.