noback
REMOTE · APPS.NOBACK.PAGE
Publish AI-made HTML apps as shareable links that save and sync data. No account or token needed.
Available components
Last scanned (38 minutes ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1027 tokens (~256/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
- Tool “create_app” rewrote its description, which is the text the model reads security
- Tool “get_sdk” rewrote its description, which is the text the model reads security
- Tool “update_app” rewrote its description, which is the text the model reads security
- Tool “validate_app” rewrote its description, which is the text the model reads security
- Schema quality: 150 → 256 ▼ functional
- Tool coverage: 89% → 100% ▲ functional
- Schema quality: good → excellent functional
- “create_app” reworded the description of “html” cosmetic
- “create_app” reworded the description of “name” cosmetic
- “create_app” reworded the description of “zipBase64” cosmetic
- “update_app” reworded the description of “appId” cosmetic
- “update_app” reworded the description of “editKey” cosmetic
- “update_app” reworded the description of “html” cosmetic
- “update_app” reworded the description of “zipBase64” cosmetic
- “validate_app” reworded the description of “html” cosmetic
- “validate_app” reworded the description of “zipBase64” cosmetic
- 2 Nov 26 +5
- HTTPS: unverified → pass ▲ security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
- Tool “create_app” rewrote its description, which is the text the model reads security
- 28 Oct 26 0
- Tool “validate_app” rewrote its description, which is the text the model reads security
- 27 Oct 26 0
- Tool “create_app” rewrote its description, which is the text the model reads security
- Tool “validate_app” rewrote its description, which is the text the model reads security
- 26 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://apps.noback.page/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=noback.page | CN=YE1,O=Let's Encrypt,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6dfc28347494998bc8703de4c028868ae75 |
| SANs: *.noback.page, noback.page | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of apps.noback.page. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| page. | present | 64712 | 8 | Verified |
| noback.page. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://apps.noback.page/mcp | Verified | 200 | |
| http (plaintext) | http://apps.noback.page/mcp | HTTPS enforced | 301 | https://apps.noback.page/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_app ~384
Publishes a new app with no account or token, from html or zipBase64. It runs the same checks as validate_app (errors make it fail, with the list and how to fix them). The app is deleted if nobody uses it for 30 days, and it can reach the internet only through the services on noback's list. Its link opens your copy: whoever opens it sees what you entered and can leave their own things (comments, sign-ups, orders) without touching anyone else's; if the app asks for sensitive data, everyone starts their own empty copy. Returns appId, version, openUrl, editKey, claimUrl, message and warnings. Tell the person message ("Your app is ready: <openUrl>") in the language of the conversation, with no extra explanations. Then ask them once "Want to save it to your account?" (in the language of the conversation) and give them claimUrl only if they say yes: it's private, only for that person, and lets them keep the app. Keep appId and editKey to publish changes to THIS same app with update_app; don't create another one. Never put editKey or claimUrl in the HTML, the data or a shared link.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | – | The complete contents of ONE HTML file, with its CSS and JS inline. Don't add the noback SDK by hand: noback injects window.app. Send html or zipBase64, not both. |
| name | string | – | Optional name for the app, shown to the people who use it (e.g. "Family groceries"). |
| zipBase64 | string | – | A complete .zip package encoded in base64, instead of html: index.html at the root, an optional noback.toml, plus scripts, styles and files. Send html or zipBase64, not both. |
No output schema declared.
No examples provided.
get_sdk ~84
Returns noback's guide for writing apps (in English, as Markdown in `markdown`): how to make a single-file HTML app whose data is saved and shared (localStorage, window.storage or app.db), what works inside noback and what doesn't, packages, limits and how to publish. Read it once before writing or changing an app for noback. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
update_app ~269
Publishes a new version of the same app without an account, using the appId and editKey from create_app, with the same checks as create_app. The data and the shared link stay as long as you keep the same app.db collections and fields and the same localStorage keys. Returns openUrl, version, message and warnings. Tell the person openUrl in the language of the conversation; give them claimUrl (private) only if they want to save the app to their account.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | The app's short id, as returned by create_app or list_apps (e.g. "a-x7k2pq"). |
| editKey | string | yes | The private edit key returned by create_app. Never put it in the HTML, the data or a shared link. |
| html | string | – | The complete contents of ONE HTML file, with its CSS and JS inline. Don't add the noback SDK by hand: noback injects window.app. Send html or zipBase64, not both. |
| zipBase64 | string | – | A complete .zip package encoded in base64, instead of html: index.html at the root, an optional noback.toml, plus scripts, styles and files. Send html or zipBase64, not both. |
No output schema declared.
No examples provided.
validate_app ~290
Checks an app (html or zipBase64) against noback's rules, with the limits of an app without an account, without publishing anything or running its code. Use it before create_app or update_app. Returns { ok, errors, warnings }; each item has a code, a message and a fix. Fix every error before publishing; warnings are suggestions and the app works anyway. Without an account, the app can reach the internet only through the services on noback's list. If warnings include NO_APP_DB with certain: true, the app loses what people enter when the page reloads: save it in localStorage (the warning's prompt says what to change) before publishing. If warnings include STATIC_LIST, the content is written by hand in the page: offer to make it editable from the page, with only the owner writing (the warning's prompt says what to ask for). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | – | The complete contents of ONE HTML file, with its CSS and JS inline. Don't add the noback SDK by hand: noback injects window.app. Send html or zipBase64, not both. |
| zipBase64 | string | – | A complete .zip package encoded in base64, instead of html: index.html at the root, an optional noback.toml, plus scripts, styles and files. Send html or zipBase64, not both. |
No output schema declared.
No examples provided.
How do I install the noback MCP server?
noback is a hosted endpoint at https://apps.noback.page/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · apps.noback.page
claude mcp add --transport http app-noback-noback 'https://apps.noback.page/mcp'
What is the noback MCP server?
noback is an MCP server listed in the public MCP registry as app.noback/noback. Publish AI-made HTML apps as shareable links that save and sync data. No account or token needed. This page covers its hosted endpoint (https://apps.noback.page/mcp).
Is the noback MCP server safe to use?
noback scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the noback MCP server expose?
noback exposes 4 tools: get_sdk, validate_app, create_app, update_app. Their descriptions and schemas cost roughly 1,027 tokens of context every time the server is loaded.
Does the noback MCP server require authentication?
No. We connected to noback without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the noback MCP server still maintained?
noback is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.