io.github.platypus-labs/platypus-db
PlatypusDB
Is the PlatypusDB MCP server down? It gave no valid answer in the probe of 2026-11-15: error. One failed probe is not an outage.
Your PlatypusDB database connections for AI agents, with the access you give each one.
error no valid answer since 2026-11-14 · probed 2026-11-15
spawn /work/bundle/server/platypus-db.exe EACCES
- Bundle
- https://github.com/platypus-labs/platypus-db/releases/download/v0.6.2/platypus-db-0.6.2-windows-x64.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
- Host
- github.com
- Repository
- https://github.com/platypus-labs/platypus-db
- Website
- https://platypus-labs.github.io/platypus-db/
- Registry
- active, updated 2026-11-14 · registry entry
Compare this server with others.
More servers
Other registry entries on github.com, the ones next to this name; all of them.
- NexusInDesign io.github.pironjulien/nexus-indesign · error
- NexusRelay io.github.pironjulien/nexus-relay · error
- NexusWindows io.github.pironjulien/nexus-windows · error
- toss io.github.plamen-g/toss · needs env
- docx4j Word documents io.github.plutext/docx4j-mcp · not found
- AYLENTO · 艾伦兔 io.github.popularzb/aylento · crashed on start
- PortDock MCP io.github.portdock/portdock-mcp · error
- Leanfare io.github.pouriaetab/leanfare · crashed on start
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 package did not start as an MCP server at its probe on 2026-11-15. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
- The probe could not complete the handshake. The error output is above.