_ registry / mcp streamable-http · checked 6m ago

laxis-operations-reconciliation

https://x402.burnesatelier.com

Registry code: 046238621c3f9c3f

api record

Use reconcile_operations for deterministic operational handoff reconciliation. Tool execution is $5.00 USDC via x402 on Base.

endpoint
https://x402.burnesatelier.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
10 · newcomer
_ is it live, free and safe measured by this hub
Is laxis-operations-reconciliation live?
Yes — it answered the hub's last check (checked 6m ago). It answered 97% of checks over the last 30 days.
Is laxis-operations-reconciliation free to use?
Not measured yet.
What tools does laxis-operations-reconciliation have?
1 tool: reconcile_operations.
Is laxis-operations-reconciliation safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
97%

90 days 85.4%· all time 85.4%

latency
424ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 137 checks · signed record
  • degraded → live
  • live → degraded· HTTP 530
  • degraded → live
  • live → degraded· HTTP 530
  • degraded → live
_ what it is for
used for
  • reconcile an operational handoff
  • check whether a handoff is complete
takes → gives
data → data
tools
1 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
4

distinct

settlements
5

last 2026-11-02

received on chain
0.025 USDC

no flags

_ what it can do 1 tools
1 never probed 0 of 1 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • reconcile_operations reads unknown never probed

    Deterministic operational handoff reconciliation. Returns COMPLETE, INCOMPLETE, or NEEDS_REVIEW with missing requirements, normalized packet, and hash-bound proof. Paid execution: $5.00 USDC via x402 on Base.

    mcp-tool

    {
      "type": "object",
      "required": [
        "subject",
        "completion_claim"
      ],
      "properties": {
        "subject": {
          "type": "object",
          "required": [
            "type",
            "label"
          ],
          "properties": {
            "type": {
              "enum": [
                "incident",
                "handoff",
                "workflow_run",
                "operational_task",
                "other"
              ],
              "type": "string"
            },
            "label": {
              "type": "string",
              "maxLength": 256
            }
          },
          "description": "What is being reconciled. Provide a supported subject type and a short human-readable label.",
          "additionalProperties": false
        },
        "evidence": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "id",
              "kind"
            ],
            "properties": {
              "id": {
                "type": "string",
                "maxLength": 128
              },
              "kind": {
                "enum": [
                  "receipt",
                  "log",
                  "hash",
                  "screenshot_reference",
                  "artifact_reference",
                  "measurement",
                  "other"
                ],
                "type": "string"
              },
              "sha256": {
                "type": "string",
                "pattern": "^[A-Fa-f0-9]{64}$"
              },
              "summary": {
                "type": "string",
                "maxLength": 4000
              }
            },
            "additionalProperties": false
          },
          "maxItems": 100,
          "description": "Evidence supporting the current state or completion claim; provide items matching the published evidence schema."
        },
        "next_owner": {
          "type": "object",
          "required": [
            "role_or_name",
            "next_action"
          ],
          "properties": {
            "due_at": {
              "type": "string",
              "maxLength": 64
            },
            "next_action": {
              "type": "string",
              "maxLength": 2000
            },
            "role_or_name": {
              "type": "string",
              "maxLength": 256
            }
          },
          "description": "Optional next responsible owner or system when additional work remains.",
          "additionalProperties": false
        },
        "request_id": {
          "type": "string",
          "maxLength": 128,
          "description": "Caller-chosen correlation identifier for this reconciliation request; maximum 128 characters."
        },
        "actions_taken": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "action"
            ],
            "properties": {
              "actor": {
                "type": "string",
                "maxLength": 256
              },
              "action": {
                "type": "string",
                "maxLength": 2000
              },
              "timestamp": {
                "type": "string",
                "maxLength": 64
              },
              "evidence_refs": {
                "type": "array",
                "items": {
                  "type": "string",
                  "maxLength": 128
                },
                "maxItems": 25
              }
            },
            "additionalProperties": false
          },
          "maxItems": 100,
          "description": "Actions already performed for this subject; include items matching the published action schema."
        },
        "current_state": {
          "type": "string",
          "maxLength": 12000,
          "description": "Describe the currently observed operational state used to evaluate the completion claim."
        },
        "completion_claim": {
          "type": "boolean",
          "description": "Set true only when the caller claims the subject is complete; otherwise false."
        }
      },
      "additionalProperties": false
    }
    arguments 145 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 046238621c3f9c3f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/046238621c3f9c3f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/046238621c3f9c3f/badge.svg)](https://brick.blue/agent/046238621c3f9c3f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
50%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.