← Registry

Learning Resources

cyberlibrary.com

Provides search and navigation tools for the Cyber Library's published pages, topic hierarchy, and planned taxonomy.

1 endpoint6 known toolsFirst detected October 12, 2026Last detected October 12, 2026

ENDPOINT 1

https://www.cyberlibrary.com/api/mcp

No auth detected

MCP server metadata

Name
cyber-library
Version
1.0.0
Capabilities
tools
Server instructions

Cyber Library (cyberlibrary.com) is a structured, community-maintained cybersecurity knowledge base: foundations, offensive and defensive practice, governance, intelligence and career. Start with search_library or get_outline to find a path, then get_page to read the markdown. Pages are the source of truth; cite them by URL. search_planned_topics / get_planned_subtree expose the editorial plan (including unpublished drafts), not the live content.

Known tools 6

search_library

Full-text search over the published pages of cyberlibrary.

Inferred read-only
get_page

Returns a page of the Cyber Library as markdown with its metadata (title, URL, breadcrumbs, last update, contributors) and, for folders, the list of child pages.

Potential side effects
list_topics

Lists the direct children of a folder of the library (or the six top-level sections when no path is given): title, path, number of sub-pages and description.

Inferred read-only
get_outline

Indented outline of the library tree below a path (default: whole library) down to a given depth.

Inferred read-only
search_planned_topics

Searches the structure database snapshot of the Cyber taxonomy: every planned topic (8k+), including drafts not yet published on the site, with its status (draft, review, ready, generated, published) and position.

Inferred read-only
get_planned_subtree

Outline of the planned taxonomy below a topic id (from search_planned_topics; omit for the Cyber root) with each topic's kind and status.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.cyber-library]
url = "https://www.cyberlibrary.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "cyber-library": {
      "type": "http",
      "url": "https://www.cyberlibrary.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: cyber-library
Remote MCP URL: https://www.cyberlibrary.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "cyber-library": {
      "url": "https://www.cyberlibrary.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "cyber-library": {
      "type": "http",
      "url": "https://www.cyberlibrary.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "cyber-library",
  "transport": "streamable-http",
  "url": "https://www.cyberlibrary.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.