| Filename | Latest commit message | Latest commit date |
|---|---|---|
7ddcd63002Bumps the cargo group with 3 updates in the /mcp-client-rust directory: [openssl](https://github.com/rust-openssl/rust-openssl), [quinn-proto](https://github.com/quinn-rs/quinn) and [serde_with](https://github.com/jonasbb/serde_with). Bumps the cargo group with 1 update in the /weather-server-rust directory: [openssl](https://github.com/rust-openssl/rust-openssl). Updates `openssl` from 0.10.79 to 0.10.81 - [Release notes](https://github.com/rust-openssl/rust-openssl/releases) - [Commits](https://github.com/rust-openssl/rust-openssl/compare/openssl-v0.10.79...openssl-v0.10.81) Updates `quinn-proto` from 0.11.14 to 0.11.17 - [Release notes](https://github.com/quinn-rs/quinn/releases) - [Commits](https://github.com/quinn-rs/quinn/compare/quinn-proto-0.11.14...quinn-proto-0.11.17) Updates `serde_with` from 3.15.0 to 3.22.0 - [Release notes](https://github.com/jonasbb/serde_with/releases) - [Commits](https://github.com/jonasbb/serde_with/compare/v3.15.0...v3.22.0) Updates `openssl` from 0.10.79 to 0.10.81 - [Release notes](https://github.com/rust-openssl/rust-openssl/releases) - [Commits](https://github.com/rust-openssl/rust-openssl/compare/openssl-v0.10.79...openssl-v0.10.81) --- updated-dependencies: - dependency-name: openssl dependency-version: 0.10.81 dependency-type: indirect dependency-group: cargo - dependency-name: quinn-proto dependency-version: 0.11.17 dependency-type: indirect dependency-group: cargo - dependency-name: serde_with dependency-version: 3.22.0 dependency-type: indirect dependency-group: cargo - dependency-name: openssl dependency-version: 0.10.81 dependency-type: indirect dependency-group: cargo ... Signed-off-by: dependabot[bot] <support@github.com> |
||
| .. | ||
| src | ||
| Cargo.lock | ||
| Cargo.toml | ||
| README.md | ||
An LLM-Powered Chatbot MCP Client written in Rust
See the Build an MCP client tutorial for more information.
Structured content
rmcp does not validate tool output, so this client compiles each declared outputSchema at connect time and checks results against it — the spec's client-side SHOULD. It uses the jsonschema crate, which rmcp's own documentation recommends.
The two channels go to different readers: content is forwarded to the model, while structured_content is used as data — the client counts the items it returns. See Structured Content.