Findings on what compounds and supplements do in the body, with evidence strength, quote and paper.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 699 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Other
Publish AI-made HTML apps as shareable links that save and sync data. No account or token needed.
1 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 3 | 1 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using noback
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http noback https://apps.noback.page/mcpCapabilities
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.
DiscoveredReturns 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.
DiscoveredPublishes 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.
DiscoveredChecks 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.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 1184 ms | 4 |