NSD.SG MCP server
io.github.aarif86/nsd-sgaarif86streamable-httpv0.14.10Scanned
Put the page your AI made online at yourname.nsd.sg. Publish, update, list and remove sites.
6 tools: 1 can delete or cancel things, 1 do something that can't be undone, 1 change things and 3 only read.
- Reads private data · 2
- Reads text others write · 2
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 1 does 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.
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 NSD.SG MCP server can do
The NSD.SG MCP server is published by the GitHub account aarif86. It has 6 tools. It can delete or cancel things (1 tool: nsd_delete_site), do things that cannot be undone, such as sending, paying or publishing (nsd_publish) and create or change data (1 tool: nsd_update). 3 tools only read.
2 tools read private data (nsd_get_site and nsd_read_file); 2 tools bring in text other people can write (nsd_list_sites and nsd_get_site); 1 tool can send data out of your system (nsd_publish). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
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 16, 2026, version 0.14.10.
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.
6 tools
Deletes or cancels 1Claude Code: deny
nsd_delete_siteDelete a site and all its versions.No findings
Why it is in this group
- The name "nsd_delete_site" says "delete": a word for removing or ending something.
Description, as the server wrote it Delete a site and all its versions. Requires the site id (never a name). The address becomes free for anyone.
Can't be undone 1Claude Code: ask
nsd_publishPut a page online at <name>.nsd.sg.Can send data outNo findings
Why it is in this group
- The name "nsd_publish" says "publish": a word for a change that another call does not undo.
What it can reach
- outboundThe name "nsd_publish" says "publish": it sends or publishes something to other people.
Description, as the server wrote it Put a page online at <name>.nsd.sg. Give a site name and either the full HTML of the page or a list of files. Creates the site if you do not have it yet; on a site you already own it adds or replaces the given files and keeps the rest. Returns the live URL. IMPORTANT: if any file contains <script>, on*= attributes or javascript:, send it as files with encoding "base64" (standard base64 of the UTF-8 text); the hosting firewall rejects such code sent as plain text with a bare 403 Forbidden. When in doubt, always use base64. FORMS: a page can collect replies (RSVP, order, contact, sign-up) with a plain <form method="post" action="https://nsd.sg/f/<name>">; each field needs a name attribute, replies go to the owner's dashboard and email, visitors never log in. Add <input type="text" name="_gotcha" style="display:none" tabindex="-1" autocomplete="off"> against spam, and optionally <input type="hidden" name="_next" value="https://<name>.nsd.sg/thanks"> to send the visitor to your own thank-you page. No file uploads in forms. A brand-new address usually gets HTTPS within a few minutes, rarely up to 15 (the browser shows a secure-connection error until then); always pass that on to the user when the result says ready: false.
Changes things 1Claude Code: ask
nsd_updateReplace ALL files of an existing site with the given HTML or files.No findings
Why it is in this group
- The name "nsd_update" says "update": a word for a change.
Description, as the server wrote it Replace ALL files of an existing site with the given HTML or files. Older versions are kept and can be restored from the dashboard. Same rule as nsd_publish: anything containing <script>, on*= attributes or javascript: must be sent as files with encoding "base64", or the hosting firewall refuses it with 403.
Only reads 3Show 3 read-only tools
nsd_get_siteOne site: URL, status, files, storage used and the plan's limits.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "nsd_get_site" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it One site: URL, status, files, storage used and the plan's limits.
nsd_list_sitesList the caller's sites: id, name, live URL, status, plan and days of free period left.Reads text others writeNo findings
Why it is in this group
- The name "nsd_list_sites" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it List the caller's sites: id, name, live URL, status, plan and days of free period left.
nsd_read_fileRead one file of a live site, exactly as it is online now.Reads private dataNo findings
Why it is in this group
- The name "nsd_read_file" says "read": a word for reading.
What it can reach
- private-dataThe name "nsd_read_file" says "read" and "file": it reads files.
- private-dataThe description's first sentence says "read" and "file": it reads files.
Description, as the server wrote it Read one file of a live site, exactly as it is online now. Use it before a small change ("change the price", "fix the date") in a chat that does not have the page yet: read the file, change only what the user asked, then send it back with nsd_publish under the same name. Text files come back as text, images and other binary files as base64. Max 1 MB.
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.
4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__nsd-sg__nsd_publish"
]
}
}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.
Looked at Nov 18, 2026, 16:24 UTC, unchanged since Nov 11, 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
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://nsd.sg/mcp: tools/list returned 6 tools to an anonymous client, including nsd_delete_site (destructive), nsd_publish (irreversible), nsd_update (write)
Posture changes
- Nov 11, 2026
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 3
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
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.
Tools1 changed.~1 changedView diff
- Changed:nsd_publishCan't be undonedescription
PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 3 (and 2 more).View diff
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 3
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
Install
Pinned to version 0.14.10. Values in angle brackets are yours to fill in.
claude mcp add --transport http nsd-sg https://nsd.sg/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http nsd-sg https://nsd.sg/mcp --header 'Authorization: <your-authorization>'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.
{
"permissions": {
"allow": [
"mcp__nsd-sg__nsd_list_sites",
"mcp__nsd-sg__nsd_get_site",
"mcp__nsd-sg__nsd_read_file"
],
"ask": [
"mcp__nsd-sg__nsd_publish",
"mcp__nsd-sg__nsd_update"
],
"deny": [
"mcp__nsd-sg__nsd_delete_site"
]
}
}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 nsd-sg. Review it before you use it.
Capability tags behind 4 rules
- mcp__nsd-sg__nsd_publish outbound
- mcp__nsd-sg__nsd_list_sites untrusted-input
- mcp__nsd-sg__nsd_get_site private-data, untrusted-input
- mcp__nsd-sg__nsd_read_file private-data
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/io.github.aarif86/nsd-sg/verify?hash=ebf5b87af3743f4066c3ff32a7e33294e760cf0d49b64d246013b3c8debefcd4" | jq -e '.changed == false'Pinned hash ebf5b87af374, from Nov 16, 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/io.github.aarif86/nsd-sg/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.aarif86/nsd-sg)Source: MCP Registry · repository. Synced Nov 16, 2026, 04:17 UTC.
NSD.SG MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the NSD.SG MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 3 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 NSD.SG MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: nsd_delete_site.
Can the NSD.SG MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: nsd_publish.
What tools does the NSD.SG MCP server have?
- 6 tools: 1 destructive, 1 irreversible, 1 write, 3 read. nsd_delete_site, nsd_publish, nsd_update, nsd_list_sites, nsd_get_site and nsd_read_file.
Does the NSD.SG MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the NSD.SG MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): nsd_publish.
Has the NSD.SG MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.