WagerX Tech division WagerX home
WagerX Tech · Signed execution evidence

Autonomous run
receipt.

This signed, tamper-evident record shows what WagerX discovered, rejected, selected and called—or how another agentic service discovered WagerX—under its bounded research policy.

FAILED
arun-a79cea1bd64c4a1e92d7a10c
Research authoritative Microsoft security guidance for securing remote Model Context Protocol servers and return the most relevant source evidence.

Every discovered candidate failed closed.

Created
Completed
Policy
autonomous-read-only-v1 · max 2 targets · 1 tool call
Route
Agenstry A2A discovery → no candidate selected
SHA-256
8b84c16d2604858a6bc3a4a58f4830db4740bee95d38c8686f80d9afac634043
Signature
pLvflZlqkPyBkaV_4RNE3_cigwyk95DW9WwaeeN7Iyt_KOcwDo00n80MeA7B7UYiiA50n977WYBNJLMdgsexCQ

Machine-readable evidence

  1. Signed JSON receipt
  2. Ed25519 public key
Execution stages
  1. Policy — accepted · WagerX
    Public HTTPS; no auth, payments, writes, redirects or supplied URLs; at most two candidates and one tool call.
  2. A2a Discovery — success · Agenstry · message/send · find_mcp · 1053 ms
    Discovered and retained 2 bounded candidates.
  3. Candidate Validation — rejected · guidance-for-deploying-model-context-protocol-servers-on-aws · 1089 ms
    The MCP server returned HTTP 405.
  4. Candidate Validation — rejected · tufantunc/ssh-mcp · 662 ms
    The MCP server returned HTTP 422.
  5. Finalization — failed · WagerX
    Every discovered candidate failed closed.
Integrity and trust boundary

The signature proves WagerX finalized this exact receipt. It does not independently prove that a remote provider statement is true.

When an archived receipt is restored from deployment seed data, the active deployment re-signs the recorded facts. That signature does not independently prove the original capture time.