_ registry / mcp http-sse · checked 12h ago

sandooq-product

https://sandooq.app

Registry code: 9e686d3f77bb5d97

api record

Sandooq product facts: plans, prices, MENA market tax and currency, and site pages as Markdown.

from a public catalogue that lists it, not from the operator

endpoint
https://sandooq.app/api/mcp/product
protocol
http-sse ·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 sandooq-product live?
Yes — it answered the hub's last check (checked 12h ago). It answered 100% of checks over the last 30 days.
Is sandooq-product free to use?
Yes — the hub reached it with no key and no payment.
What tools does sandooq-product have?
4 tools: get_pricing, search_docs, get_country_info, get_page.
Is sandooq-product 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
1,535ms

last good check

priced tools
0

of 4 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 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.

  • get_pricing unknown never probed

    Sandooq's subscription plans, prices and per-plan limits, read from the same source the pricing page renders.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "country": {
          "type": "string",
          "description": "Optional ISO 3166-1 alpha-2 country code, lowercase. One of: sa, qa, ae, bh, om, sy, lb. Pricing is identical in every country; the code is echoed back so the answer can name it."
        }
      }
    }
    arguments 10 lines
  • search_docs unknown 12h ago

    Search Sandooq's public pages and blog articles by keyword, returning ranked titles, URLs and excerpts. Follow a result with get_page to read it in full.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "How many results to return. Default 5, maximum 20. `matchCount` reports the total number of matching pages regardless."
        },
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "Words to search for. Matched case-insensitively against page titles and body text in the chosen language; there is no stemming, so the words a reader would use work best."
        },
        "locale": {
          "enum": [
            "en",
            "ar"
          ],
          "type": "string",
          "description": "Response language: 'en' (default) or 'ar'. Arabic returns the Arabic copy the site publishes, not a translation of the English."
        }
      }
    }
    arguments 28 lines
  • get_country_info unknown 12h ago

    What Sandooq publishes about one MENA market: VAT rate, e-invoicing posture, currency, how tenders are handled, the regulator, and the market notes shown on that country's page.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "country"
      ],
      "properties": {
        "locale": {
          "enum": [
            "en",
            "ar"
          ],
          "type": "string",
          "description": "Response language: 'en' (default) or 'ar'. Arabic returns the Arabic copy the site publishes, not a translation of the English."
        },
        "country": {
          "enum": [
            "sa",
            "qa",
            "ae",
            "bh",
            "om",
            "sy",
            "lb"
          ],
          "type": "string",
          "description": "Country to describe, as a lowercase ISO 3166-1 alpha-2 code. One of: sa, qa, ae, bh, om, sy, lb."
        }
      }
    }
    arguments 30 lines
  • get_page unknown 12h ago

    One Sandooq page as Markdown — the same representation the site serves at /agent and via Accept: text/markdown, with no HTML or navigation chrome.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "path"
      ],
      "properties": {
        "path": {
          "type": "string",
          "description": "Site-relative path, no leading slash and no language prefix — e.g. 'pricing', 'about', 'pos-system/saudi-arabia', 'blog/<slug>'. Use '' for the home page. Choose the language with `locale`, not with a '/ar' prefix."
        },
        "locale": {
          "enum": [
            "en",
            "ar"
          ],
          "type": "string",
          "description": "Response language: 'en' (default) or 'ar'. Arabic returns the Arabic copy the site publishes, not a translation of the English."
        }
      }
    }
    arguments 21 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 9e686d3f77bb5d97.

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

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.