TridentStack Control Docs

Search and read TridentStack Control documentation: patching, vulnerabilities, compliance, API.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
97%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~481Tokens (tool definitions)
~783 BTypical response size
Minimal attention impact (0.38% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "docs": {
      "url": "https://docs.tridentstack.com/mcp"
    }
  }
}

Remote endpoints

https://docs.tridentstack.com/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢search_docs(query, source, limit)

Full-text search over TridentStack Control's customer documentation (guides, API reference, changelog, roadmap). Returns ranked results with titles, URLs, and snippets. Use this first to find relevant docs, then get_doc to read one in full. It also covers reference formats, including the Endpoint Checks import file format, so an assistant can write a check file a customer imports. Before writing or making calls to the TridentStack Control REST API, search for "API rate limits and efficient polling": it explains which endpoints answer a question in the fewest requests and how to handle a 429.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Natural-language or keyword query"
    },
    "source": {
      "description": "Restrict to one content type",
      "type": "string",
      "enum": [
        "guide",
        "api",
        "changelog",
        "roadmap"
      ]
    },
    "limit": {
      "description": "Max results (default 8)",
      "type": "integer",
      "minimum": 1,
      "maximum": 25
    }
  },
  "required": [
    "query"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢get_doc(id)

Return the full markdown of a single documentation chunk by its id (from a search_docs result). Only ids present in the index are valid; this never fetches arbitrary URLs.

Input Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "A doc id from search_docs, e.g. guide:rings#phases"
    }
  },
  "required": [
    "id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢list_docs(source)

List the documentation catalog (id, title, source, url), optionally filtered to one content type. Use to browse structure before searching.

Input Schema

{
  "type": "object",
  "properties": {
    "source": {
      "description": "Restrict to one content type",
      "type": "string",
      "enum": [
        "guide",
        "api",
        "changelog",
        "roadmap"
      ]
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools