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

blueprint-modular

https://blueprint-modular.com

Registry code: fb0e1d19b562f14a

api record

Catalogue read-only des composants Blueprint Modular (@blueprint-modular/core). 172 composants. Flux conseillé : list_components / search_components pour explorer, get_component pour la signature exacte (props/exemple) et la couche sémantique (rôle, frame Ω, indicateur, guidance), suggest_composition pour partir d'un besoin. Aucune écriture, aucune authentification, aucune donnée personnelle.

endpoint
https://blueprint-modular.com/api/mcp
protocol
http-sse ·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 blueprint-modular live?
Yes — it answered the hub's last check (checked 2h ago). It answered 97% of checks over the last 30 days.
Is blueprint-modular free to use?
Yes — the hub reached it with no key and no payment.
What tools does blueprint-modular have?
4 tools: suggest_composition, get_component, search_components, list_components.
Is blueprint-modular 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
96.9%

90 days 94.1%· all time 94.1%

latency
93ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 236 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • list ui components of a design system
  • search components for a need
  • get component props and example
  • suggest component composition
takes → gives
text → data, code
tools
4 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 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.

  • list_components reads open 6h ago

    Liste les composants du design system Blueprint Modular (nom + description en une ligne). À UTILISER pour parcourir le catalogue ou découvrir ce qui existe dans une catégorie donnée. Résultat paginé par curseur (réutiliser 'nextCursor' pour la page suivante). Catégories : Affichage de données, Feedback, Graphiques, IA & Spécialisés, Identification & traçabilité, Interaction, Mise en page, Média, Navigation, Utilitaires.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "cursor": {
          "type": "string",
          "description": "Curseur de pagination renvoyé par un appel précédent (nextCursor). Optionnel."
        },
        "category": {
          "type": "string",
          "description": "Filtre par catégorie exacte ou partielle (ex. 'Graphiques'). Optionnel."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • suggest_composition reads unknown 2h ago

    Suggère une liste de composants Blueprint Modular répondant à un besoin décrit en langage naturel, en raisonnant sur la couche sémantique (rôle, frame Ω, guidance) : chaque suggestion explicite son sens (meaning) et ses associations sémantiques (pairWith). À UTILISER pour partir d'une intention d'écran (ex. 'un dashboard avec des métriques et un graphique') et obtenir les briques pertinentes. Réponse bornée.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "need"
      ],
      "properties": {
        "need": {
          "type": "string",
          "minLength": 1,
          "description": "Description du besoin / de l'écran à construire."
        },
        "limit": {
          "type": "integer",
          "minimum": 1,
          "description": "Nombre max de suggestions (défaut 8 ; plafonné à 12). Optionnel."
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • get_component reads unknown 6h ago

    Retourne le détail complet d'un composant : description, props/types, exemple d'usage, composants associés/parents et couche sémantique (rôle, frame Ω, type d'indicateur, directionnalité, guidance agent — valeurs proposées, ontologie curée par l'humain). À UTILISER après list/search pour obtenir la signature exacte ET le sens du composant avant de générer du code. Le nom accepte 'bpm.metric' ou 'metric'.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "minLength": 1,
          "description": "Nom du composant (ex. 'bpm.metric' ou 'metric')."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • search_components reads unknown 6h ago

    Recherche les composants pertinents pour une requête en texte libre (match sur nom, description, catégorie et tags), triés par pertinence. À UTILISER quand on cherche un composant par fonction ou mot-clé (ex. 'tableau triable', 'graphique', 'upload fichier'). Résultat paginé par curseur.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "Termes de recherche en langage naturel."
        },
        "cursor": {
          "type": "string",
          "description": "Curseur de pagination renvoyé par un appel précédent (nextCursor). Optionnel."
        }
      },
      "additionalProperties": false
    }
    arguments 19 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 fb0e1d19b562f14a.

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