Rust DocsSAFE
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
An MCP (Model Context Protocol) server that provides access to Rust documentation from docs.rs. This server allows AI tools to search for documentation, type information, feature flags, version numbers, and symbol definitions/source code.
Features
- Search for crates on docs.rs
- Get documentation for specific crates and versions
- Get type information (structs, enums, traits, etc.)
- Get feature flags for crates
- Get available versions for crates
- Get source code for specific items
- Search for symbols within crates
Installation
This project uses Bun for development, but the built server can run with Node.js.
# Clone the repository git clone https://github.com/yourusername/rust-docs-mcp-server.git cd rust-docs-mcp-server # Install dependencies bun install
Building
# Build the server bun run build
This will create a build directory with the compiled JavaScript files.
Running
# Run the development server bun run dev # Or run the built server bun run start
Usage with MCP Clients
This server implements the Model Context Protocol and can be used with any MCP client. To use it with an MCP client, you'll need to configure the client to connect to this server.
Available Tools
The server provides the following tools:
search_crates: Search for crates on docs.rsget_crate_documentation: Get documentation for a specific crateget_type_info: Get type information for a specific itemget_feature_flags: Get feature flags for a crateget_crate_versions: Get available versions for a crateget_source_code: Get source code for a specific itemsearch_symbols: Search for symbols within a crate
Testing
# Run tests bun test
License
MIT
f073a2ae1e7bOBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add rust-docs-mcp-server -- npx -y [email protected]
{
"mcpServers": {
"rust-docs-mcp-server": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}Exposed tools (7)
7 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
get_crate_documentation | read | |
get_crate_versions | read | |
get_feature_flags | read | |
get_source_code | read | |
get_type_info | read | |
search_crates | read | |
search_symbols | read |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (2 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (3)
.clinerules
@biomejs/biome, @modelcontextprotocol/sdk, axios, cheerio, pino, turndown, zod, @types/bun
Gates applied: no_behavioural_pass, no_license.
f073a2ae1e7bfull audit observations/trust-audit/mcp-server/laptou__rust-docs-1.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | f073a2ae1e7b | SAFE | B | 89 | first audit |
Questions
What tools does Rust Docs expose?
7 in total: 7 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Rust Docs safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Rust Docs need?
No credential environment variables were found in its source, so it appears to need none.
How does Rust Docs run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as rust-docs-mcp-server at 1.0.0.
How current is this page?
The grade is for one exact copy of the source (f073a2ae1e7b), read on 2026-10-08. The repository is watched and re-audited when it changes.