No user-submitted related servers found.
Scored across 2 tools
The two tools occupy strictly non-overlapping phases: one runs before payment (read-only conformance probing, never pays), the other runs after payment (links a signed receipt to an on-chain settlement). Descriptions explicitly state the temporal ordering and the distinct inputs/outputs, so misselection is essentially impossible.
Both names are snake_case and action-first (check_…, link_…), giving a readable, predictable pattern. The prefixes and noun styles differ ('x402_endpoint' vs 'receipt_to_settlement'), but this reflects genuinely different operations rather than sloppy convention.
Two tools is on the thin side, but the domain — verifying x402 offer-receipts before and after payment — is narrow and the pair maps cleanly onto its two lifecycle checkpoints. Nothing in the surface feels redundant or padded.
The before-pay and after-pay verification paths are both covered, with explicit tri-state answers (linked / not linked / could-not-check) avoiding dead ends. Minor gaps remain: no way to inspect or list previously verified receipts, and no batch or summary operation for multiple endpoints.