app.polypane/polypane
Polypane
Is the Polypane MCP server down? It gave no valid answer in the probe of 2026-11-20: not found. One failed probe is not an outage.
Check and fix websites in Polypane: every viewport at once, with accessibility and layout checks.
not found no valid answer since 2026-11-20 · probed 2026-11-20
command not found: /opt/Polypane/polypane
- Bundle
- https://github.com/Polypane/agent-plugins/releases/download/v32.0.1/polypane.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
- Host
- github.com
- Repository
- https://github.com/Polypane/agent-plugins
- Website
- https://polypane.app/docs/automation/
- Registry
- active, updated 2026-11-19 · registry entry
Compare this server with others.
More servers
Other registry entries on github.com, the ones next to this name; all of them.
- KeySlip app.keyslip/keyslip · alive
- Kilobat app.kilobat/kilobat · crashed on start
- M1K3 app.m1k3/m1k3 · error
- MetaDock app.metadock/metadock · not found
- PostSail app.postsail/postsail · alive
- ScreenPost app.screenpost/screenpost · alive
- ShowTake app.showtake/showtake · crashed on start
- Filmlog cc.filmlog/filmlog · crashed on start
Servers that mention accessibility or viewport.
- Sitejar Web Compliance Scanner app.sitejar/mcp · needs auth
- com.benriscore/api · needs auth
- Chateaupedia com.chateaupedia/chateaux · server error
- Gachi Data API — Japan Station & Accessibility Data com.gachi-tokusuru/japan-data-api · alive
- Inclusify Accessibility com.inclusifyapp/inclusify · needs auth
- Jeikin com.jeikin/mcp · needs auth
- Lazynext Accessibility Checker com.lazynext/accessibility-checker · alive
- Sitelemetry com.sitelemetry/sitelemetry · needs auth
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-20. 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 endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.