Model Context Protocol moderate risk

Rust Docs

This MCP server provides up-to-date Rust crate documentation to LLMs, improving code generation accuracy by querying current API details via semantic search and summarization.

Connections & Capabilities

Connects To

GitHubStripe

Capabilities

read

Quickstart

Config

{
  "mcpServers": {
    "rust-docs-reqwest": {
      "command": "/path/to/your/rustdocs_mcp_server",
      "args": [
        "reqwest@0.12"
      ],
      "env": {
        "OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE"
      },
      "disabled": false,
      "alwaysAllow": []
    },
    "rust-docs-async-stripe": {
      "command": "rustdocs_mcp_server",
      "args": [
        "async-stripe@0.40",
        "-F",
        " runtime-tokio-hyper-rustls"
      ],
      "env": {
        "OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE"
      },
      "disabled": false,
      "alwaysAllow": []
    }
  }
}

Exposed MCP Tools (1)

safe

query_rust_docs

Queries the documentation for a specified Rust crate and returns a summarized answer based on semantic search.

Read-only access to documentation; no destructive operations.

Safety Assessment

This server is relatively safe for read-only documentation access. Risks are primarily associated with the OpenAI API key management and potential supply chain vulnerabilities during crate download. Ensure the OpenAI API key is securely stored and consider using a trusted registry to mitigate supply chain risks.

Read-only access to crate documentation.
Sandboxed execution via `cargo doc`.
No direct filesystem access beyond caching.
Limited network access only for crate download and OpenAI API.

Requires an OpenAI API key, potentially exposing it if misconfigured.
Relies on external services (OpenAI) for embeddings and summarization.
Vulnerable to supply chain attacks if `cargo doc` downloads malicious crate dependencies.
Potential for information leakage if OpenAI logs sensitive data from documentation queries.