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

storeinvent-mcp

https://www.storeinvent.cz

Registry code: 8034d60a74dfd151

api record

Store Invent & Partners - Czech inventory services provider (stocktaking for retail). Use get_company_info / list_services / get_service_details / get_faq to learn about the company. Before calling submit_inquiry, call get_quote_requirements and collect as many of the listed details from your user as possible - a complete inquiry gets a faster and more accurate quote. submit_inquiry sends a real non-binding inquiry to the sales team; use the customer's real e-mail address. For free-form questions use ask_question (answers come from the company knowledge base, Czech or English).

endpoint
https://www.storeinvent.cz/api/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 storeinvent-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is storeinvent-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does storeinvent-mcp have?
7 tools: submit_inquiry, ask_question, get_service_details, list_services, get_faq, get_company_info, get_quote_requirements.
Is storeinvent-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 99.7%· all time 99.7%

latency
829ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 295 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • learn about retail stocktaking services
  • get quote requirements
  • ask a question about inventory services
  • submit a quote inquiry
takes → gives
text, data → text, data
tools
6 reads1 sends messages
_ 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 7 tools
4 open 3 never probed 4 of 7 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.

  • list_services reads open 9h ago

    List of all 6 inventory services with short descriptions and detail page URLs.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_faq reads open 9h ago

    Frequently asked questions and answers about the services.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_company_info reads open 23h ago

    Basic facts about STORE INVENT & PARTNERS, s.r.o.: history, scale, coverage, technology, contacts.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_quote_requirements reads open 23h ago

    What information the sales team needs to prepare a quote (pricing is always individual), plus data-format details and inventory preparation advice. Call this before submit_inquiry.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • submit_inquiry sends messages unknown never probed

    Submit a real non-binding inquiry (nezávazná poptávka) to the sales team. They reply to the given e-mail after reviewing the inquiry. Collect the details from get_quote_requirements first and include them in the message.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name",
        "company",
        "email",
        "services",
        "message"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Contact person full name"
        },
        "email": {
          "type": "string",
          "description": "Customer e-mail address (sales replies there)"
        },
        "phone": {
          "type": "string",
          "description": "Phone number (optional)"
        },
        "locale": {
          "enum": [
            "cs",
            "en"
          ],
          "type": "string",
          "description": "Language of the confirmation e-mail (default cs)"
        },
        "stores": {
          "type": "string",
          "description": "Number of stores/sites, digits only (optional)"
        },
        "company": {
          "type": "string",
          "description": "Company name"
        },
        "message": {
          "type": "string",
          "description": "Inquiry details - locations, floor size, SKU/piece counts, back-room share, barcode coverage, time window, required outputs"
        },
        "services": {
          "type": "string",
          "description": "Requested service(s), comma separated. Valid values: Inventura zboží, Inventura majetku, Audit inventur, Remodeling prodejen, Asistovaná inventura, Audit cenovek"
        },
        "timeline": {
          "type": "string",
          "description": "Preferred date (optional)"
        }
      },
      "additionalProperties": false
    }
    arguments 53 lines
  • ask_question reads unknown never probed

    Ask a free-form question about the company or its inventory services; answered from the company knowledge base (Czech or English).

    mcp-tool

    {
      "type": "object",
      "required": [
        "question"
      ],
      "properties": {
        "locale": {
          "enum": [
            "cs",
            "en"
          ],
          "type": "string",
          "description": "Preferred answer language (default cs)"
        },
        "question": {
          "type": "string",
          "description": "The question (max 2000 characters)"
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • get_service_details reads unknown 23h ago

    Details of one service: what it includes, how it works, practical notes.

    mcp-tool

    {
      "type": "object",
      "required": [
        "service"
      ],
      "properties": {
        "service": {
          "enum": [
            "Inventura zboží",
            "Inventura majetku",
            "Audit inventur",
            "Remodeling prodejen",
            "Asistovaná inventura",
            "Audit cenovek",
            "Stock inventory",
            "Asset inventory",
            "Inventory audit",
            "Store remodeling",
            "Assisted inventory",
            "Price tag audit"
          ],
          "type": "string",
          "description": "Service name (Czech or English)"
        }
      },
      "additionalProperties": false
    }
    arguments 27 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 8034d60a74dfd151.

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