glm-5.2
64696fec97
to_mcp is the MCP-direction gateway projection (ADR-041): exposes 4 fixed gateway tools (search, schema, call, batch) over rmcp StreamableHttpService nested into the axum Router at /mcp, not one MCP tool per registry operation. The LLM discovers operations on demand via search+schema. - ToMcpGateway implements rmcp ServerHandler (call_tool, list_tools, get_info) - tools/list returns the 4 fixed gateway tools, never the registry's ops - search dispatches services/list via GatewayDispatch::invoke, excludes Subscription ops (ADR-041 §2), returns names + descriptions - schema dispatches services/schema, returns the full OperationSpec - call dispatches via GatewayDispatch::invoke (shared spine), maps ResponseEnvelope -> CallToolResult::structured (Ok) / CallToolResult::structured_error (Err(CallError)) - batch loops over invoke, returns an array of results - Bearer auth via shared bearer_auth_middleware applied around nest_service (rmcp simple_auth_streamhttp pattern); Identity read from RequestContext.extensions -> http::request::Parts.extensions (research §6 #2 identity-survives-framing assumption, confirmed via test) - to_mcp is a pure projection (consumes registry, produces no entries) - Feature-gated behind mcp; stdio NOT built (ADR-037) - /mcp route wired in adapter.rs replacing the placeholder 501 cargo test -p alknet-http --features mcp: 172 passed cargo clippy -p alknet-http --features mcp --all-targets: clean cargo check -p alknet-http (no mcp): clean
Alknet
Status: Pre-alpha — This project is undergoing a major architectural pivot to an ALPN-as-service model. The previous implementation has been archived and a greenfield rebuild is in progress.
A self-hostable networking toolkit built on QUIC+TLS with ALPN-based protocol dispatch. Each protocol handler (SSH, SFTP, Git, HTTP, DNS, messaging, call protocol) registers an ALPN string on a shared endpoint. The ALPN negotiation during the TLS/QUIC handshake routes connections to the correct handler before any application bytes are read.
Core Insight
A service IS an ALPN. One endpoint, one port, many protocols — dispatched by the TLS handshake, not by application-level peeking or separate listeners.
Crates
| Crate | Status | Description |
|---|---|---|
alknet-vault |
stable | Local key vault: BIP39/SLIP-0010/AES-GCM key derivation and encryption |
alknet-core |
planned | ProtocolHandler trait, ALPN router, auth/identity, config |
alknet-ssh |
planned | SSH handler (russh), SOCKS5, port forwarding |
alknet-call |
planned | JSON-RPC call protocol (EventEnvelope framing) |
alknet-fs |
planned | Content-addressed file storage (iroh-blobs backend) |
alknet-sftp |
planned | SFTP handler (russh-sftp protocol core) |
alknet-git |
planned | Git smart protocol handler (gix) |
alknet-http |
planned | HTTP handler (axum, REST API, MCP) |
alknet-dns |
planned | DNS handler (hickory-proto, pkarr) |
alknet-msg |
planned | E2E encrypted messaging, mixnet support |
alknet |
planned | CLI binary (assembles and registers handlers) |
Documentation
- ALPN-as-service architecture — pivot proposal
- Cleanup plan — greenfield transition plan
- SDD process — spec-driven development process
- Research references — iroh, russh, russh-sftp deep dives
Reference implementation (previous architecture) is preserved at /workspace/@alkdev/alknet-main/.
License
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.