Skip to content

noback MCP server

app.noback/nobacknoback.appstreamable-httpv1.0.0Scanned

Publish AI-made HTML apps as shareable links that save and sync data. No account or token needed.

4 tools: 2 do something that can't be undone and 2 only read.

Tools: 0 delete, 2 irreversible, 0 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the noback MCP server can do

The noback MCP server is published by noback.app, a domain the MCP Registry verified. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (create_app and update_app), but cannot delete data. 2 tools only read.

1 tool reads private data (get_sdk); 1 tool brings in text other people can write (get_sdk).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Can't be undone 2Claude Code: ask
  • create_appPublishes a new app with no account or token, from html or zipBase64.No findings

    Why it is in this group

    • The name "create_app" says "create": a word for a change.
    • The description's first verb is "publish": a word for a change that another call does not undo.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
  • update_appPublishes 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.No findings

    Why it is in this group

    • The name "update_app" says "update": a word for a change.
    • The description's first verb is "publish": a word for a change that another call does not undo.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
Only reads 2Show 2 read-only tools
  • get_sdkReturns 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 …Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_sdk" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "file": it reads files.
    • untrusted-inputThe description's first sentence says "return" and "html": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
  • validate_appChecks 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.No findings

    Why it is in this group

    • The name "validate_app" says "validate": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:22 UTC, unchanged since Nov 16, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://apps.noback.page/.well-known/oauth-protected-resource/mcp
Authorization servers
https://apps.noback.page
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (2 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://apps.noback.page/mcp: tools/list returned 6 tools to an anonymous client, including create_app (irreversible), update_app (irreversible), connect (write)

    What this check looks for

Posture changes

  1. Nov 16, 2026
    • Tools that change things, listed without credentials: 2 to 3
    • RFC 9728 protected resource metadata: none to https://apps.noback.page/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://apps.noback.page
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3; RFC 9728 protected resource metadata: none -> https://apps.noback.page/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://ap…View diff
    • Tools that change things, listed without credentials: 2 to 3
    • RFC 9728 protected resource metadata: none to https://apps.noback.page/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://apps.noback.page
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to yes
  2. Tools4 changed.~4 changedView diff
    • Changed:create_appCan't be undonedescriptioninputSchema
    • Changed:get_sdkOnly readsdescription
    • Changed:update_appCan't be undonedescriptioninputSchema
    • Changed:validate_appOnly readsdescriptioninputSchema

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http noback https://apps.noback.page/mcp
claude mcp add --transport http noback https://apps.noback.page/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__noback__get_sdk",
      "mcp__noback__validate_app"
    ],
    "ask": [
      "mcp__noback__create_app",
      "mcp__noback__update_app"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as noback. Review it before you use it.

Capability tags behind 1 rule
  • mcp__noback__get_sdk private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.noback/noback/verify?hash=dedfcc600c9b54a36a31be78676ff05154868e7581f081be61d98f718aac3cd2" | jq -e '.changed == false'

Pinned hash dedfcc600c9b, from Nov 9, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.noback/noback/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.noback/noback
[![Anlyon Radar](https://radar.anlyon.com/badge/app.noback/noback.svg)](https://radar.anlyon.com/servers/app.noback/noback)

Source: MCP Registry. Synced Oct 25, 2026, 13:17 UTC.

noback MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the noback MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the noback MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the noback MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: create_app and update_app.

What tools does the noback MCP server have?

4 tools: 2 irreversible, 2 read. create_app, update_app, get_sdk and validate_app.

Does the noback MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the noback MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the noback MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.