Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Pollen — Managed Agent-Readiness Layer

REMOTE · POLLEN.ELYTRON.IN

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

0 this week 91 Trust /100

Last scanned (21 hours ago)

Scores higher than 98% of remote servers

Reachable. Last reached 4 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1820 tokens (~79/item across 23 items; 23 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 69% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Nov 26 0
    • Stability: fail → pass ▲ security
  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 92 to 95.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 85 to 89.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 79 to 82.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 69 to 75.

  • 10 Oct 26 +3

    No change was recorded against any check on this day. Stability & Change Management went from 49 to 69.

  • 4 Oct 26 0
    • Stability: 0.50 → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “set_llm_provider” was removed ▼ security
  • 2 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://pollen.elytron.in/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=elytron.in CN=WE1,O=Google Trust Services,C=US 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA256 169588d73f8940c61300803a6f81a6f4
SANs: elytron.in, *.elytron.in
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of pollen.elytron.in. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
in. present 10094 13 Verified
elytron.in. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://pollen.elytron.in/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://pollen.elytron.in/.well-known/oauth-protected-resource"
Header Value
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Protected resource metadata

Document https://pollen.elytron.in/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://pollen.elytron.in/mcp
Authorisation server https://pollen.elytron.in

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pollen.elytron.in/mcp Verified 200
http (plaintext) http://pollen.elytron.in/mcp HTTPS enforced 301 https://pollen.elytron.in/mcp
MCP tools · 23 exposed · ~1,820 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
accept_google_terms ~61

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

apply_description ~109

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).

NameTypeReqDescription
productIdstringyesPollen internal product ID

No output schema declared.

No examples provided.

apply_fixes ~125

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.

NameTypeReqDescription
fixTypestringyes–

No output schema declared.

No examples provided.

connect_google ~97

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

connect_meta ~92

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

enrich_all_products ~49

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

enrich_product ~49

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

NameTypeReqDescription
productIdstringyesPollen internal product ID

No output schema declared.

No examples provided.

get_account_summary ~59

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?'

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_deep_audit ~83

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_fix_opportunities ~110

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?'.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_google_connect_status ~97

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_meta_connect_status ~90

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_network_insights ~111

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?'

NameTypeReqDescription
categorystring–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 com…

No output schema declared.

No examples provided.

get_pipeline_status ~49

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?'

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_product ~49

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

NameTypeReqDescription
productIdstringyesPollen internal product ID

No output schema declared.

No examples provided.

get_setup_instructions ~65

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?'.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_products ~87

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.

NameTypeReqDescription
enrichmentStatusstring–Filter by enrichment status
limitinteger––
searchstring–Match against title/vendor/type
sortBystring––

No output schema declared.

No examples provided.

pick_google_account ~68

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.

NameTypeReqDescription
accountIdstringyesMerchant Center account ID from the candidates list

No output schema declared.

No examples provided.

pick_meta_business ~67

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.

NameTypeReqDescription
businessIdstringyesBusiness portfolio ID from the candidates list

No output schema declared.

No examples provided.

pick_meta_catalog ~90

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.

NameTypeReqDescription
catalogIdstringyesCatalog ID from the candidates list, or "__create__"

No output schema declared.

No examples provided.

sync_catalog ~42

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

update_product_facts ~126

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.

NameTypeReqDescription
updatesarrayyes–

No output schema declared.

No examples provided.

write_back_to_store ~45

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'.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Pollen — Managed Agent-Readiness Layer MCP server?

Pollen — Managed Agent-Readiness Layer is a hosted endpoint at https://pollen.elytron.in/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · pollen.elytron.in

# add to Claude Code
claude mcp add --transport http in-elytron-pollen 'https://pollen.elytron.in/mcp'
Common questions

What is the Pollen — Managed Agent-Readiness Layer MCP server?

Pollen — Managed Agent-Readiness Layer is an MCP server listed in the public MCP registry as in.elytron/pollen. Manage your Pollen account: sync, enrich, fix, and publish your store's catalog for AI agents. This page covers its hosted endpoint (https://pollen.elytron.in/mcp).

Is the Pollen — Managed Agent-Readiness Layer MCP server safe to use?

Pollen — Managed Agent-Readiness Layer scores 91 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Pollen — Managed Agent-Readiness Layer MCP server expose?

Pollen — Managed Agent-Readiness Layer exposes 23 tools: get_account_summary, get_deep_audit, list_products, get_product, get_pipeline_status, and 18 more. Their descriptions and schemas cost roughly 1,820 tokens of context every time the server is loaded.

Does the Pollen — Managed Agent-Readiness Layer MCP server require authentication?

Yes. Pollen — Managed Agent-Readiness Layer asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Pollen — Managed Agent-Readiness Layer MCP server still maintained?

Pollen — Managed Agent-Readiness Layer is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.