Two MCP servers over Wasmer: an Edge-deployed Postgres/observability server and
Two MCP servers over Wasmer: an Edge-deployed Postgres/observability server and a host-local wasmer_sdk sandbox companion — a DX exercise with an issue-ready feedback ledger
active Production-safe Score 85/100 http no auth
At a glance
| Endpoint | https://wasmer-sandbox-mcp.wasmer.app/mcp |
|---|---|
| Source | https://github.com/francisco-perez-sorrosal/wasmer-sandbox-mcp |
| Transport | http |
| Tools | 6 |
| Auth | none |
| First seen | 2026-09-06 03:22:30 |
| Last checked | 2026-11-17 22:02:53 |
Observed reliability
| 7-day uptime | 99% |
|---|---|
| 24-hour uptime | 99% |
| Handshake success | 99% |
| Latency p50 / p95 | 1273 / 1617 ms |
| Last successful check | 2026-11-17 22:02:53 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (6)
get_server_info— Report this deployed instance's identity, database health, versions and uptime. Use it to confirm which build is live, whether the instancestore_echo— Save a note that outlives this conversation, and get back its id. Use it whenever something should still be findable in a later session: aget_echo— Fetch one stored note by the id `store_echo` or `list_echoes` returned. Use it when you already have an id. To find one, use `list_echoes`.list_echoes— Browse stored notes newest-first, optionally narrowed by tag or message text. Use it to find a note whose id you do not have. `tag` matchesrecord_feedback— Report friction you hit while using Wasmer, so it reaches the maintainers. Use it when something about the Wasmer SDK, Edge, anybuild, thelist_feedback— Read back recorded Wasmer friction reports, newest first. Use it to check whether something has already been reported before adding a dupli
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 22:02:53 | ✓ | ✓ | 83 ms | 99 | active |
| 2026-11-17 21:47:52 | ✓ | ✓ | 180 ms | 95 | active |
| 2026-11-17 21:32:51 | ✓ | ✓ | 94 ms | 99 | active |
| 2026-11-17 21:17:51 | ✓ | ✓ | 203 ms | 95 | active |
| 2026-11-17 21:02:51 | ✓ | ✓ | 91 ms | 99 | active |
| 2026-11-17 20:47:51 | ✓ | ✓ | 257 ms | 95 | active |
| 2026-11-17 20:32:51 | ✓ | ✓ | 92 ms | 99 | active |
| 2026-11-17 20:17:51 | ✓ | ✓ | 251 ms | 95 | active |
| 2026-11-17 20:02:51 | ✓ | ✓ | 76 ms | 99 | active |
| 2026-11-17 19:47:51 | ✓ | ✓ | 188 ms | 95 | active |
| 2026-11-17 19:32:51 | ✓ | ✓ | 96 ms | 99 | active |
| 2026-11-17 19:17:51 | ✓ | ✓ | 323 ms | 92 | active |
| 2026-11-17 19:02:51 | ✓ | ✓ | 79 ms | 99 | active |
| 2026-11-17 18:47:51 | ✓ | ✓ | 247 ms | 95 | active |
| 2026-11-17 18:32:50 | ✓ | ✓ | 93 ms | 99 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://wasmer-sandbox-mcp.wasmer.app/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/wasmer-sandbox-mcp-wasmer-app-mcp # JSON