VPS Hardening is an MCP server published by io.github.NoteSupreme, hosted at notesupreme.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 5 tools, including vpshardening__read_node, vpshardening__search_nodes, vpshardening__list_ship_nodes, vpshardening__get_ship_digest, vpshardening__get_blueprint_overview.
Read-only security checklists: VPS hardening, Docker, secrets, Supabase, Stripe, auth, AI agents.
3 connections through 5 shared values. Tap any node.
Read one node's full markdown body + frontmatter by node_id. Response includes outbound_links[] (resolved graph edges) unless with_links:false, plus source attribution. Pass heading (e.g. "Tactics") to get ONLY that markdown section — a few hundred chars instead of the whole body; every heading read, hit or miss, carries the node's headings list, and a miss is heading_not_found — so a guessed heading is cheap (heading "" just lists the headings). A heading read is partial — never write it back as a node's content; re-read without heading first. A long body is returned one page at a time — when the response says truncated, call again with { cursor } to continue it.
| Parameter | Type | Description |
|---|---|---|
| cursor | string | |
| heading | string | |
| node_id * | string | |
| with_links | boolean |
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
{
"name": "vpshardening__read_node",
"description": "Read one node's full markdown body + frontmatter by node_id. Response includes outbound_links[] (resolved graph edges) unless with_links:false, plus source attribution. Pass heading (e.g. \"Tactics\") to get ONLY that markdown section — a few hundred chars instead of the whole body; every heading read, hit or miss, carries the node's headings list, and a miss is heading_not_found — so a guessed heading is cheap (heading \"\" just lists the headings). A heading read is partial — never write it back as a node's content; re-read without heading first. A long body is returned one page at a time — when the response says truncated, call again with { cursor } to continue it.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"node_id"
],
"properties": {
"cursor": {
"type": "string",
"maxLength": 2048
},
"heading": {
"type": "string",
"maxLength": 200
},
"node_id": {
"type": "string",
"maxLength": 512
},
"with_links": {
"type": "boolean"
}
}
}
}Search nodes by text, node_type, and/or semantic `type`. Token-AND across title + description + tags. Primary retrieval path — use it before reading bodies. Results are ranked best match first — `score` on each row is the match strength (title hits count double). Page 1 is the top of the ranking. A one-word query can match hundreds of rows — put two or more terms in `query` so the top rows are the answer, not a dump. Terms are AND-ed: if two return nothing, drop one. Reports total_matches; when more matches exist than fit in one response, narrow the query or pass { cursor } for the next page (a cursor is only valid for the query that produced it).
| Parameter | Type | Description |
|---|---|---|
| type | string | |
| query | string | |
| cursor | string | |
| node_type | string |
{
"name": "vpshardening__search_nodes",
"description": "Search nodes by text, node_type, and/or semantic `type`. Token-AND across title + description + tags. Primary retrieval path — use it before reading bodies. Results are ranked best match first — `score` on each row is the match strength (title hits count double). Page 1 is the top of the ranking. A one-word query can match hundreds of rows — put two or more terms in `query` so the top rows are the answer, not a dump. Terms are AND-ed: if two return nothing, drop one. Reports total_matches; when more matches exist than fit in one response, narrow the query or pass { cursor } for the next page (a cursor is only valid for the query that produced it).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"type": {
"type": "string"
},
"query": {
"type": "string",
"maxLength": 1000
},
"cursor": {
"type": "string",
"maxLength": 2048
},
"node_type": {
"type": "string"
}
}
}
}List every node: node_id, title, parent_id, node_type, plus type/description/tags/resource when set. No bodies. This is a flat list of the WHOLE Ship — on a large one it is long and arrives in pages, so pass { cursor } to continue. To navigate rather than enumerate, use vpshardening__get_ship_digest.
| Parameter | Type | Description |
|---|---|---|
| cursor | string |
{
"name": "vpshardening__list_ship_nodes",
"description": "List every node: node_id, title, parent_id, node_type, plus type/description/tags/resource when set. No bodies. This is a flat list of the WHOLE Ship — on a large one it is long and arrives in pages, so pass { cursor } to continue. To navigate rather than enumerate, use vpshardening__get_ship_digest.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"cursor": {
"type": "string",
"maxLength": 2048
}
}
}
}Orient on this Ship — ALWAYS call this first. With no arguments it returns the section MAP and nothing else: every top-level section with its description and child_count, which is small and cheap even on a Ship of hundreds of nodes. Then pass { section_id } to list one section's direct children, and vpshardening__read_node for the ones worth reading. A large section arrives in pages — continue it with { cursor }.
| Parameter | Type | Description |
|---|---|---|
| cursor | string | |
| section_id | string |
{
"name": "vpshardening__get_ship_digest",
"description": "Orient on this Ship — ALWAYS call this first. With no arguments it returns the section MAP and nothing else: every top-level section with its description and child_count, which is small and cheap even on a Ship of hundreds of nodes. Then pass { section_id } to list one section's direct children, and vpshardening__read_node for the ones worth reading. A large section arrives in pages — continue it with { cursor }.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"cursor": {
"type": "string",
"maxLength": 2048
},
"section_id": {
"type": "string",
"maxLength": 512
}
}
}
}Read the human-AUTHORED overview prose for the Ship (omit node_id) or for one section. Useful only where someone has written a summary; it is not the way to navigate — vpshardening__get_ship_digest is the map, call that first. When no summary has been written this falls back to the same section map vpshardening__get_ship_digest returns, drilled with { section_id } and paged with { cursor }.
| Parameter | Type | Description |
|---|---|---|
| cursor | string | |
| node_id | string | |
| section_id | string |
{
"name": "vpshardening__get_blueprint_overview",
"description": "Read the human-AUTHORED overview prose for the Ship (omit node_id) or for one section. Useful only where someone has written a summary; it is not the way to navigate — vpshardening__get_ship_digest is the map, call that first. When no summary has been written this falls back to the same section map vpshardening__get_ship_digest returns, drilled with { section_id } and paged with { cursor }.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"cursor": {
"type": "string",
"maxLength": 2048
},
"node_id": {
"type": "string"
},
"section_id": {
"type": "string",
"maxLength": 512
}
}
}
}Free, read-only security library: research-backed VPS hardening and app security checklists, every point linked to its sources. SECTIONS - 🛡️ VPS Hardening: Research Findings (how servers got hacked in 2026 + the setup people agree on), Round 2 Findings (Cloudflare Tunnel + Access service tokens, Docker skipping UFW, getting API keys off servers), Tailscale vs Cloudflare, Sources. - 🔐 App Security Checklists: 9 topics, each with a Checklist (Playbook) and Sources (Reference): 1 Free trial & API abuse · 2 Database security · 3 Bad packages & supply chain · 4 AI agent & MCP risks · 5 Backups & recovery · 6 Monitoring & alerts · 7 Login & auth · 8 Payments & Stripe · 9 Safe deployments & rollbacks. HOW TO USE 1. For a topic, search_nodes with 2 words, e.g. "checklist payments", "checklist database", "docker firewall", "tailscale cloudflare". 2. read_node the Checklist first; open the matching Sources node when the user wants proof or links. 3. Cite sources when quoting. This is general information, not professional security advice. TAGS: app-security · checklist · sources · free-trial-abuse · database · supply-chain · ai-agents · backups · monitoring · authentication · payments · deployments · vps-security · docker · tailscale · cloudflare-tunnel · cloudflare-access · supabase · stripe.
Names, descriptions and schemas were written by the server and are shown as data.