dev.simkit/simkit
dev.simkit/simkit
Is the dev.simkit/simkit MCP server down? It gave no valid answer in the probe of 2026-11-17: install failed. One failed probe is not an outage.
See an iOS app's network traffic, mock responses and drive the simulator through SimKit for Mac.
install failed no valid answer since 2026-11-17 · probed 2026-11-20 · unchanged since 2026-11-17
npm error notsup Valid os: darwin npm error notsup Actual os: linux npm error A complete log of this run can be found in: /root/.npm/_logs/2026-11-18T09_08_12_
- Run it
- npx -y simkit-mcp@0.1.0-beta.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/ealtaca/simkit-mcp
- Website
- https://simkit.dev
- Registry
- active, updated 2026-11-16 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- SatRank — Lightning trust + audit oracle dev.satrank/mcp · alive
- ScratchRun dev.scratchrun/mcp · alive
- seekrit (local crypto plane) dev.seekrit/mcp · alive
- dev.sexai/sexai-mcp · crashed on start
- skillhook dev.skillhook/skillhook · alive
- Skillry MCP dev.skillry/skillry · alive
- Small Print dev.smallprint/smallprint · alive
- AXF dev.smartergpt/axf · alive
Servers that mention responses or simulator.
- ai.rise2/figlime · needs auth
- mumo chat.mumo/mcp · alive
- Widgy co.widgy/widgy · needs auth
- Biz Planner com.biz-planner/mcp · needs auth
- BTC DCA Engine com.btcdcaengine/btc-dca-engine · alive
- EarningsWatcher com.earnings-watcher/mcp · needs auth
- FormBuilder com.formbuilder/formbuilder · needs auth
- Formasty com.formasty/form-builder · 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-17. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.