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

goods-receipt

https://mcp.zovo.one

Registry code: da7a4ded5a255488

api record

Goods receipt against purchase orders. It covers purchase orders with SKU lines, ordered quantities and over and under tolerances, goods-receipt notes for full or partial deliveries with damaged and short units, discrepancies, closed receipt notes, and the status of every order against its receipts. Records are stored per user account on McpStamp's hosted service. Receiving is on the free tier; CSV export needs Pro. One lifetime key unlocks this server and all 58 others: https://mcp.zovo.one/buy/bundle?src=instr.goods-receipt

endpoint
https://mcp.zovo.one/mcp/goods-receipt
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
0 · newcomer
_ is it live, free and safe measured by this hub
Is goods-receipt live?
Yes — it answered the hub's last check (checked 6h ago). It answered 100% of checks over the last 30 days.
Is goods-receipt free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does goods-receipt have?
11 tools: grn_get, po_add, license_activate, grn_discrepancy, grn_list, license_status, grn_export_csv, grn_add, ….
Is goods-receipt 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
99.6%

90 days 99.7%· all time 99.7%

latency
823ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 388 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
topic
productivity & business procurement & sourcing
used for
  • create a purchase order
  • record goods received against a po
  • list delivery discrepancies
  • reconcile purchase orders
  • export goods receipts as csv
