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

inventory-planner-mcp

https://inventory-planner.usefulapi.io

Registry code: 2a8b81fc417fda0f

api record

Tools for Inventory Planner, hosted by usefulapi.io. Read-only tools never change data; ask the user before a tool that creates, changes or deletes Inventory Planner data. Free plan: 100 tool calls per month. Run inventoryplanner_usage_status to see the calls used this month. If the user asks for something none of these tools can do, tell the user and, with their OK, run inventoryplanner_request_feature to record the request. Pro (unlimited calls, $9/month or $90/year): when the user wants more calls or reaches the limit, run inventoryplanner_upgrade; it returns a Stripe Checkout link for the…

endpoint
https://inventory-planner.usefulapi.io/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
0 · newcomer
_ is it live, free and safe measured by this hub
Is inventory-planner-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is inventory-planner-mcp free to use?
No — it asks for a key or a login before it will serve.
What tools does inventory-planner-mcp have?
11 tools: inventoryplanner_list_variant_vendors, inventoryplanner_list_purchase_orders, inventoryplanner_get_purchase_order, inventoryplanner_list_purchase_order_items, inventoryplanner_get_purchase_order_connections, inventoryplanner_get_purchase_order_stock_update, inventoryplanner_create_draft_purchase_order, inventoryplanner_update_draft_purchase_order, ….
Is inventory-planner-mcp 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
100%

90 days 100%· all time 100%

