mcpbeat Sign in

ShipReady Metrics MCP Server

by shipreadymetrics Your server? Claim it
not responding

ShipReady Metrics is listed as active in the registry but did not answer our last check. It exposes 2 tools.

Read-only scan of a public GitHub repo for leaked secrets, with a 0-100 grade.

Uptime history 27 days of history · worst day 0%
27 days agonow
1.1%
Uptime 24h
1 of 92 checks
2
Tools
read from the server
873 ms
Response time
average over 24h
open, no key
Access
streamable-http

ShipReady Metrics does not always answer

Over the last week it answered 1.6% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not 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 2 min ago.

run in your terminal
claude mcp add public-scan --transport http https://shipreadymetrics.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://shipreadymetrics.com/mcp
~/.codex/config.toml
[mcp_servers.public-scan]
url = "https://shipreadymetrics.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "public-scan": {
      "url": "https://shipreadymetrics.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "public-scan": {
      "type": "http",
      "url": "https://shipreadymetrics.com/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

ask
ask_compliance
Find relevant public ShipReady compliance guides. Returns sourced excerpts, not legal advice or an assertion that ShipReady supports a framework.
scan
scan_public_repo
Scan a public GitHub repository using ShipReady's live /scan pipeline. Returns a point-in-time score, counts and up to three findings; no private repos or tenant data. A score is not a certification or release approval.

Endpoints

URLTransportStateLatencyChecked
https://shipreadymetrics.com/mcp streamable-http answering 67 ms 2 min ago

Alternatives to ShipReady Metrics

same job, measured the same way
Audit
by commitshow

Score a public GitHub repo 0-100, or search Legit.Show for launched software by what we measured.

63 installs/wk local only
Cra Check
by holistis

Free read-only check of a public GitHub repo for eight security signals related to the EU CRA.

2 tools answering
GitHub Repository Metrics — Stars, Forks & Issue Counts
by kriton-dev

Read numeric metrics for known public GitHub repositories

answering
Vibescan
by bigfloppy-vibescan

Free security scan for AI-written GitHub repos: leaked keys, .env, eval, SQLi, CORS.

1 tools answering
S
SandboxAPIs
by sandboxapis

Drop-in read-only replicas of GitHub, Jira, Slack and 22 more, preloaded with one fake company.

411 installs/wk local only
Agent Ready Report
by agenticplug

Scan any public website and see how ready it is for AI agents and AI search, explained plainly.

2 tools answering
SafeToClone
by safetoclone

Safety grade (A to F) for any public GitHub repo, in plain English, before you install it.

2 tools answering
Compuute MCP Security Scanner
by compuute

Scan any public GitHub MCP-server repo for security issues. 37 MCP-specific L1 rules, 8 languages.

1 tools answering

ShipReady Metrics — questions

Answers built from our own checks of this server.

What can ShipReady Metrics do?
It exposes 2 tools, read directly from the server on our last check. Among them: ask_compliance, scan_public_repo. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is ShipReady Metrics working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 1 of 92 checks got a reply (1.1%), average response time 873 ms. The bar chart above shows every period we have measured.
The registry lists ShipReady Metrics as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect ShipReady Metrics?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does ShipReady Metrics need an API key?
No. ShipReady Metrics completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is ShipReady Metrics?
It answers our handshake in 873 ms on average, which is faster than 7% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.