takes → gives
data → data, documents
tools
6 reads5 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 11 tools
11 auth-required 11 of 11 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.

  • grn_get reads auth-required 25h ago

    Get a single goods-receipt note by id, with its lines, damage and shortage per line.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "grn"
  ],
  "properties": {
    "grn": {
      "type": "string",
      "maxLength": 40,
      "description": "GRN id, e.g. GRN-0001"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • po_add changes data auth-required never probed

    Create a purchase order to receive goods against. Lines carry a sku, a description and an ordered whole-unit quantity. Over/under tolerances are whole percentages allowed above/below ordered before a GRN is flagged. Ids look like PO-0001. Free tier, full CRUD.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "reference",
    "supplier",
    "lines"
  ],
  "properties": {
    "lines": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "sku",
          "description",
          "ordered"
        ],
        "properties": {
          "sku": {
            "type": "string",
            "maxLength": 40,
            "description": "Stock-keeping unit / model code"
          },
          "ordered": {
            "type": "integer",
            "maximum": 1000000,
            "minimum": 1,
            "description": "Whole units ordered"
          },
          "description": {
            "type": "string",
            "maxLength": 160,
            "description": "What it is"
          }
        },
        "additionalProperties": false
      },
      "maxItems": 200,
      "minItems": 1,
      "description": "Lines on this purchase order"
    },
    "supplier": {
      "type": "string",
      "maxLength": 60,
      "description": "Who you ordered from"
    },
    "reference": {
      "type": "string",
      "maxLength": 60,
      "description": "Your own purchase-order number"
    },
    "overTolerancePct": {
      "type": "integer",
      "default": 10,
      "maximum": 100,
      "minimum": 0,
      "description": "Whole % extra allowed above ordered (default 10)"
    },
    "underTolerancePct": {
      "type": "integer",
      "default": 10,
      "maximum": 100,
      "minimum": 0,
      "description": "Whole % short allowed below ordered (default 10)"
    }
  },
  "additionalProperties": false
}
    arguments 69 lines
  • license_activate changes data auth-required never probed

    Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "key"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "License key from checkout, MCPL1.<payload>.<signature>"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • grn_discrepancy reads auth-required never probed

    List lines that are not as ordered: damaged units, a declared shortage, or received below the PO line's under tolerance. Optionally filter to one PO.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "po": {
      "type": "string",
      "maxLength": 40,
      "description": "Only discrepancies on this purchase order"
    },
    "includeResolved": {
      "type": "boolean",
      "default": false,
      "description": "Include GRNs that are closed (resolved)"
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • grn_list reads auth-required 25h ago

    List goods-receipt notes, newest first, optionally filtered to one purchase order.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "po": {
      "type": "string",
      "maxLength": 40,
      "description": "Only GRNs against this purchase order"
    },
    "includeLines": {
      "type": "boolean",
      "default": false,
      "description": "Include line detail"
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • license_status reads auth-required 25h ago

    Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • grn_export_csv reads auth-required never probed

    Pro. Export every GRN (or just one PO's GRNs) as CSV with a header row: grn,po,po_reference,received_at,carrier,status,line,sku,received,damaged,shortage,damage_note,shortage_note. Watermark-free and not truncated.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "po": {
      "type": "string",
      "maxLength": 40,
      "description": "Export GRNs for one purchase order only"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • grn_add changes data auth-required never probed

    Create a goods-receipt note (GRN) against an open purchase order. Give one cell per PO line: the whole units received and/or damaged. received is checked against the line's ordered quantity and the PO's over tolerance; receiving past the over tolerance is refused unless declared damaged. Shortage is recorded automatically (ordered minus received, floored at zero) and shown as a discrepancy. Partial deliveries are fine: raise several GRNs against the same PO. Free tier, full CRUD.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "po",
    "lines"
  ],
  "properties": {
    "po": {
      "type": "string",
      "maxLength": 40,
      "description": "Purchase-order id or reference, e.g. PO-0001"
    },
    "note": {
      "type": "string",
      "maxLength": 400,
      "description": "Memo for the whole GRN"
    },
    "lines": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "line",
          "received"
        ],
        "properties": {
          "line": {
            "type": "string",
            "maxLength": 40,
            "description": "PO line to receive, e.g. L01"
          },
          "damaged": {
            "type": "integer",
            "maximum": 1000000,
            "minimum": 0,
            "description": "Whole units received but damaged"
          },
          "received": {
            "type": "integer",
            "maximum": 1000000,
            "minimum": 0,
            "description": "Whole units of good stock"
          },
          "shortage": {
            "type": "integer",
            "maximum": 1000000,
            "minimum": 0,
            "description": "Whole units short; when you know the count"
          },
          "damageNote": {
            "type": "string",
            "maxLength": 400,
            "description": "What was damaged"
          },
          "shortageNote": {
            "type": "string",
            "maxLength": 400,
            "description": "Why it is short"
          }
        },
        "additionalProperties": false
      },
      "maxItems": 200,
      "minItems": 1,
      "description": "Which PO lines you are receiving now"
    },
    "carrier": {
      "type": "string",
      "maxLength": 60,
      "description": "Delivered by"
    },
    "receivedAt": {
      "type": "string",
      "maxLength": 10,
      "description": "ISO date of physical receipt (default today)"
    }
  },
  "additionalProperties": false
}
    arguments 80 lines
  • grn_line_add changes data auth-required never probed

    Add another PO line (or more units on a line already open on this GRN) to an existing open goods-receipt note. Useful when one delivery arrives in batches. The over-tolerance gate still applies to the PO line's cumulative received count across every GRN. Free tier, full CRUD.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "grn",
    "line",
    "received"
  ],
  "properties": {
    "grn": {
      "type": "string",
      "maxLength": 40,
      "description": "Open GRN id, e.g. GRN-0001"
    },
    "line": {
      "type": "string",
      "maxLength": 40,
      "description": "PO line to receive, e.g. L01"
    },
    "damaged": {
      "type": "integer",
      "maximum": 1000000,
      "minimum": 0,
      "description": "Whole units received but damaged"
    },
    "received": {
      "type": "integer",
      "maximum": 1000000,
      "minimum": 0,
      "description": "Whole units of good stock"
    },
    "damageNote": {
      "type": "string",
      "maxLength": 400,
      "description": "What was damaged"
    },
    "shortageNote": {
      "type": "string",
      "maxLength": 400,
      "description": "Why it is short"
    }
  },
  "additionalProperties": false
}
    arguments 44 lines
  • grn_close changes data auth-required never probed

    Close an open GRN. A closed GRN can no longer take lines, and its discrepancies are treated as resolved. Closing is free-tier and never mutates the PO.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "grn"
  ],
  "properties": {
    "grn": {
      "type": "string",
      "maxLength": 40,
      "description": "Open GRN id, e.g. GRN-0001"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • grn_status_report reads auth-required never probed

    Reconcile every purchase order against every GRN: open POs (not yet fully received), POs fully received within tolerance, POs with at least one discrepancy, and per-line open/short/damaged counts. Nothing is written.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "includeOnlyDiscrepancies": {
      "type": "boolean",
      "default": false,
      "description": "Only list POs with at least one discrepancy"
    }
  },
  "additionalProperties": false
}
    arguments 12 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 da7a4ded5a255488.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/da7a4ded5a255488/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/da7a4ded5a255488/badge.svg)](https://brick.blue/agent/da7a4ded5a255488?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
100%

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.

_ also on zovo.one 8 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.