Is the io.github.FoundryNet/mint-mcp MCP server working?

Is the io.github.FoundryNet/mint-mcp MCP server working?

No, not as the registry describes it. 4 declared endpoints failed the MCP initialize handshake on 2026-09-17 — the protocol's own way of asking a server to identify itself. No tool was ever called.

ERR-2026-3003, ERR-2026-3004, ERR-2026-3005, ERR-2026-3006

Why can't I reach the io.github.FoundryNet/mint-mcp API?

Its declared address answered neither a request nor a TLS handshake on 2026-09-17, across 16 cases. This is a weaker finding than a host that does not exist: a server can be temporarily down.

ERR-2026-2994, ERR-2026-2995, ERR-2026-2996, ERR-2026-2997, ERR-2026-2998, ERR-2026-2999, ERR-2026-3000, ERR-2026-3001, ERR-2026-3002, ERR-2026-3007, ERR-2026-3008, ERR-2026-3009

Every record behind those answers

20 open records, observed 2026-09-10. Every claim below carries the command that disproves it. If one is wrong, it should be withdrawn — 111 have been across the whole registry.

server error (16)

The declared origin answered with a server error.

Check it yourself:

curl -s -X POST https://academic-intel-mcp-production.up.railway.app/mcp -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"check","version":"1"}}}'

the endpoint is gone (4)

The endpoint this registry entry declares returns 404 or 410 to the MCP initialize handshake.

Check it yourself:

curl -s -X POST https://foundrynet-geo-production.up.railway.app/mcp -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"check","version":"1"}}}'

Also filed as: io.github.FoundryNet, io.github.FoundryNet/academic-intel-mcp, io.github.FoundryNet/brand-intel-mcp, io.github.FoundryNet/compliance-mcp, io.github.FoundryNet/crypto-intel-mcp, io.github.FoundryNet/currency-intel-mcp, io.github.FoundryNet/cyber-intel-mcp, io.github.FoundryNet/email-verify-mcp. One page, because two sweeps named the same subject differently and the record that mattered was on the page nobody would open.

If a record here is wrong

Run its check. If the answer differs from what is written, say so here and it will be withdrawn — 111 already have been. A record nobody can contest is a record asking to be trusted, which is the opposite of the point.

What this page does not tell you

This is not a clean bill of health for anything not listed. The registry was built from a sample of two directories, and an operation absent from it was almost certainly never examined. Silence here means not looked at, not looked at and fine — which is the same mistake this registry exists to record in other people.

What this is

A record of defects in the public description of machine-callable operations: documents a directory claims are live and are not, hosts that no longer resolve, specifications that contradict the API they describe. It is not a ranking, not a review, and not a judgement about the service. No credential is ever sent to anything listed here.

The whole registry, machine-readable: errata.json. Index of subjects: index.html.

Built from registry errata-2026-09-10@21826040e38a. If manifest.json shows a different one, this page is behind the records and should not be trusted over them.