io.github.vanja-ivancevic/apex-db
Apex DB
Is the Apex DB MCP server down? It gave no valid answer in the probe of 2026-11-14: not MCP (HTTP 200). One failed probe is not an outage.
Vehicle specifications, emissions, and powertrain data with source provenance.
not MCP no valid answer since 2026-11-14 · probed 2026-11-15 · unchanged since 2026-11-14 · HTTP 200
Streamable HTTP error: Error POSTing to endpoint: {"error":"rate_limited","retry_after_seconds":1}- Endpoint
- https://mcp.apex-db.org/mcp (streamable-http)
- Host
- mcp.apex-db.org
- Protocol
- 2025-11-25
- Reports itself as
- apex 1.0.0
- Capabilities
- tools
- Repository
- https://github.com/vanja-ivancevic/all-db-system
- Registry
- active, updated 2026-11-12 · registry entry
- Changes
- 2 recorded, reachable in 1 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention apex.
- ARADIA | sovereign & private agentic systems com.aradia/sovereign-hardware · timeout
- Vector (Apex Fusion) io.github.Apex-Fusion/vector · alive
- ViewportWitness by Apex Labs io.github.Baffles78/viewport-witness · alive
- AgentPhone-Apex io.github.Evozim/agent-phone · not found
- Apex (smartapex.uk) AI Component Card Store io.github.mickeyappol-create/apex · alive
- ApexVol Options Analytics io.github.ryansilk/apexvol-mcp · needs auth
- Apex by LeadShark — discovery io.github.rzere/linkedin-mcp · alive
- Domain Liveness org.ottobot/domain-liveness · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-14 11:05 | not MCP | 1.0 s | |||
| 2026-11-13 11:46 | alive | 1.6 s | 2 | 497 | 267 |
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
- No valid answer since 2026-11-14. One failed probe is not an outage: the board calls a server down after two days without a valid answer. The next probe runs within a day.
- The endpoint answers HTTP 200, but not with a valid MCP initialize result. Common causes: the URL is a web page or a REST API and not the MCP endpoint, the server answers a JSON-RPC error on initialize, or the response is HTML.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.