mcpbeat Sign in

Shipstar MCP Server

answering

Shipstar is answering right now. Last checked 15 min ago.

Generate changelogs, release emails, help-center articles, banners, and social posts from commits.

Uptime history 38 days of history · worst day 99%
38 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
400 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Shipstar missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.shipstar.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.shipstar.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.shipstar.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.shipstar.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.shipstar.ai/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.shipstar.ai/mcp streamable-http sign-in 433 ms 15 min ago

Alternatives to Shipstar

same job, measured the same way
Fiber AI
by fiber

Search companies, enrich contacts, and reveal emails and phones from your AI agent.

5 tools answering
Banger
by bangermail

All your company email, operated by agents and reviewed by you.

answering
Hyades
by apology-is-policy

Render LaTeX math as pure Unicode text art for terminals, code comments, and emails.

1 tools answering
Versium REACH
by versium

Enrich leads, generate prospect lists, and validate emails using Versium's B2B2C identity graph.

answering
Dead Simple Email
by deadsimple

Give an agent its own inbox: send, receive, and pull signup codes from real email.

941 installs/wk 14 tools answering
Hedwig
by hedwig-ai

Read, arrange, and build agents on your Hedwig email board from any AI client. Nothing ever sends.

answering
OutSend
by outsend

Find local businesses, enrich them with emails and socials, and run lead pipelines from your AI.

answering
Cold Email
by bluecraft-ai

Generate hyper-personalized cold email sequences via AI.

6 tools answering

Shipstar — questions

Answers built from our own checks of this server.

Why is there no tool list for Shipstar?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Shipstar working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 400 ms. The bar chart above shows every period we have measured.
How do I connect Shipstar?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Shipstar?
No API key is involved. Shipstar answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Shipstar?
It answers our handshake in 400 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.