Ardaro: a synthetic MCP invoice result for testing a human-review boundary in agent workflows

[ashevilleislove]

I'm Brent, founder of Ardaro. I built a read-only MCP invoice-checking service and am sharing a small synthetic fixture for Agent Framework builders working on review steps around external tool results.

Connect a Streamable HTTP MCP client to https://agents.getardaro.com/mcp, complete the normal initialization handshake, then make this tool call (it is not a complete client configuration):

{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"get_invoice_matching_example","arguments":{}}}

This fixed synthetic example is free and needs no wallet. In our direct MCP check on September 13, 2026, the server identified itself as ardaro-agent-services 1.3.0 and listed 18 tools. The fixture returned synthetic_only: true, response.status: "review_required", and:

{
  "outcome": "no_discrepancies",
  "human_review_required": true,
  "delivery_verified": false,
  "payment_approved": false
}

Those four fields are from response.result.summary; they are an excerpt, not the entire tool result. The example's invoice quantity is 2 against an order quantity of 5. Its policy explicitly says earlier invoices and deliveries are not checked. Matching supplied fields therefore does not establish delivery or authorize payment.

The workflow test I suggest is simple: a successful tool call should reach a review state when human_review_required is true, even if the supplied invoice and PO show no discrepancies. Display the matched quantities and the unverified-delivery flag at that review step. Do not let a summarizing agent turn no_discrepancies into a payment approval; payment_approved is explicitly false and the service does not support financial posting.

I have verified the direct MCP response, not a native Agent Framework run. I would welcome feedback on whether these fields are sufficient for an explicit review step without making the tool responsible for the host application's approval state.

The live services are read-only and advisory. The separate paid analyses use per-service x402 fees on Base and require owner-authorized payment. This example check made no paid calls. Ardaro does not perform image OCR or post to accounting.

Service documentation

Disclosure: I am affiliated with Ardaro. This post was prepared with AI assistance and checked against the live MCP response. Validation here is direct MCP, not an executed native Agent Framework integration.