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

seerxo

https://api.seerxo.com

Registry code: ff58bc3b74e8e545

api record

Generate SEO-optimized Etsy listings — title, description, and 13 tags — from your AI assistant.

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

endpoint
https://api.seerxo.com/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 seerxo live?
Partly — its last checks failed now and then (checked 7h ago). It answered 98% of checks over the last 30 days.
Is seerxo 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 seerxo have?
5 tools: generate_etsy_seo, seerxo_analyze_listing, seerxo_optimize_listing, seerxo_suggest_keywords, seerxo_quota.
Is seerxo 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
degraded
uptime, 30 days
98.3%

90 days 99.1%· all time 99.1%

latency
305ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 327 checks · signed record
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • generate an seo etsy listing
  • analyze an etsy listing
  • suggest etsy keywords
  • optimize etsy titles and tags
takes → gives
text → text, data
tools
5 reads
_ 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 5 tools
1 auth-required 4 never probed 1 of 5 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.

  • seerxo_quota reads auth-required 2d ago

    Use this when the user asks about Seerxo credits or usage. Shows the authenticated account's remaining monthly generation quota. Free.

    mcp-tool

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

    Use this when the user wants a complete SEO-optimized Etsy listing from a product idea. Returns a title, A/B title variants, description, exactly 13 tags, and attributes. Uses one generation from the monthly quota.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "product_name"
      ],
      "properties": {
        "category": {
          "type": "string",
          "maxLength": 120,
          "description": "Etsy category, e.g. \"Home & Living\""
        },
        "product_name": {
          "type": "string",
          "maxLength": 300,
          "minLength": 2,
          "description": "Product description, e.g. \"handmade ceramic coffee mug, speckled glaze, 12oz\""
        }
      }
    }
    arguments 20 lines
  • seerxo_analyze_listing reads unknown 2d ago

    Use this when the user wants to assess an existing Etsy listing. Returns a versioned Listing Readiness score with official Etsy sources, limitations, weak points, missing keywords, and tag utilization. It does not predict search rank or sales. Free — does not use quota.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "tags": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 20,
          "description": "Current Etsy tags"
        },
        "title": {
          "type": "string",
          "maxLength": 500,
          "description": "Current Etsy listing title"
        },
        "description": {
          "type": "string",
          "maxLength": 20000,
          "description": "Current Etsy listing description"
        },
        "product_name": {
          "type": "string",
          "maxLength": 300,
          "minLength": 2,
          "description": "Short product description, e.g. \"handmade ceramic coffee mug, speckled glaze, 12oz\""
        }
      }
    }
    arguments 30 lines
  • seerxo_optimize_listing reads unknown never probed

    Use this when the user wants to rewrite an existing Etsy title, description, or tags based on audit findings. A re-audit gate prevents score regression. Uses one generation from the monthly quota.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "mode": {
          "enum": [
            "full",
            "title_only",
            "description_only",
            "tags_only"
          ],
          "type": "string",
          "description": "Which fields to rewrite (default: full)"
        },
        "tags": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 20,
          "description": "Current Etsy tags"
        },
        "title": {
          "type": "string",
          "maxLength": 500,
          "description": "Current Etsy listing title"
        },
        "description": {
          "type": "string",
          "maxLength": 20000,
          "description": "Current Etsy listing description"
        },
        "product_name": {
          "type": "string",
          "maxLength": 300,
          "minLength": 2,
          "description": "Short product description, e.g. \"handmade ceramic coffee mug, speckled glaze, 12oz\""
        }
      }
    }
    arguments 40 lines
  • seerxo_suggest_keywords reads unknown never probed

    Use this when the user wants Etsy keyword ideas for a product or listing. Returns ranked autosuggest phrases with relative demand and placement guidance; never fabricates search volumes. Uses one generation from the monthly quota.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "seed": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "Seed phrase to expand"
        },
        "tags": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 20,
          "description": "Current Etsy tags"
        },
        "title": {
          "type": "string",
          "maxLength": 500,
          "description": "Current Etsy listing title"
        },
        "description": {
          "type": "string",
          "maxLength": 20000,
          "description": "Current Etsy listing description"
        },
        "product_name": {
          "type": "string",
          "maxLength": 300,
          "minLength": 2,
          "description": "Short product description, e.g. \"handmade ceramic coffee mug, speckled glaze, 12oz\""
        }
      }
    }
    arguments 36 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 ff58bc3b74e8e545.

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

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.