Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.

Yes — the hub reached it with no key and no payment.

What tools does ply have?

3 tools: search_components, get_component, list_components.

Is ply 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.

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

ply

https://mcp.ply-ui.com

Registry code: 51c711c37d9cb81b

api record

List, search, and inspect Ply Angular + Tailwind copy-in components.

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

endpoint: https://mcp.ply-ui.com/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 ply live?: Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is ply free to use?: Yes — the hub reached it with no key and no payment.
What tools does ply have?: 3 tools: search_components, get_component, list_components.
Is ply 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.1%

90 days 99.4%· all time 99.4%

latency

162ms

last good check

priced tools

of 3 tools

_ answered our checks, 90 days 354 checks · signed record

2026-11-13 22:50 degraded → live
2026-11-12 13:36 live → degraded· timeout after 20000ms
2026-10-12 11:07 down → live
2026-09-28 11:42 unknown → live

_ what it is for

topic: developer tools code & repositories
used for: search angular ui components
get component metadata and source
list components by category
takes → gives: text → data, code
tools: 3 reads

_ 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

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 3 tools

1 open 2 never probed 1 of 3 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.

list_components reads open 11h ago

List components from the Ply registry. Filter by tier (free|pro|all), category, or name substring. Does not install anything. To copy a component into a project, tell the user to run npx ply-ui-cli add <name>.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "q": {
      "type": "string",
      "description": "Substring filter on name, description, usage, or keywords (case-insensitive)"
    },
    "tier": {
      "enum": [
        "free",
        "pro",
        "all"
      ],
      "type": "string",
      "default": "all",
      "description": "Filter by license tier"
    },
    "category": {
      "enum": [
        "application",
        "page-layout",
        "block",
        "widget",
        "shell",
        "component"
      ],
      "type": "string",
      "description": "Filter by registry category"
    }
  }
}

arguments 32 lines

search_components reads unknown 11h ago

Fuzzy / token search over registry component names (e.g. "dialog", "sheet", "carousel"). Does not install anything. Prefer this before guessing names, then give the user npx ply-ui-cli add <name> (or local stdio add_components).

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "tier": {
      "enum": [
        "free",
        "pro",
        "all"
      ],
      "type": "string",
      "default": "all",
      "description": "Filter by license tier"
    },
    "limit": {
      "type": "integer",
      "default": 12,
      "maximum": 40,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "minLength": 1,
      "description": "Natural-language or substring query (e.g. \"dialog modal\", \"button\"). Matches name, description, usage, and keywords."
    },
    "category": {
      "enum": [
        "application",
        "page-layout",
        "block",
        "widget",
        "shell",
        "component"
      ],
      "type": "string",
      "description": "Filter by registry category"
    }
  }
}

arguments 42 lines

get_component reads unknown 11h ago

Get registry metadata for one component (deps, category, file list). Free source only when includeSource=true. Pro source is never streamed via MCP. Does not install; returns installCommand (npx ply-ui-cli add <name>).

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Registry component name (e.g. button, card)"
    },
    "includeSource": {
      "type": "boolean",
      "default": false,
      "description": "If true, include free-tier source file contents. Pro source is never returned via MCP in V1."
    }
  }
}

arguments 18 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.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
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.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 51c711c37d9cb81b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/51c711c37d9cb81b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/51c711c37d9cb81b/badge.svg)](https://brick.blue/agent/51c711c37d9cb81b?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

70%

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

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.