io.github.verymint/mint
Mint
Is the Mint MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.
Work journal for coding agents: worklogs, tasks, project state and costs across projects.
needs auth probed 2026-11-14 · unchanged since 2026-10-26 · HTTP 401 · ApiKey
Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthorized","error_description":"Missing or invalid API key. Send \"Authorization: Bearer mint_sk_- Endpoint
- https://verymint.app/api/mcp (streamable-http)
- Host
- verymint.app
- Getting access
- A key or token from the publisher, sent in the Authorization header (ApiKey). The server publishes no OAuth metadata. Store the key once: npx mcpcost auth https://verymint.app/api/mcp --header "Authorization: ApiKey …".
Read from the server's public OAuth metadata, without a token. Method. - Registry
- active, updated 2026-10-24 · registry entry
Compare this server with others.
More servers
Servers that mention mint.
- LLMIntel Model Lifecycle ai.llmintel/model-lifecycle · alive
- Pozeidon ai.pozeidon/pozeidon · needs auth
- Synthetic Data — Random User ai.saifs/synthetic-data-random-user · needs auth
- Offers ca.mattherbert/offers · not found
- ca.swiftsign/mcp · alive
- webhook-inbox co.kymac.inbox/webhook-inbox · no DNS
- com.auto-reader/ocr · alive
- Clypmint com.clypmint/clypmint · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.