All servers · Scraping & browsing

VoteShip

io.github.MattKilmer/voteship · v0.2.3

Has write/delete tools

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2025-06-18
Rank score	—
Declared risk	Has destructive tools (destructiveHint)
Capabilities declared	prompts, resources, tools
Tool definitions	4 tools · with description 100% · input schema is an object 100% · read/destructive hints 100%

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

streamable-http · https://voteship.app/mcp

claude mcp add --transport http voteship https://voteship.app/mcp

{
  "mcpServers": {
    "voteship": {
      "url": "https://voteship.app/mcp"
    }
  }
}

submit_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
browse_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.
upvote_post write/delete
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.
add_public_comment
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.

Repository · Website · JSON · Text for agents · Registry updated 2026-08-22