io.github.Wolfe-Jam/rust-faf-mcp
REMOTE · MCPAAS.LIVE
Persistent project context — Rust-native MCP server. IANA-registered .faf format.
Available components
Last scanned (5 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Deprecated
This server is marked deprecated in the MCP registry.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 415 tokens (~34/item across 12 items; 3 tools + 9 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 5 Nov 26 0
- Server version: mcpaas-cf@1.11.11 → mcpaas-cf@1.11.14 functional
- 4 Nov 26 0
- Server version: mcpaas-cf@1.11.7 → mcpaas-cf@1.11.11 functional
- 31 Oct 26 0
- Server version: mcpaas-cf@1.11.5 → mcpaas-cf@1.11.7 functional
- 30 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “faf_score” rewrote its description, which is the text the model reads security
- Tool “faf_validate” rewrote its description, which is the text the model reads security
- Schema quality: 22 → 34 ▼ functional
- Schema quality: fair → good functional
- Server version: mcpaas-cf@1.11.3 → mcpaas-cf@1.11.5 functional
- 20 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 20 → 22 ▼ functional
- Schema quality: good → fair functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: mcpaas-cf@1.11.2 → mcpaas-cf@1.11.3 functional
- 19 Oct 26 0
- Server version: mcpaas-cf@1.11.1 → mcpaas-cf@1.11.2 functional
- 18 Oct 26 0
- Server version: mcpaas-cf@1.11.0 → mcpaas-cf@1.11.1 functional
- 17 Oct 26 0
- Server version: mcpaas-cf@1.9.0 → mcpaas-cf@1.11.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 5 Nov 2026 · Probed https://mcpaas.live/rust/mcp/v1
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcpaas.live | CN=WE1,O=Google Trust Services,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 8d37294707672d33135102509b0ab759 |
| SANs: mcpaas.live | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcpaas.live. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| live. | present | 4724, 36322 | 8, 8 | Verified |
| mcpaas.live. | 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://mcpaas.live/rust/mcp/v1 | Verified | 200 | |
| http (plaintext) | http://mcpaas.live/rust/mcp/v1 | HTTPS enforced | 301 | https://mcpaas.live/rust/mcp/v1 |
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 →
faf_read ~42
Parse a .faf and return its normalized structure (Rust→WASM, at the edge).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Raw .faf file content (YAML) |
No output schema declared.
No examples provided.
faf_score ~56
Score a .faf 0-100 with the always-33 faf-kernel, the same score faf-cli gives (Rust→WASM, at the edge).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Raw .faf file content (YAML) |
No output schema declared.
No examples provided.
faf_validate ~51
Validate a .faf: structure errors/warnings plus the always-33 score faf-cli gives (Rust→WASM, at the edge).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Raw .faf file content (YAML) |
No output schema declared.
No examples provided.
How do I install the io.github.Wolfe-Jam/rust-faf-mcp server?
io.github.Wolfe-Jam/rust-faf-mcp is a hosted endpoint at https://mcpaas.live/rust/mcp/v1, 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 · mcpaas.live
claude mcp add --transport http wolfe-jam-rust-faf-mcp 'https://mcpaas.live/rust/mcp/v1'
What is the io.github.Wolfe-Jam/rust-faf-mcp server?
io.github.Wolfe-Jam/rust-faf-mcp is listed in the public MCP registry as io.github.Wolfe-Jam/rust-faf-mcp. Persistent project context, Rust-native MCP server. IANA-registered .faf format. This page covers its hosted endpoint (https://mcpaas.live/rust/mcp/v1).
Is the io.github.Wolfe-Jam/rust-faf-mcp server safe to use?
io.github.Wolfe-Jam/rust-faf-mcp scores 79 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 io.github.Wolfe-Jam/rust-faf-mcp server expose?
io.github.Wolfe-Jam/rust-faf-mcp exposes 3 tools: faf_validate, faf_score, faf_read. Their descriptions and schemas cost roughly 149 tokens of context every time the server is loaded.
Does the io.github.Wolfe-Jam/rust-faf-mcp server require authentication?
No. We connected to io.github.Wolfe-Jam/rust-faf-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.Wolfe-Jam/rust-faf-mcp server still maintained?
io.github.Wolfe-Jam/rust-faf-mcp is marked deprecated in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.