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

pollen-management

https://pollen.elytron.in

Registry code: a587d51dda4fc495

api record

Manage your Pollen account: sync, enrich, fix, and publish your store's catalog for AI agents.

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

endpoint
https://pollen.elytron.in/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 pollen-management live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is pollen-management 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 pollen-management have?
23 tools: apply_fixes, get_account_summary, sync_catalog, write_back_to_store, get_setup_instructions, connect_meta, enrich_product, get_network_insights, ….
Is pollen-management 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
99.4%

90 days 99%· all time 99%

latency
652ms

last good check

priced tools
0

of 23 tools

_ answered our checks, 90 days 308 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
productivity & business marketing & seo
used for
  • sync a store catalog
  • enrich product data for ai agents
  • apply seo fixes to a catalog
  • connect google or meta catalogs
takes → gives
text → data
tools
10 reads13 changes data
_ 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 23 tools
23 auth-required 23 of 23 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.

  • apply_fixes changes data auth-required never probed

    Run one of Pollen's automated catalog-wide fixes on the merchant's store: 'seo' (fill empty SEO titles + meta descriptions), 'tags' (add tags from enrichment facts to products with fewer than 3), 'altText' (fill empty image alt texts), or 'brand' (fill missing brand from enrichment or the store's own name - Shopify vendor / WC Brands). Fill-only-empty: values the merchant already set are NEVER touched. Queued on the worker - poll get_fix_opportunities fixStatuses for progress.

    mcp-tool

    {
  "type": "object",
  "required": [
    "fixType"
  ],
  "properties": {
    "fixType": {
      "enum": [
        "seo",
        "tags",
        "altText",
        "brand"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • get_account_summary reads auth-required 18h ago

    Get a high-level summary of the merchant's Pollen account: plan, agent-ready %, product counts, last sync/enrichment/writeback timestamps. Use this first if the user asks 'where do I stand?' or 'what's my status?'

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • sync_catalog changes data auth-required never probed

    Trigger a full product sync from the merchant's platform (Shopify, WC, BC) into Pollen. Use before enrichment if products are missing or out of date.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • write_back_to_store changes data auth-required never probed

    Push enriched data back to the merchant's platform as metafields/meta_data. Run after enrichment completes. Use when the user says 'publish' or 'push to my store'.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_setup_instructions reads auth-required never probed

    Get the merchant-side setup steps Pollen cannot do via API - platform plugin/extension activation, SEO plugin note, surface connections still pending. Each section says exactly what to do and why. Use when onboarding or when the user asks 'what's left to set up?'.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • connect_meta changes data auth-required never probed

    Start (or restart) connecting the merchant's Meta (Facebook/Instagram) Business catalog to Pollen. Returns an authUrl that the HUMAN must open in a browser to approve via Facebook Login - an agent cannot click it. Afterwards call get_meta_connect_status; the flow may pause on a business or catalog picker (resume with pick_meta_business / pick_meta_catalog). Once active, Pollen publishes the enriched catalog automatically.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • enrich_product changes data auth-required never probed

    Run Pollen's multimodal enrichment on a single product. Returns immediately with a job reference; check `get_pipeline_status` for progress.

    mcp-tool

    {
  "type": "object",
  "required": [
    "productId"
  ],
  "properties": {
    "productId": {
      "type": "string",
      "description": "Pollen internal product ID"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_network_insights reads auth-required 25h ago

    Fetch Hive cross-merchant signal for the merchant's catalog: category benchmarks (avg images, top angles, etc.) alongside the merchant's own catalog stats for comparison. Use when the user asks 'how do I compare to similar stores?'

    mcp-tool

    {
  "type": "object",
  "properties": {
    "category": {
      "type": "string",
      "description": "Optional category to benchmark against (apparel, beauty, home_decor, food_beverage, furniture, jewelry, footwear, fitness, electronics, diy_hardware). If omitted, returns insights across the most common category in the catalog."
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • get_meta_connect_status reads auth-required 25h ago

    Where the Meta connection stands. status: none|selecting_business (call pick_meta_business with a candidate)|selecting_catalog (call pick_meta_catalog with a candidate id or "__create__" for a fresh Pollen-managed catalog)|not_admin (the Facebook account isn't a Business admin - reconnect with the right account)|active|error. When active, includes the live funnel stage and approval counts.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • apply_description changes data auth-required never probed

    Replace ONE product's shopper-visible store description with Pollen's SANITIZED enriched version - the storefrontDescriptionCandidate shown by get_product, NOT the raw agentDescription (hedged sentences and enrichment meta-commentary are stripped before anything touches the store). This overwrites human-facing content, so you MUST show the merchant that exact candidate first and get their explicit approval before calling. Only applies when the store's current description is thin (<200 chars).

    mcp-tool

    {
  "type": "object",
  "required": [
    "productId"
  ],
  "properties": {
    "productId": {
      "type": "string",
      "description": "Pollen internal product ID"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • connect_google changes data auth-required never probed

    Start (or restart) connecting the merchant's Google Merchant Center to Pollen. Returns an authUrl that the HUMAN must open in a browser to grant Google consent - an agent cannot click it. After they approve, call get_google_connect_status to see where the flow landed (it may pause on an account picker or Terms-of-Service acceptance; resume with pick_google_account / accept_google_terms). Once active, Pollen publishes the enriched catalog automatically.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • pick_google_account changes data auth-required never probed

    Resume a Google connect paused on the account picker (status selecting_account). Pass the accountId of one of the candidates returned by get_google_connect_status. On success Pollen finishes the handshake and publishes the catalog automatically.

    mcp-tool

    {
  "type": "object",
  "required": [
    "accountId"
  ],
  "properties": {
    "accountId": {
      "type": "string",
      "description": "Merchant Center account ID from the candidates list"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • accept_google_terms changes data auth-required never probed

    Resume a greenfield Google connect paused on Terms-of-Service acceptance (status tos_required). Only call this after the merchant has confirmed they accept the Google Merchant Center ToS (termsUrl from get_google_connect_status). Creates their Merchant Center account and finishes the handshake.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • pick_meta_business changes data auth-required never probed

    Resume a Meta connect paused on the business picker (status selecting_business). Pass the businessId of a candidate from get_meta_connect_status. May advance to the catalog picker (selecting_catalog) or go straight active.

    mcp-tool

    {
  "type": "object",
  "required": [
    "businessId"
  ],
  "properties": {
    "businessId": {
      "type": "string",
      "description": "Business portfolio ID from the candidates list"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_pipeline_status reads auth-required 18h ago

    Read live pipeline status for the merchant's shop: sync, enrichment (with progress), and writeback. Use when the user asks 'is anything running?' or 'how far along is enrichment?'

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list_products reads auth-required 18h ago

    List products in the merchant's catalog with optional filters. Useful for 'show me products that haven't been enriched yet' or 'find products with the lowest scores'. Returns up to 50 per call.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 25,
      "maximum": 50,
      "minimum": 1
    },
    "search": {
      "type": "string",
      "description": "Match against title/vendor/type"
    },
    "sortBy": {
      "enum": [
        "score_asc",
        "score_desc",
        "updated_desc"
      ],
      "type": "string",
      "default": "updated_desc"
    },
    "enrichmentStatus": {
      "enum": [
        "PENDING",
        "COMPLETED",
        "FAILED",
        "RUNNING"
      ],
      "type": "string",
      "description": "Filter by enrichment status"
    }
  },
  "additionalProperties": false
}
    arguments 35 lines
  • enrich_all_products changes data auth-required never probed

    Run enrichment across the merchant's full catalog (PENDING + FAILED products). Returns a job reference; check `get_pipeline_status` for progress. This is the primary 'do the work' action.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • pick_meta_catalog changes data auth-required never probed

    Resume a Meta connect paused on the catalog picker (status selecting_catalog). Pass a candidate catalog id, or "__create__" to create a dedicated "Pollen - {shop}" catalog. NEVER pick an existing catalog without the merchant's explicit confirmation - Pollen will manage (add/remove) products in it.

    mcp-tool

    {
  "type": "object",
  "required": [
    "catalogId"
  ],
  "properties": {
    "catalogId": {
      "type": "string",
      "description": "Catalog ID from the candidates list, or \"__create__\""
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • update_product_facts changes data auth-required never probed

    Write merchant-supplied physical facts to the store - the 'only you know this' gaps Pollen can't fill from enrichment: SKU, barcode (GTIN/UPC/EAN), weight, and brand. Use when the merchant provides values ('all tees weigh 180 grams', 'barcodes from my supplier sheet'). sku/barcode/weight are per-variant: products with multiple variants need variantId (list them via get_product). Up to 25 updates per call; each returns applied + previous values and the product's new score.

    mcp-tool

    {
  "type": "object",
  "required": [
    "updates"
  ],
  "properties": {
    "updates": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "productId"
        ],
        "properties": {
          "sku": {
            "type": "string"
          },
          "brand": {
            "type": "string",
            "description": "Brand name - written to Shopify vendor / WooCommerce Brands (WC 9.6+)"
          },
          "weight": {
            "type": "number"
          },
          "barcode": {
            "type": "string",
            "description": "GTIN/UPC/EAN"
          },
          "productId": {
            "type": "string",
            "description": "Pollen internal product ID"
          },
          "variantId": {
            "type": "string",
            "description": "Pollen internal variant ID - required when the product has multiple variants and sku/barcode/weight are being set"
          },
          "weightUnit": {
            "enum": [
              "g",
              "kg",
              "oz",
              "lb"
            ],
            "type": "string",
            "description": "Shopify only (default g). WooCommerce uses the store's configured unit."
          }
        },
        "additionalProperties": false
      },
      "maxItems": 25,
      "minItems": 1
    }
  },
  "additionalProperties": false
}
    arguments 55 lines
  • get_product reads auth-required 25h ago

    Fetch full enriched detail for one product by ID. Includes the structured facts, agent description, missing attributes, cultural references, and score breakdown.

    mcp-tool

    {
  "type": "object",
  "required": [
    "productId"
  ],
  "properties": {
    "productId": {
      "type": "string",
      "description": "Pollen internal product ID"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_fix_opportunities reads auth-required 6h ago

    Analyze the catalog's agent-readiness gaps and what can be done about each: points lost per score dimension, counts fixable automatically by Pollen (empty SEO meta, missing image alt text, thin tags), the 'needs you' checklist of physical facts only the merchant knows (SKU, barcode, weight, brand, photos) with product names, and per-product description candidates awaiting merchant approval. Start here when the user asks 'what's wrong?' or 'how do I improve my score?'.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_deep_audit reads auth-required 6h ago

    The Deep Audit report: the AI answer-visibility test (frozen shopper questions asked to Claude and Gemini - cited or not, with evidence), the catalog fix plan, and the worst-scoring products with their missing attributes. Access requires the $9 one-time purchase or any paid plan; without access this returns what the report contains and how to unlock it.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_google_connect_status reads auth-required 6h ago

    Where the Google connection stands. status: none|selecting_account (call pick_google_account with one of the returned candidates)|tos_required (call accept_google_terms)|verifying|awaiting_approval|connector_pending (Pollen is finishing setup server-side - just re-check later)|active|claim_conflict|not_admin|error. When active, includes the live funnel stage (publishing/in_review/live) and approval counts.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 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 a587d51dda4fc495.

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