Business operationsPublic source

Warranty MCP Server

A warranty management platform for ADK-Rust Enterprise agents. 24 MCP tools covering products, warranty plans with coverage terms, registrations with computed coverage periods, entitlement/coverage checks, a claims…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Products & plans — a product catalog and warranty plans carrying coverage terms: duration, covered failure types, exclusions, per-claim deductible, total coverage cap, and transferability.

Registrations — bind a plan to a serial number + owner; the coverage window is computed from the plan duration and purchase date (month-accurate, day-clamped). Transfer respects the plan's…

Entitlement — check_entitlement reports in-window status, days remaining, whether a failure type is covered or excluded, the deductible, and remaining cap.

Claims lifecycle — submit → triage → approve/reject → in_repair → closed. validate_claim is a read-only adjudication pre-check; approve_claim re-runs coverage validation and refuses…

RMA / repair — issue an RMA only for an approved claim (repair/replace/refund); status flow issued → received → repaired → shipped → closed; closing the RMA closes the claim.

Analytics — claims by status, approval rate, total and average approved payout, optionally scoped to a product.

Architecture

How Warranty MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Warranty MCP Server

Validates the request and owns 24 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Warranty MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Warranty MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

24 named tools

create_product

Create a product in the catalog

internal write

get_product

Get a product by id

read only

list_products

List products by category

read only

create_plan

Create a warranty plan with coverage terms

internal write

get_plan

Get a warranty plan

read only

list_plans

List warranty plans

read only

register

internal write

get_registration

Get a registration by id or serial

read only

list_registrations

List registrations by owner/status

read only

transfer_registration

Transfer a registration to a new owner (if transferable)

internal write

check_entitlement

Check coverage/entitlement for a registration

read only

submit_claim

File a warranty claim

internal write

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

13 read only8 internal write3 external write

Three writes carry financial/contractual weight and are gated (requires_approval, external_write): approve_claim (commits a payout), reject_claim (a contractual denial), and issue_rma…
Coverage can't be bypassed — approval re-validates the coverage window, covered-failure list, exclusions, and cap; an expired registration or excluded failure is refused (verified in tests…
validate_claim is read-only so agents can pre-check adjudication without side effects. Everything material is on the audit trail (audit_log).
Sample data is fictitious.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-warranty

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-warranty",
    ["mcp-warranty"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Architecture ↗docs/architecture.svg Issues and support ↗github.com issues

Keep exploring