Servidor MCP de SKULayer

• Nome no registrocom.skulayer/skulayerverificado no registro MCP

O nome no registro fica sob skulayer.com. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

• Estadorespondeverificado em 2026-10-25
• Ferramentas19
• O servidor se chamaskulayer
• Versão do servidor1.4.0
• Versão do protocolo2025-06-18

Em 2026-10-25 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 24 ms.

• As ferramentas fazem todos os casos de uso verificados: find missing availability and description data in product feeds; review suggested feed fixes before they reach Google Shopping.
• Verificado em 2 dos 7 dias necessários para julgar a confiabilidade.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 2 até agora
• O que um agente consegue fazer com ele2 de 2 casos de uso
• Respondeumedindo2 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta864 ms
• Espaço no contexto do agente≈ 3.883 tokensas definições de todas as ferramentas (19), que o agente carrega a cada turno
• Definições das ferramentasA · 100 de 100
• Resultados tipados0 de 19 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Todas as ferramentas passam nas seis verificações.

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (30%), se faz o trabalho do produto (25%), definições (20%), contexto (10%) e uso (15%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

• list_feeds

  List every live feed in the workspace: source format, schedule, status, channels, item count, and the latest run summary (including audit issue count). Start here to find feed ids. Archived feeds are not listed: they do not run and do not…

• get_feed

  Full detail for one feed: configuration, latest complete run summary, and the size of its rule stack. Works on an archived feed too, and says so, so an id from an earlier conversation resolves to an explanation rather than a not-found.

• list_rules

  The feed's rule stack in execution order: names, enabled state, a plain-English summary, and the full JSON definition of each rule.

• get_audit_findings

  Audit findings for the latest complete run, grouped by check with severity, counts, sample item ids, and plain-English guidance on why each finding costs money and how to fix it. The audit measures the DELIVERED feed (after rules). Also…

• get_field_inventory

  What the merchant's source feed ACTUALLY contained, and what SKULayer did with each field: every field as their platform sends it, how many items carry a value for it, whether it was recognised as a shopping attribute, kept as a custom…

• get_merchant_issues

  Google's OWN verdict on a feed, from its Merchant Center connection (the app's What Google sees panel): per-issue-code cases with severity, affected-item counts, sample ids, Google's description and documentation link, and an honest…

• search_items

  Search or page through the items of the latest complete run. Returns delivered items (what channels receive) by default, with base (pre-rules) available via view. query matches id, title, brand, and product type, case-insensitive.

• preview_rule

  Preview an UNSAVED rule against a sample of the latest run: match/change/exclusion counts, per-field change tallies, danger warnings (required fields emptied, identifiers stripped, heavy exclusion), audit deltas, and example before/after…

• search_taxonomy

  Search Google's product taxonomy — the set of valid googleProductCategory values. Returns ranked category paths with their numeric ids, plus whether the query itself is already a valid category (full path or id). Use it to find the right…

• map_categories

  Propose a googleProductCategory mapping for a feed: groups the latest run's delivered items by distinct productType, matches each onto Google's taxonomy (exact-path and unique-leaf matches first, then candidate-constrained AI when…

• create_rule

  Create a rule on a feed. The definition is validated, the standard preview runs server-side, and the report comes back WITH the created rule: match/change/exclusion counts, per-field tallies, warnings, and audit deltas. Show the human…

• set_rule_enabled

  Enable or disable one rule by id. Disabling takes a rule out of the stack from the next run onward; nothing else about it changes. Use list_rules to find rule ids.

• delete_rule

  Delete one rule by id. This is permanent; prefer set_rule_enabled with enabled=false when the human might want the rule back. Takes effect on the next run.

• trigger_run

  Start a feed run: fetch the source, apply rules, audit the delivered output, and compile channel files. This tool needs a write-scoped connection. The workspace SKU limit, the manual-run cap, and one run at a time per feed also apply…

• get_run_status

  One run's progress and outcome: status (queued/fetching/auditing/transforming/compiling/complete/failed), item counts, audit issue count, timing, and the error message when a run failed. Use after trigger_run to poll to completion.

• start_merchant_link

  Start connecting Google Merchant Center for this workspace. Returns a short-lived, single-use SKULayer URL the workspace owner must open while signed in as the same person. That page sends them to Google consent and, when Google shows one…

• get_merchant_link

  Read this workspace's Merchant Center link. status is linked, pending, expired, error, or none (nothing started). accounts lists Merchant Center account ids and the connection each one belongs to. connections lists stored rows, including…

• select_merchant_account

  Choose which Merchant Center account a feed uses. Required when get_merchant_link lists more than one account. Pass connectionId and accountId from that result, plus feedId. The account must be one Google actually showed for this…

• get_activity

  The workspace's recent activity: who did what and when, across the app and every agent connection. Each event has an actor (a human user, an agent via a token or sign-in, or the system scheduler), the action (rule…