Steward MCP

Overview Schema Source Related Servers Discussions Admin

trust_verify_status

Check whether a domain is Steward Verified: get verification status, method, issuance/expiry dates, and endpoint count before trusting a merchant domain.

Instructions

Check whether a domain is Steward Verified: returns verification status, method, issuance/expiry, and endpoint count. Read-only and advisory — it reports status; verification is never issued here and can never be purchased. Use before trusting a merchant domain; for agent counterparties use trust_agent_attestation; for a pay/no-pay decision use trust_screen. Paid: $0.01 USDC on Base per lookup — the rail quotes each call via 402; this server verifies the quote (exact scheme, Base network, USDC, Steward payee) and settles from your wallet automatically, refusing quotes over your per-call or daily spend caps. Your payer key never leaves your machine.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "trust_verify_status"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Domain to check, without scheme (e.g. pay.brianbooms.com). Lowercased automatically.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Oct 17, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does so: it declares read-only/advisory behavior, states that verification is never issued or purchasable here, and discloses the payment mechanics end-to-end ($0.01 USDC on Base, 402 quote, exact scheme/network/token/payee validation, per-call and daily spend caps, automatic wallet settlement, payer key never leaves the machine).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and routing before the lengthy payment paragraph. Every sentence is substantive, though the payment/settlement passage is dense enough that it could be tightened slightly without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description names the four returned fields, so return semantics are covered. Combined with the safety, cost and routing disclosure, nothing an agent needs to invoke this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and there is a single parameter, so the schema already documents format, length bounds and auto-lowercasing. The description references the domain concept but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Check whether a domain is Steward Verified') and enumerates the returned fields (status, method, issuance/expiry, endpoint count). It also explicitly distinguishes itself from two siblings by name, so an agent can route without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('before trusting a merchant domain') and names the correct alternatives with their selecting conditions: trust_agent_attestation for agent counterparties, trust_screen for pay/no-pay decisions. This is exactly the routing guidance an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.