latency
406ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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.

  • inventoryplanner_list_variant_vendors auth-required never probed

    The vendors a variant can be ordered from, with cost_price, landing_cost_price, vendor_reference (vendor SKU), vendor_name, vendor_packaging (MOQ) and uom_ordering. GET /api/v1/variants/{id}/vendors.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "variant_id"
      ],
      "properties": {
        "variant_id": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Inventory Planner id."
        }
      }
    }
    arguments 15 lines
  • inventoryplanner_list_purchase_orders auth-required never probed

    List stock orders: purchase orders, transfers and assembly orders (the `type` field is "po"/empty, "transfer" or "assembly"). Filter with `filters`, e.g. {"status": "OPEN", "vendor": "Acme", "expected_date_lt": "2026-11-01"}. Default fields: id,reference,status,type,vendor,warehouse,source,created_date,expected_date,received_date,currency,total,total_ordered,total_received. GET /api/v1/purchase-orders.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "page": {
          "type": "integer",
          "maximum": 1000000,
          "minimum": 0,
          "description": "Page number, counting from 0 (default 0). Pass the previous reply's next_page."
        },
        "sort": {
          "type": "object",
          "required": [
            "field"
          ],
          "properties": {
            "field": {
              "type": "string",
              "pattern": "^[A-Za-z0-9_]{1,80}$"
            },
            "direction": {
              "enum": [
                "asc",
                "desc"
              ],
              "type": "string",
              "default": "asc"
            }
          },
          "description": "Sort by one field, e.g. {\"field\": \"under_value\", \"direction\": \"desc\"}."
        },
        "limit": {
          "type": "integer",
          "maximum": 1000,
          "description": "Results per page, 1-1000 (default 25).",
          "exclusiveMinimum": 0
        },
        "fields": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_.,-]+$",
          "maxLength": 2000
        },
        "filters": {
          "type": "object",
          "description": "Filters, as {\"<field>\": value} or {\"<field>_<operator>\": value}. Operators: eq (default), eqi (case-insensitive), ne, gt, gte, lt, lte, range (\"5-10\"), match (regex), in (comma-separated). Example: {\"replenishment_gt\": 0, \"sku_match\": \"^TSHIRT\"}.",
          "propertyNames": {
            "type": "string",
            "pattern": "^[A-Za-z0-9_]{1,80}$"
          },
          "additionalProperties": {
            "anyOf": [
              {
                "type": "string",
                "maxLength": 500
              },
              {
                "type": "number"
              },
              {
                "type": "boolean"
              }
            ]
          }
        }
      }
    }
    arguments 66 lines
  • inventoryplanner_get_purchase_order auth-required never probed

    One purchase order, transfer or assembly order by id, with its header fields (reference, status, vendor, warehouse, dates, addresses, totals, notes) and line items. GET /api/v1/purchase-orders/{id}.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "purchase_order_id"
      ],
      "properties": {
        "fields": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_.,-]+$",
          "maxLength": 2000
        },
        "purchase_order_id": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Inventory Planner id."
        }
      }
    }
    arguments 20 lines
  • inventoryplanner_list_purchase_order_items auth-required never probed

    The line items of a purchase order: variant id, sku, title, ordered quantity (replenishment), received quantity and received_history, cost price, tax, discount and stock snapshots. GET /api/v1/purchase-orders/{id}/items.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "purchase_order_id"
      ],
      "properties": {
        "page": {
          "type": "integer",
          "maximum": 1000000,
          "minimum": 0,
          "description": "Page number, counting from 0 (default 0). Pass the previous reply's next_page."
        },
        "limit": {
          "type": "integer",
          "maximum": 1000,
          "description": "Results per page, 1-1000 (default 25).",
          "exclusiveMinimum": 0
        },
        "fields": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_.,-]+$",
          "maxLength": 2000
        },
        "purchase_order_id": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Inventory Planner id."
        }
      }
    }
    arguments 32 lines
  • inventoryplanner_get_purchase_order_connections auth-required never probed

    Whether and how a purchase order was saved to connected systems (ERP, accounting): per connection the status (success, error, run, queued), save_po flag and the PO's id and reference there. Read-only. GET /api/v1/purchase-orders/{id}/connections.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "purchase_order_id"
      ],
      "properties": {
        "purchase_order_id": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Inventory Planner id."
        }
      }
    }
    arguments 15 lines
  • inventoryplanner_get_purchase_order_stock_update auth-required never probed

    The stock updates a purchase order has computed: per warehouse (wh) the items with stock_before, delta and error. for_destination false reads the source warehouse of a transfer. Read-only: nothing is pushed. GET /api/v1/purchase-orders/{id}/stock-update.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "purchase_order_id"
      ],
      "properties": {
        "for_destination": {
          "type": "boolean",
          "description": "true (default) = the destination warehouse; false = the source warehouse (transfers only)."
        },
        "purchase_order_id": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Inventory Planner id."
        }
      }
    }
    arguments 19 lines
  • inventoryplanner_create_draft_purchase_order auth-required never probed

    WRITE: create a purchase order with status "draft" in Inventory Planner (POST /api/v1/purchase-orders). A draft is only a plan inside Inventory Planner: it is NOT sent to the vendor, NOT saved to any connected system and moves no stock or money. Purchase orders only (no transfers or assembly orders). Each line item is a variant id plus the quantity to order (replenishment).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "vendor",
        "warehouse",
        "items"
      ],
      "properties": {
        "items": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "id",
              "quantity"
            ],
            "properties": {
              "id": {
                "type": "string",
                "maxLength": 200,
                "minLength": 1,
                "description": "Variant id."
              },
              "quantity": {
                "type": "number",
                "maximum": 10000000,
                "description": "Quantity to order.",
                "exclusiveMinimum": 0
              }
            }
          },
          "maxItems": 500,
          "minItems": 1
        },
        "notes": {
          "type": "string",
          "maxLength": 2000
        },
        "vendor": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "The vendor name, as it appears in Inventory Planner."
        },
        "currency": {
          "type": "string",
          "pattern": "^[A-Za-z]{3}$"
        },
        "reference": {
          "type": "string",
          "maxLength": 200,
          "description": "Your PO reference."
        },
        "warehouse": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "The destination warehouse, as it appears in Inventory Planner."
        },
        "expected_date": {
          "type": "string",
          "maxLength": 40,
          "description": "Expected delivery date, e.g. 2026-11-15 or 2026-11-15T10:00:00+01:00."
        }
      }
    }
    arguments 67 lines
  • inventoryplanner_update_draft_purchase_order auth-required never probed

    WRITE: change the reference, expected date or notes of a purchase order that is still a draft (PATCH /api/v1/purchase-orders/{id}). The order is read first and refused unless its status is "draft". It never changes the status, sends the order, or touches line items or received quantities.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "purchase_order_id"
      ],
      "properties": {
        "notes": {
          "type": "string",
          "maxLength": 2000
        },
        "reference": {
          "type": "string",
          "maxLength": 200
        },
        "expected_date": {
          "type": "string",
          "maxLength": 40,
          "description": "Expected delivery date, e.g. 2026-11-15 or 2026-11-15T10:00:00+01:00."
        },
        "purchase_order_id": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Inventory Planner id."
        }
      }
    }
    arguments 28 lines
  • inventoryplanner_list_variants auth-required 1h ago

    List product variants with Inventory Planner's computed metrics (forecast, replenishment, days to sell out, lost revenue, lead time, review period and ~200 more). Always pass `fields` to pick the metrics you need (default: id,sku,lead_time,review_period,replenishment,oos,under_value; oos = forecasted days to sell out, under_value = forecasted lost revenue, replenishment = recommended order quantity). Use `filters` and `sort` for questions like "which SKUs need reordering". Removed variants are excluded unless include_removed. GET /api/v1/variants.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "page": {
          "type": "integer",
          "maximum": 1000000,
          "minimum": 0,
          "description": "Page number, counting from 0 (default 0). Pass the previous reply's next_page."
        },
        "sort": {
          "type": "object",
          "required": [
            "field"
          ],
          "properties": {
            "field": {
              "type": "string",
              "pattern": "^[A-Za-z0-9_]{1,80}$"
            },
            "direction": {
              "enum": [
                "asc",
                "desc"
              ],
              "type": "string",
              "default": "asc"
            }
          },
          "description": "Sort by one field, e.g. {\"field\": \"under_value\", \"direction\": \"desc\"}."
        },
        "limit": {
          "type": "integer",
          "maximum": 1000,
          "description": "Results per page, 1-1000 (default 25).",
          "exclusiveMinimum": 0
        },
        "fields": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_.,-]+$",
          "maxLength": 2000
        },
        "filters": {
          "type": "object",
          "description": "Filters, as {\"<field>\": value} or {\"<field>_<operator>\": value}. Operators: eq (default), eqi (case-insensitive), ne, gt, gte, lt, lte, range (\"5-10\"), match (regex), in (comma-separated). Example: {\"replenishment_gt\": 0, \"sku_match\": \"^TSHIRT\"}.",
          "propertyNames": {
            "type": "string",
            "pattern": "^[A-Za-z0-9_]{1,80}$"
          },
          "additionalProperties": {
            "anyOf": [
              {
                "type": "string",
                "maxLength": 500
              },
              {
                "type": "number"
              },
              {
                "type": "boolean"
              }
            ]
          }
        },
        "include_removed": {
          "type": "boolean"
        }
      }
    }
    arguments 69 lines
  • inventoryplanner_get_variant auth-required 1h ago

    One variant by its Inventory Planner id, with the metrics named in `fields` (default: id,sku,lead_time,review_period,replenishment,oos,under_value). GET /api/v1/variants/{id}.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "variant_id"
      ],
      "properties": {
        "fields": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_.,-]+$",
          "maxLength": 2000
        },
        "variant_id": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Inventory Planner id."
        }
      }
    }
    arguments 20 lines
  • inventoryplanner_get_variant_vendor auth-required 1h ago

    One vendor's terms for a variant: cost_price, landing_cost_price, vendor_reference, vendor_name, vendor_packaging (MOQ), uom_ordering. vendor_id is the vendor name in lowercase. GET /api/v1/variants/{id}/vendors/{vendor_id}.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "variant_id",
        "vendor_id"
      ],
      "properties": {
        "vendor_id": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "The vendor name in lowercase, as listed by inventoryplanner_list_variant_vendors."
        },
        "variant_id": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Inventory Planner id."
        }
      }
    }
    arguments 22 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 2a8b81fc417fda0f.

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

123 more sit on this domain. All of them.