noback
v1.0.0Publish AI-made HTML apps as shareable links that save and sync data. No account or token needed.
Endpoint health
online- Last checked
- 11/20/2026, 8:17:13 AM
- Latency
- 474 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:app.noback%2Fnoback
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"app.noback/noback": {
"url": "https://apps.noback.page/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
6 shown · authentication unknown
connect
Optional: you don't need it, create_app asks for approval by itself the first time you publish. Asks the person for approval without publishing anything (agent is your name, like "Claude Code"). Returns url, code, pollKey and message. Take the person to url yourself: open it in their browser if you can (open on macOS, xdg-open on Linux, start on Windows, or navigate there if you have a browser); if you can't, show them the link in one line in the language of the conversation. Then call connect_status with pollKey and carry on by yourself as soon as it's approved, without asking the person to type anything. Never put pollKey in an app.
Schema valid · SHA-256 5db120a437d5…
View input schema
{ "type": "object", "properties": { "agent": { "description": "Your name as the person knows you (e.g. \"Claude Code\", \"Codex\", \"ChatGPT\").", "type": "string", "maxLength": 40 } }, "$schema": "http://json-schema.org/draft-07/schema#" }connect_status
Waits (up to 20 seconds) for the person to approve the request that create_app, update_app or connect started, and answers as soon as they do. Returns status: pending (call it again), slow_down (wait a few seconds, then call it again), approved (with token and kind: account or anonymous), denied or expired. The token comes only once: right away call create_app or update_app again with credential: token, and keep sending it on every publish. Never show it to the person or put it in an app.
Schema valid · SHA-256 f7d74a10a853…
View input schema
{ "type": "object", "properties": { "pollKey": { "type": "string", "description": "The pollKey from connect in create_app's or update_app's answer (or from connect)." } }, "required": [ "pollKey" ], "$schema": "http://json-schema.org/draft-07/schema#" }
Connections
streamable-http
https://apps.noback.page/mcp