_ registry / mcp streamable-http · checked 43m ago

refy

https://refy.design

Registry code: 193ac4826e7e2a61

api record

Refy é um design system. Para montar tela: refy_search com a necessidade, refy_component na família escolhida, escreva o código, refy_validate no resultado. Para identidade visual: refy_theme_generate e refy_theme_validate; para partir de um site, refy_theme_extract. Cor, fonte e raio vêm do tema, nunca de CSS solto. Este é o servidor remoto: não lê arquivos da máquina de quem usa; passe o código em refy_validate.

endpoint
https://refy.design/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 refy live?
Yes — it answered the hub's last check (checked 43m ago). It answered 100% of checks over the last 30 days.
Is refy free to use?
Yes — the hub reached it with no key and no payment.
What tools does refy have?
7 tools: refy_search, refy_validate, refy_theme_generate, refy_theme_validate, refy_theme_extract, refy_component, refy_collections.
Is refy 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
100%

90 days 100%· all time 100%

latency
384ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 7 tools
1 open 6 never probed 1 of 7 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.

  • refy_collections open 43m ago

    Lista as coleções do catálogo (core e especializadas) com os membros reais de cada uma.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "query": {
          "type": "string"
        },
        "version": {
          "type": "string",
          "description": "Versão do pacote cuja API você quer ler (ex.: 1.2.0). Padrão: a versão deste servidor."
        }
      }
    }
    arguments 12 lines
  • refy_search unknown never probed

    Encontra a família do Refy para uma necessidade descrita em português, inglês ou espanhol ("confirmar antes de apagar", "lista suspensa com busca"). Devolve as famílias em ordem, com o motivo, como usar, quando usar outra e o import.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 5,
          "maximum": 20,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "A necessidade da tela, em linguagem natural."
        },
        "version": {
          "type": "string",
          "description": "Versão do pacote cuja API você quer ler (ex.: 1.2.0). Padrão: a versão deste servidor."
        },
        "collection": {
          "type": "string",
          "description": "Filtra por coleção (core, media, geolocation, conversation, analytics...)."
        }
      }
    }
    arguments 26 lines
  • refy_validate unknown never probed

    Confere código de tela contra o contrato do Refy: props obrigatórias, valores fora da união aceita, props fora da API, controles HTML crus, cor/fonte literal e import interno. Recebe o código da tela em code.

    mcp-tool

    {
      "type": "object",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "description": "Código da tela (TSX/JSX/TS/JS/CSS)."
        },
        "theme": {
          "type": "object",
          "description": "Tema do projeto (RefyTheme, ou objeto com vários temas). Tokens declarados nele não geram unverified-token. Com files, sem theme, vale o theme.json da raiz do projeto."
        },
        "version": {
          "type": "string",
          "description": "Versão do pacote cuja API você quer ler (ex.: 1.2.0). Padrão: a versão deste servidor."
        },
        "filename": {
          "type": "string",
          "description": "Nome do arquivo do código, define a linguagem. Padrão: Tela.tsx."
        }
      }
    }
    arguments 24 lines
  • refy_theme_generate unknown never probed

    Gera um tema completo (claro e escuro) a partir da cor primária, com raio, densidade e fontes opcionais. O tema sai no formato do ThemeProvider e já conferido: tokens reconhecidos, referências e contraste AA.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name",
        "primary"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Identificador: minúsculas, números e hífen."
        },
        "label": {
          "type": "string",
          "description": "Nome de exibição."
        },
        "radius": {
          "enum": [
            "sharp",
            "default",
            "round"
          ],
          "type": "string"
        },
        "density": {
          "enum": [
            "compact",
            "default",
            "comfortable"
          ],
          "type": "string"
        },
        "primary": {
          "type": "string",
          "description": "Cor primária em hexadecimal, ex.: #2163ad."
        },
        "fontBody": {
          "type": "string"
        },
        "fontMono": {
          "type": "string"
        },
        "description": {
          "type": "string"
        },
        "fontHeading": {
          "type": "string"
        }
      }
    }
    arguments 49 lines
  • refy_theme_validate unknown never probed

    Confere um tema (objeto do ThemeProvider) contra o contrato dos temas do Refy: tokens reconhecidos, label, referências resolvíveis e contraste AA de texto, estado e marca, no claro e no escuro.

    mcp-tool

    {
      "type": "object",
      "required": [
        "theme"
      ],
      "properties": {
        "theme": {
          "type": "object"
        }
      }
    }
    arguments 11 lines
  • refy_theme_extract unknown 43m ago

    Lê cores, fontes e raios de um site e monta um tema do Refy (claro e escuro) já conferido em contraste AA, com a razão de cada escolha. Recebe url (lê o HTML e o CSS servidos), html/css, ou observations da sonda refy://theme-probe rodada no navegador do agente, que é a leitura mais fiel para site montado por JavaScript.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "css": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Folhas de estilo, no lugar de url."
        },
        "url": {
          "type": "string",
          "description": "Endereço público do site, http ou https."
        },
        "html": {
          "type": "string",
          "description": "HTML da página, no lugar de url."
        },
        "name": {
          "type": "string",
          "description": "Identificador do tema: minúsculas, números e hífen. Padrão: o domínio."
        },
        "label": {
          "type": "string"
        },
        "description": {
          "type": "string"
        },
        "observations": {
          "type": "array",
          "items": {
            "type": "object"
          },
          "description": "Saída da sonda refy://theme-probe (campo observations)."
        }
      }
    }
    arguments 37 lines
  • refy_component unknown 43m ago

    Devolve a API real (props, tipos, obrigatórias), exemplos de código, uso, alternativas e teclado de uma família ou de um membro documentado (ex.: Button, CardHeader, D3Chart).

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string"
        },
        "version": {
          "type": "string",
          "description": "Versão do pacote cuja API você quer ler (ex.: 1.2.0). Padrão: a versão deste servidor."
        }
      }
    }
    arguments 15 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 193ac4826e7e2a61.

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