Anton Kochkov 4ee627c4dc Update rmcp to 3.8 to serve MCP 2026-07-28 clients ...

* A client of MCP 2026-07-28, such as FastMCP 4.1.4, begins with
  `server/discover` and falls back to `initialize` on an error. rmcp 1.8
  accepts nothing but `initialize` first: it logged "expect initialized
  request, but received: ... server/discover" and exited, so the client
  only saw the connection close.
* rmcp 3.8 answers `ping` and `server/discover` before `initialize`
  (with the supported revisions, 2024-11-05 to 2026-07-28), serves the
  requests of 2026-07-28 clients without `initialize`, and answers other
  early requests with an error instead of exiting. FastMCP 4.1.4 now
  connects and calls tools on both backends.
* Port to its API: `ContentBlock`, `Role`, `Resource`,
  `ResourceTemplate`, and `ReadResourceResponse` for `read_resource`.
  rmcp 3 needs Rust 1.88.
* tests/protocol.rs speaks raw JSON-RPC for both kinds of client; with
  rmcp 1.8 both tests fail on the closed connection.

2026-10-30 22:29:05 +08:00

..

contract.rs

Analyze GNU ls in the tests also on Ubuntu 26.04

2026-10-30 22:29:05 +08:00

integration.rs

Analyze GNU ls in the tests also on Ubuntu 26.04

2026-10-30 22:29:05 +08:00

protocol.rs

Update rmcp to 3.8 to serve MCP 2026-07-28 clients

2026-10-30 22:29:05 +08:00

tools.rs

Return Rizin's messages from every raw command

2026-10-30 22:29:05 +08:00

wedge.rs

Report a dead session as closed, with the reason

2026-10-30 18:35:59 +08:00