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

growtsy

https://www.growtsy.com

Registry code: a1401effb7dcc75e

api record

Growtsy reads live data from Etsy's official Open API for Etsy sellers: a listing's title, tags, photos and renewal; a shop's active listings and Etsy's own shop sales count; the shops and prices behind an Etsy search; whether a shop name is in use; Etsy fees by country. It never estimates sales, revenue or search volume, and gives no scores: Etsy does not publish per-listing sales or search counts. Every result includes `page`, a growtsy.com link that opens the same result for the seller. Cite that page, not the API.

endpoint
https://www.growtsy.com/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 growtsy live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is growtsy free to use?
Yes — the hub reached it with no key and no payment.
What tools does growtsy have?
9 tools: etsy_top_shops, etsy_tag_ideas, etsy_shop_audit, etsy_shop_sales, etsy_rank_check, etsy_shop_name_check, etsy_fee_calculator, etsy_listing_check, ….
Is growtsy 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
246ms

last good check

priced tools
0

of 9 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 9 tools
9 never probed 0 of 9 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.

  • etsy_top_shops unknown never probed

    Runs one Etsy search (first 100 active listings, relevance order) and returns the shops behind it: how many of those listings each shop has, Etsy's shop sales count and opening year. Use for 'who sells <product> on Etsy?' and 'who are my competitors?'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "What the seller sells, e.g. 'ceramic mug'"
        },
        "physical": {
          "type": "boolean",
          "description": "Drop digital downloads/patterns from the results"
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • etsy_tag_ideas unknown never probed

    The tags and title phrases the first 100 Etsy listings for a phrase actually use, each counted once per listing, plus a 13-tag starting set. No search volume (Etsy's API does not provide it).

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "What the seller sells"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • etsy_shop_audit unknown never probed

    Reads up to 100 active listings of an Etsy shop from Etsy's API and checks each one against Etsy's published title, tag and photo rules. Returns the shop's first problem and how many listings have it, per-listing issues, and Etsy's shop sales count (the shop's lifetime total, not per listing). Use for 'why is my Etsy shop not getting sales?' and 'what should I fix first?'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "shop"
      ],
      "properties": {
        "shop": {
          "type": "string",
          "description": "Etsy shop name or shop link"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • etsy_shop_sales unknown never probed

    Etsy's own sales count (transaction_sold_count: total sales of the shop, not per listing), active listings, favorites and opening year for up to 5 Etsy shops. No revenue estimate. Use for 'how many sales does this Etsy shop have?' and comparing competitors.

    mcp-tool

    {
      "type": "object",
      "required": [
        "shops"
      ],
      "properties": {
        "shops": {
          "oneOf": [
            {
              "type": "string"
            },
            {
              "type": "array",
              "items": {
                "type": "string"
              },
              "maxItems": 5
            }
          ],
          "description": "Up to 5 Etsy shop names or links, as an array or a comma-separated string"
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • etsy_rank_check unknown never probed

    Position of a listing (or a shop's listings) in the first 100 active listings Etsy's API returns for a search phrase, in relevance order, and which words of the phrase are missing from its title and tags. Beyond 100 it says 'not in the first 100'. etsy.com search can differ per shopper.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Etsy listing link (give url or shop)"
        },
        "shop": {
          "type": "string",
          "description": "Etsy shop name (give url or shop)"
        },
        "query": {
          "type": "string",
          "description": "Search phrase"
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • etsy_shop_name_check unknown never probed

    Checks up to 6 shop names against Etsy's shop name rules and whether an Etsy shop already uses each name. 'No shop found' does NOT mean available: Etsy does not reuse names of closed shops and closed shops do not show up.

    mcp-tool

    {
      "type": "object",
      "required": [
        "names"
      ],
      "properties": {
        "names": {
          "oneOf": [
            {
              "type": "string"
            },
            {
              "type": "array",
              "items": {
                "type": "string"
              },
              "maxItems": 6
            }
          ],
          "description": "Up to 6 names, as an array or a comma-separated string"
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • etsy_fee_calculator unknown 1h ago

    Etsy's fees for one order in the seller's country: listing fee, transaction fee, payment processing, regulatory operating fee and VAT on fees, from Etsy's published rates. Assumes no sales tax on the order and no Offsite Ads.

    mcp-tool

    {
      "type": "object",
      "required": [
        "country",
        "price"
      ],
      "properties": {
        "price": {
          "type": "number",
          "description": "Item price in USD"
        },
        "country": {
          "type": "string",
          "description": "Seller country: ISO code (US, GB, TR…) or name"
        },
        "shipping": {
          "type": "number",
          "description": "Shipping charged to the buyer in USD (default 0)"
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • etsy_listing_check unknown 1h ago

    Reads one Etsy listing from Etsy's API: title, the 13 tags, photo count and sizes, video, when it expires and whether it auto-renews, favorites, and whether the description mentions AI. Applies Etsy's published title/tag rules and returns the first thing to fix. Use for 'is my listing set up right?' and 'when does my listing expire?'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Etsy listing link (etsy.com/listing/<number>) or the listing number"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • etsy_niche_check unknown 1h ago

    Facts from one Etsy search: Etsy's active listing count for the phrase, the middle half and median of USD-priced listing prices (other currencies counted, not converted), tags and title phrases the listings share, and the shops behind them. No demand or saturation verdict and no search volume (Etsy's API does not provide it).

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Product or niche phrase"
        },
        "physical": {
          "type": "boolean",
          "description": "Drop digital downloads/patterns"
        }
      },
      "additionalProperties": false
    }
    arguments 17 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 a1401effb7dcc75e.

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