Wayreceipt
Proof of delivery for agent work: verify countersigned receipts and deliverable hashes. Free.
¿Debería usar esto?
Calidad y seguridad
Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.
Costo de contexto
Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.
Instalar
Instalación con un clic
Agrega esto a tu archivo `claude_desktop_config.json`:
{
"mcpServers": {
"wayreceipt": {
"url": "https://wayreceipt.pages.dev/mcp"
}
}
}Puntos de conexión remotos
https://wayreceipt.pages.dev/mcpstreamable-httpQué puede hacer
Inventario de herramientas
Herramientas (4)
🟢verify_delivery_receipt(receipt, file_sha256)
Proof of delivery check. Verifies a delivery receipt: the seller's signature over the deliverable hash (SHA-256) and, if present, the buyer's countersignature. Returns countersigned, seller-only or invalid, with reasons. Optionally compares a file's SHA-256 with the deliverable hash. Relevant to a delivery dispute or to checking a seller before payment. Free, no sign-up, no API key.
Esquema de entrada
{
"type": "object",
"properties": {
"receipt": {
"type": "object",
"description": "A Wayreceipt delivery receipt (W3C Verifiable Credential 2.0 with eddsa-jcs-2022 proofs)."
},
"file_sha256": {
"type": "string",
"pattern": "^[0-9a-f]{64}$",
"description": "Optional SHA-256 (hex) of a local file to compare with the receipt."
}
},
"required": [
"receipt"
],
"additionalProperties": false
}Esquema de salida
{
"type": "object",
"properties": {
"valid": {
"type": "boolean"
},
"state": {
"type": "string",
"enum": [
"countersigned",
"seller-only",
"invalid"
]
},
"reasons": {
"type": "array",
"items": {
"type": "string"
}
}
},
"required": [
"valid",
"state",
"reasons"
]
}🟢lookup_delivery_receipt(receipt_id, file_sha256, seller)
Finds countersigned receipts in the public log by receipt ID, deliverable hash (file SHA-256) or seller key. Shows a seller's published proof of delivery history. The log only holds receipts that a seller or buyer chose to publish, and a key is not a verified identity.
Esquema de entrada
{
"type": "object",
"properties": {
"receipt_id": {
"type": "string",
"description": "Receipt id (urn:uuid:...) or log sequence number."
},
"file_sha256": {
"type": "string",
"pattern": "^[0-9a-f]{64}$",
"description": "SHA-256 (hex) of the delivered file."
},
"seller": {
"type": "string",
"description": "Seller DID (did:key:... or did:web:...)."
}
},
"additionalProperties": false
}🟢log_stats
Counts from the public log of countersigned receipts: receipts, distinct seller keys, distinct buyer keys and distinct seller-buyer pairs. Receipts the Wayreceipt team made for testing and removed entries are not counted.
Esquema de entrada
{
"type": "object",
"properties": {},
"additionalProperties": false
}🟡publish_delivery_receipt(receipt, seller_link, buyer_link)
Publishes a countersigned receipt (already signed by both seller and buyer) to the public log, as lasting proof of delivery for a deliverable hash. Signing happens on your side with the free library; this server never holds keys. The server re-verifies the receipt and rejects seller-only or invalid ones. Optional seller_link and buyer_link pages are checked for proof that they belong to the signing key (match, mismatch or unreachable). Published receipts are public.
Esquema de entrada
{
"type": "object",
"properties": {
"receipt": {
"type": "object",
"description": "A Wayreceipt delivery receipt (W3C Verifiable Credential 2.0 with eddsa-jcs-2022 proofs)."
},
"seller_link": {
"type": "string",
"format": "uri"
},
"buyer_link": {
"type": "string",
"format": "uri"
}
},
"required": [
"receipt"
],
"additionalProperties": false
}Comunidad
Evidencia