Ferritin — Rust documentation
REMOTE · FERRITIN.RS · SCANNED SEP 20
Search and read Rust documentation for the standard library and any crate on crates.io
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability89
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 487 tokens (~243/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Tools include usage examples.Pass
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Ferritin — Rust documentation MCP server?
Ferritin — Rust documentation is a hosted endpoint at https://ferritin.rs/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ferritin.rs
claude mcp add --transport http rs-ferritin-rustdoc 'https://ferritin.rs/mcp'
{
"mcpServers": {
"rs-ferritin-rustdoc": {
"url": "https://ferritin.rs/mcp"
}
}
} {
"servers": {
"rs-ferritin-rustdoc": {
"type": "http",
"url": "https://ferritin.rs/mcp"
}
}
} [mcp_servers.rs-ferritin-rustdoc] url = "https://ferritin.rs/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rs-ferritin-rustdoc": {
"type": "remote",
"url": "https://ferritin.rs/mcp",
"enabled": true
}
}
} openclaw mcp add rs-ferritin-rustdoc --url 'https://ferritin.rs/mcp' --transport streamable-http
mcp_servers:
rs-ferritin-rustdoc:
url: "https://ferritin.rs/mcp" {
"McpServers": {
"rs-ferritin-rustdoc": {
"Transport": "http",
"Url": "https://ferritin.rs/mcp"
}
}
} assistant mcp add rs-ferritin-rustdoc -t streamable-http -u 'https://ferritin.rs/mcp'
{
"mcpServers": {
"rs-ferritin-rustdoc": {
"type": "http",
"url": "https://ferritin.rs/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Sept 26 0
- HSTS header: unverified → fail ▼ security
- DNSSEC: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 2 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Aug 26 0
- Authorization: unverified → partial ▲ security
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Aug 26 0
- Server version: 0.16.0 → 0.17.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://ferritin.rs/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ferritin.rs | CN=YE2,O=Let's Encrypt,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5988d2d1326f2d690669274e8f6ef0818e8 |
| SANs: ferritin.rs | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ferritin.rs. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| rs. | present | 57382 | 13 | Verified |
| ferritin.rs. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ferritin.rs/mcp | Verified | 200 | |
| http (plaintext) | http://ferritin.rs/mcp | HTTPS enforced | 301 | https://ferritin.rs/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get ~96
Show documentation for a Rust item by path.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Item path, e.g. `serde::Deserialize` or `std::vec::Vec`. A crate segment may carry an `@`-suffixed semver requirement (not an exact version): `tokio@1::runtime::Runtime` serves the newest 1.x, while… |
No output schema declared.
{"description":"Look up a trait","path":"serde::Deserialize"}search ~222
Search for items within a crate's documentation, or — without a crate — discover which crate to use.
| Name | Type | Req | Description |
|---|---|---|---|
| crate | string | – | Crate to search within, optionally with an `@`-suffixed semver requirement (not an exact version): `serde`, `tokio@1` (newest 1.x), or `tokio@=1.40` to pin an exact release. **Omit only to discover… |
| query | string | yes | Search query — one or more complete words. With `crate`, matched against item names and documentation prose; without it, against crate names, descriptions, and declared keywords. |
No output schema declared.
{"crate":"serde","description":"Find deserialization items in serde","query":"deserialize"}{"description":"Discover which crate to use for MQTT","query":"mqtt client"}What is the Ferritin — Rust documentation MCP server?
Ferritin — Rust documentation is an MCP server listed in the public MCP registry as rs.ferritin/rustdoc. Search and read Rust documentation for the standard library and any crate on crates.io. This page covers its hosted endpoint (https://ferritin.rs/mcp).
Is the Ferritin — Rust documentation MCP server safe to use?
Ferritin — Rust documentation scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Ferritin — Rust documentation MCP server expose?
Ferritin — Rust documentation exposes 2 tools: get, search. Their descriptions and schemas cost roughly 318 tokens of context every time the server is loaded.
Does the Ferritin — Rust documentation MCP server require authentication?
No. We connected to Ferritin — Rust documentation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Ferritin — Rust documentation MCP server still maintained?
Ferritin — Rust documentation is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.