VPS Hardening
Read-only security checklists: VPS hardening, Docker, secrets, Supabase, Stripe, auth, AI agents.
Sollte ich dies verwenden
Qualität und Sicherheit
Befunde (1)
- LOWin vpshardening__get_blueprint_overview
Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.
Kontextkosten
Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.
Installieren
Installation mit einem Klick
Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:
{
"mcpServers": {
"vps-hardening": {
"url": "https://notesupreme.com/p/vps-hardening?token=nsp_6bmDN1j4mZCnQJCfL0rgDA"
}
}
}Remote-Endpunkte
https://notesupreme.com/p/vps-hardening?token=nsp_6bmDN1j4mZCnQJCfL0rgDAstreamable-httpWas es kann
Tool-Inventar
Tools (5)
🟡vpshardening__read_node(node_id, with_links, heading, cursor)
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.
Eingabe-Schema
{
"type": "object",
"properties": {
"node_id": {
"type": "string",
"maxLength": 512
},
"with_links": {
"type": "boolean"
},
"heading": {
"type": "string",
"maxLength": 200
},
"cursor": {
"type": "string",
"maxLength": 2048
}
},
"required": [
"node_id"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🔴vpshardening__search_nodes(query, node_type, type, cursor)
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).
Eingabe-Schema
{
"type": "object",
"properties": {
"query": {
"type": "string",
"maxLength": 1000
},
"node_type": {
"type": "string"
},
"type": {
"type": "string"
},
"cursor": {
"type": "string",
"maxLength": 2048
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢vpshardening__list_ship_nodes(cursor)
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.
Eingabe-Schema
{
"type": "object",
"properties": {
"cursor": {
"type": "string",
"maxLength": 2048
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢vpshardening__get_ship_digest(section_id, cursor)
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 }.
Eingabe-Schema
{
"type": "object",
"properties": {
"section_id": {
"type": "string",
"maxLength": 512
},
"cursor": {
"type": "string",
"maxLength": 2048
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢vpshardening__get_blueprint_overview(node_id, section_id, cursor)
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 }.
Eingabe-Schema
{
"type": "object",
"properties": {
"node_id": {
"type": "string"
},
"section_id": {
"type": "string",
"maxLength": 512
},
"cursor": {
"type": "string",
"maxLength": 2048
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}Community
Nachweis