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

skulayer

https://skulayer.com

Registry code: e9c3d1bfe4966a29

api record

SKULayer gives retailers and agencies agent-readable product data: feed optimisation that audits merchant product feeds, transforms them with rules, and serves cleaner versions to Google Shopping and Meta. Read tools inspect feeds, runs, audits, Merchant Center verdicts on connected feeds, source-field inventory, delivered items, Google's product taxonomy, and rule previews without changing data. get_merchant_link reports whether Merchant Center is linked. Write tools need a write-scoped token: create_rule returns the standard preview report with the created rule, including any danger-level…

endpoint
https://skulayer.com/mcp
protocol
streamable-http ·2025-06-18
authentication
bearer
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 skulayer live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is skulayer 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 skulayer have?
19 tools: get_merchant_issues, search_items, list_feeds, list_rules, preview_rule, get_field_inventory, get_feed, get_audit_findings, ….
Is skulayer 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.5%

90 days 99.7%· all time 99.7%

latency
603ms

last good check

priced tools
0

of 19 tools

_ answered our checks, 90 days 327 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
payments & commerce shopping & products
used for
  • audit product feeds
  • fix product data
  • serve product feeds to agents
takes → gives
data → 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 19 tools
19 auth-required 19 of 19 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.

  • get_merchant_issues auth-required 13h ago

    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 lifecycle state — open, fix_shipped (a rule shipped, Google has not re-read yet), or cleared (Google stopped reporting it). Includes account-level issues and the latest pull's scan summary. Complements get_audit_findings: the audit is what SKULayer thinks, this is what Google thinks. Requires the feed to be connected in the app; fixes are built like any rule — preview_rule then create_rule.

    mcp-tool

    {
  "type": "object",
  "required": [
    "feedId"
  ],
  "properties": {
    "feedId": {
      "type": "string",
      "description": "Feed id from list_feeds."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • search_items auth-required 9h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "feedId"
  ],
  "properties": {
    "view": {
      "enum": [
        "delivered",
        "base"
      ],
      "type": "string",
      "description": "delivered = after rules (default); base = as ingested."
    },
    "limit": {
      "type": "number",
      "description": "Items to return, max 25 (default 10)."
    },
    "query": {
      "type": "string",
      "description": "Substring match on id, title, brand, or product type. Omit to page through everything."
    },
    "feedId": {
      "type": "string",
      "description": "Feed id from list_feeds."
    },
    "offset": {
      "type": "number",
      "description": "Scan offset into the run for paging (default 0)."
    }
  },
  "additionalProperties": false
}
    arguments 33 lines
  • list_feeds auth-required 6h ago

    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 serve, and only a person can restore one, in the app.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list_rules auth-required 13h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "feedId"
  ],
  "properties": {
    "feedId": {
      "type": "string",
      "description": "Feed id from list_feeds."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • preview_rule auth-required 13h ago

    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 diffs. Nothing is written anywhere. Rule definition format: {"when":{"all":[conditions],"any":[conditions],"anyOf":[{"all":[conditions]}]},"then":[actions]} — anyOf is an OR of condition groups, AND-ed with the top-level conditions. Actions: set/copy/replace/append/prepend/lookup/extract/shorten/calculate/round/concat/normalize/strip_html/remove_duplicates (dedupe a separator-delimited list value)/clear/fallback/from_parent/exclude/exclude_group. Condition ops: eq, ne, contains, not_contains, starts_with, not_starts_with, ends_with, not_ends_with, regex, not_regex, gt, lt, gte, lte, between, not_between (take "values": [min,max]), longer_than, shorter_than, in_list, not_in_list (take "values": string[]), in_list_regex, not_in_list_regex (take "values" of regex patterns; match when any pattern matches), date_before, date_after ("today", "today+/-N" or "YYYY-MM-DD"), date_range_active, date_range_inactive (no value; test the ISO range in the field against now), empty, not_empty. Conditions may use "valueField" to compare against another field instead of a literal. Variant groups (items sharing custom:item_group_id): exclude_group {"match":"any"|"all", default "any"} removes the whole family when any/every member matches the conditions and must be the rule's only action; from_parent {"field"} copies the group parent's value onto matching variants (parent = the member whose id equals the group id, else the first member); the condition pseudo-field "group:size" is the family's member count (numeric ops only). Group exclusions are reported as whole groups in the preview warnings.

    mcp-tool

    {
  "type": "object",
  "required": [
    "feedId",
    "definition"
  ],
  "properties": {
    "feedId": {
      "type": "string",
      "description": "Feed id from list_feeds."
    },
    "definition": {
      "type": "object",
      "description": "The rule definition JSON to preview."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • get_field_inventory auth-required 16h ago

    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 attribute, or arrived empty on every row, plus per-attribute coverage before and after the rule stack. Completes the triad with get_audit_findings (what SKULayer thinks) and get_merchant_issues (what Google thinks): this is what the merchant sent. Use it BEFORE proposing rules. It is the only way to tell an attribute the merchant never sends from one they send blank from one they send with a value we cannot use, all three of which look identical in the audit.

    mcp-tool

    {
  "type": "object",
  "required": [
    "feedId"
  ],
  "properties": {
    "feedId": {
      "type": "string",
      "description": "Feed id from list_feeds."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_feed auth-required 16h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "feedId"
  ],
  "properties": {
    "feedId": {
      "type": "string",
      "description": "Feed id from list_feeds."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_audit_findings auth-required 16h ago

    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 returns `opportunities`: attributes left empty whose value was found in another field the merchant DID send (e.g. the brand sitting in the title, matched against brands the same feed already uses), each with exact fill and decline counts, the evidence, and a ready rule definition to pass straight to preview_rule. Opportunities are not defects: they sit outside totalIssues and the readiness score.

    mcp-tool

    {
  "type": "object",
  "required": [
    "feedId"
  ],
  "properties": {
    "feedId": {
      "type": "string",
      "description": "Feed id from list_feeds."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_merchant_link auth-required 6h ago

    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 revoked, and which feeds are attached. When status is pending and accounts has more than one entry, the owner has not chosen yet: call select_merchant_account with connectionId, accountId and feedId. Does not return tokens or the consent URL.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • search_taxonomy auth-required 9h ago

    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 category for a product type, to fix unmatched entries from map_categories, or to check a value before writing it into a rule.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "number",
      "description": "Results to return, max 25 (default 10)."
    },
    "query": {
      "type": "string",
      "description": "Free text (\"sofa bed\"), a full path, or a numeric category id."
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • get_run_status auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "feedId",
    "runId"
  ],
  "properties": {
    "runId": {
      "type": "string",
      "description": "Run id from trigger_run or list_feeds."
    },
    "feedId": {
      "type": "string",
      "description": "Feed id from list_feeds."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • get_activity auth-required 6h ago

    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 created/updated/enabled/disabled/deleted, run triggered, Merchant Center link started/completed, Merchant Center account chosen), the feed, and a short summary. Use it to check what changed lately, or what you and others have already done, before acting again. Note that counts in a summary are preview SAMPLE counts, not catalog totals: compare them against the sampled figure alongside them. On a workspace with hourly feeds, scheduled runs dominate the newest events, so pass actorTypes to see human and agent changes.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "How many events to return, newest first (max 100, default 50)."
    },
    "actorTypes": {
      "type": "array",
      "items": {
        "enum": [
          "user",
          "agent",
          "system"
        ],
        "type": "string"
      },
      "description": "Narrow to these actor types. Omit for everything. Pass [\"user\",\"agent\"] to skip scheduled runs, which are high volume on hourly feeds and can fill the window on their own."
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • map_categories auth-required never probed

    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 available and useAi is not false), and returns the mapping table WITH a ready-to-save rule definition (one lookup keyed on productType). NOTHING is saved: show the human the mapping, resolve unmatched product types with search_taxonomy and edit the rule's table, then save with create_rule — which runs the standard preview and returns the impact report. Options: onlyMissing=true scopes the rule to items with no category yet; defaultCategory (a valid taxonomy path) is applied to items whose productType is not in the table.

    mcp-tool

    {
  "type": "object",
  "required": [
    "feedId"
  ],
  "properties": {
    "useAi": {
      "type": "boolean",
      "description": "Use AI for product types with no deterministic taxonomy match (default true). AI mapping is rate-limited. When it is not available, call again with useAi=false for deterministic matches."
    },
    "feedId": {
      "type": "string",
      "description": "Feed id from list_feeds."
    },
    "onlyMissing": {
      "type": "boolean",
      "description": "Scope the suggested rule to items with an empty googleProductCategory (default false: the reviewed mapping also fixes wrong existing values)."
    },
    "defaultCategory": {
      "type": "string",
      "description": "Optional valid taxonomy path applied when an item's productType is not in the table."
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
  • create_rule auth-required never probed

    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 this report; danger-level warnings mean the rule can empty required fields or exclude heavily. The rule lands enabled, appended after existing rules, and applies on the NEXT run (never to the live delivered feed mid-flight). Same definition format as preview_rule.

    mcp-tool

    {
  "type": "object",
  "required": [
    "feedId",
    "name",
    "definition"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Human-readable rule name, 2 to 120 characters."
    },
    "feedId": {
      "type": "string",
      "description": "Feed id from list_feeds."
    },
    "definition": {
      "type": "object",
      "description": "The rule definition JSON (same format as preview_rule)."
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • set_rule_enabled auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "feedId",
    "ruleId",
    "enabled"
  ],
  "properties": {
    "feedId": {
      "type": "string",
      "description": "Feed id from list_feeds."
    },
    "ruleId": {
      "type": "string",
      "description": "Rule id from list_rules."
    },
    "enabled": {
      "type": "boolean",
      "description": "true = in the stack, false = skipped."
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • delete_rule auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "feedId",
    "ruleId"
  ],
  "properties": {
    "feedId": {
      "type": "string",
      "description": "Feed id from list_feeds."
    },
    "ruleId": {
      "type": "string",
      "description": "Rule id from list_rules."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • trigger_run auth-required never probed

    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. Returns a runId. Poll get_run_status until it completes. An in-flight run never affects the live delivered feed.

    mcp-tool

    {
  "type": "object",
  "required": [
    "feedId"
  ],
  "properties": {
    "feedId": {
      "type": "string",
      "description": "Feed id from list_feeds."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • start_merchant_link auth-required never probed

    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 account, links it. You never receive Google tokens. Optional feedId attaches that feed when there is exactly one account. If there are several, poll get_merchant_link and call select_merchant_account. Owner only. At most 5 starts per workspace per hour, on top of the normal MCP rate limit. Does not add a data source and does not write to Merchant Center.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "feedId": {
      "type": "string",
      "description": "Feed to attach when Google shows exactly one Merchant Center account. Omit to connect the account without attaching a feed yet."
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • select_merchant_account auth-required never probed

    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 connection. Owner only. Does not write a feed or a data source to Google.

    mcp-tool

    {
  "type": "object",
  "required": [
    "connectionId",
    "accountId",
    "feedId"
  ],
  "properties": {
    "feedId": {
      "type": "string",
      "description": "Feed that should read this Merchant Center account."
    },
    "accountId": {
      "type": "string",
      "description": "Merchant Center account id from get_merchant_link."
    },
    "connectionId": {
      "type": "string",
      "description": "connectionId from get_merchant_link."
    }
  },
  "additionalProperties": false
}
    arguments 23 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 e9c3d1bfe4966a29.

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