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

lamina-workflow-discovery

https://app.uselamina.ai

Registry code: 229d953f2b178693

api record

On-brand product photos, model try-ons, video reels & banners from a brief + brand kit.

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

endpoint
https://app.uselamina.ai/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 lamina-workflow-discovery live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is lamina-workflow-discovery free to use?
Yes — the hub reached it with no key and no payment.
What tools does lamina-workflow-discovery have?
4 tools: execute_public_workflow, get_public_workflow_execution_status, recommend_public_workflows, prepare_public_workflow_execution.
Is lamina-workflow-discovery 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.6%

90 days 99.4%· all time 99.4%

latency
228ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 511 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
media generation images
used for
  • generate on-brand product photos
  • create model try-on images
  • create video reels and banners
  • recommend a creative workflow
takes → gives
text, images → images, video
tools
3 reads1 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 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.

  • execute_public_workflow changes data unknown never probed

    Use this from the Lamina widget after the user fills the Lamina form and clicks Generate. Starts a public workflow execution.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "appId",
    "inputValues"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "minLength": 1,
      "description": "The Lamina public workflow ID to execute."
    },
    "inputValues": {
      "type": "object",
      "description": "Workflow form values keyed by public parameter key.",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "idempotencyKey": {
      "type": "string",
      "minLength": 1,
      "description": "Stable Lamina-generated key reused across retries for the same widget submission."
    }
  }
}
    arguments 28 lines
  • get_public_workflow_execution_status reads unknown 13h ago

    Use this from the Lamina widget to poll a running public workflow execution and fetch media results when it completes.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "executionId"
  ],
  "properties": {
    "executionId": {
      "type": "string",
      "minLength": 1,
      "description": "The Lamina public execution ID to inspect."
    }
  }
}
    arguments 14 lines
  • recommend_public_workflows reads unknown 13h ago

    Use this when the user wants to create or edit an image or video and you should recommend the best Lamina public workflows. Do not use this to execute a workflow.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "userRequest"
  ],
  "properties": {
    "mediumHint": {
      "enum": [
        "image",
        "video"
      ],
      "type": "string",
      "description": "Optional hint when the user explicitly wants image or video output."
    },
    "userRequest": {
      "type": "string",
      "minLength": 1,
      "description": "The user request for an image or video workflow."
    }
  }
}
    arguments 22 lines
  • prepare_public_workflow_execution reads unknown 13h ago

    Use this after the user selects a Lamina workflow so you can render the Lamina form widget with every required input. Do not ask the user to type the inputs in chat when the widget form can collect them.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "appId"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "minLength": 1,
      "description": "The Lamina public workflow ID chosen by the user."
    }
  }
}
    arguments 14 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 229d953f2b178693.

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

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.