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

nasaq

https://mcp.nasaqui.com

Registry code: 583601b1a1746f0e

api record

Nasaq (نسق) is a bilingual (English/Arabic, LTR/RTL) React design system built on Base UI and Tailwind v4. Before writing UI with Nasaq: call get_setup once, then list_components or search_components to find the right component, then get_component for its manual (props, examples, accessibility, RTL rules). Use only props the manual documents. Colours come from tokens (bg-nq-*, text-nq-*); never hard-code hex. Never recolour, mirror or redraw a product logo. Docs: https://docs.nasaqui.com. Components can also be added with the shadcn CLI: npx shadcn@latest add @nasaq/<name>. Not on React? Pass…

endpoint
https://mcp.nasaqui.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 nasaq live?
Yes — it answered the hub's last check (checked 49m ago). It answered 100% of checks over the last 30 days.
Is nasaq free to use?
Yes — the hub reached it with no key and no payment.
What tools does nasaq have?
6 tools: search_components, get_component, get_setup, list_tokens, get_foundation, list_components.
Is nasaq 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
362ms

last good check

priced tools
0

of 6 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 6 tools
3 open 3 never probed 3 of 6 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_tokens open 49m ago

    CSS custom properties (--nq-*) with their value in each context (light, dark, brand, density). Filter by prefix, e.g. '--nq-danger' or 'surface'. In Tailwind use them as utilities: bg-nq-surface, text-nq-fg-muted, border-nq-border.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 500,
      "minimum": 1
    },
    "prefix": {
      "type": "string"
    }
  }
}
    arguments 14 lines
  • get_foundation open 49m ago

    Design rules behind the components: colour roles, layout and density, architecture, brand/logo rules, README spec. Omit `topic` to list topics.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "topic": {
      "type": "string"
    }
  }
}
    arguments 9 lines
  • list_components open 49m ago

    Lists every Nasaq web component with its category, status, one-line summary and exports. Filter by category or a text query. With a non-React `framework`, lists only the components that exist in that stack.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "query": {
      "type": "string",
      "description": "Free-text filter, e.g. 'table' or 'menu'"
    },
    "category": {
      "enum": [
        "account",
        "actions",
        "admin",
        "ai",
        "ai-agents",
        "alerts",
        "analytics",
        "auth",
        "billing",
        "bookings",
        "brand",
        "charts",
        "chat",
        "collaboration",
        "crm",
        "data-display",
        "delivery",
        "developer-tools",
        "editors",
        "feedback",
        "feedback-sdk",
        "files",
        "form-builders",
        "forms",
        "gamification",
        "healthcare",
        "integrations",
        "keyboard",
        "layout",
        "marketing",
        "monitoring",
        "navigation",
        "onboarding",
        "overlays",
        "pickers",
        "platforms",
        "pricing",
        "productivity",
        "security",
        "seo",
        "server-tools",
        "store",
        "store-admin",
        "typography",
        "utilities",
        "website",
        "wellness",
        "work",
        "workflow"
      ],
      "type": "string",
      "description": "Only this category"
    },
    "framework": {
      "enum": [
        "react",
        "shadcn",
        "inertia",
        "inertia-vue",
        "html",
        "alpine",
        "vue",
        "nuxt",
        "blade",
        "livewire",
        "filament",
        "laravel",
        "tomatophp"
      ],
      "type": "string",
      "description": "Default react (@fadymondy/nasaq/web). shadcn: the same React components copied by the shadcn CLI. inertia / inertia-vue: Laravel + Inertia. vue / nuxt / inertia-vue: Vue 3. blade / livewire / filament / laravel / tomatophp: Laravel Blade components. html / alpine: rendered HTML run by Alpine."
    }
  }
}
    arguments 84 lines
  • search_components unknown never probed

    Ranks components for a need described in words, e.g. 'switch between products', 'empty state', 'keyboard shortcut'.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 30,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "minLength": 1
    }
  }
}
    arguments 18 lines
  • get_component unknown never probed

    Returns one component's details and manual. `name` may be the folder (app-shell), the title (AppShell) or any export (SidebarItem). `include` picks what to return: readme (default, full manual), api (API section only), examples, source (TSX), story (Storybook CSF), all. `framework` returns the component in another stack (html, alpine, vue, blade, livewire, filament, inertia, shadcn, …).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1
    },
    "include": {
      "type": "array",
      "items": {
        "enum": [
          "readme",
          "api",
          "examples",
          "source",
          "story",
          "all"
        ],
        "type": "string"
      },
      "description": "Default: ['readme']"
    },
    "framework": {
      "enum": [
        "react",
        "shadcn",
        "inertia",
        "inertia-vue",
        "html",
        "alpine",
        "vue",
        "nuxt",
        "blade",
        "livewire",
        "filament",
        "laravel",
        "tomatophp"
      ],
      "type": "string",
      "description": "Default react (@fadymondy/nasaq/web). shadcn: the same React components copied by the shadcn CLI. inertia / inertia-vue: Laravel + Inertia. vue / nuxt / inertia-vue: Vue 3. blade / livewire / filament / laravel / tomatophp: Laravel Blade components. html / alpine: rendered HTML run by Alpine."
    }
  }
}
    arguments 47 lines
  • get_setup unknown never probed

    Install command, CSS imports, provider and the usual app skeleton. Call once before building UI. `framework` picks the guide: react (default), shadcn, inertia, html, alpine, vue, or blade/livewire/filament/laravel/tomatophp.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "framework": {
      "enum": [
        "react",
        "shadcn",
        "inertia",
        "inertia-vue",
        "html",
        "alpine",
        "vue",
        "nuxt",
        "blade",
        "livewire",
        "filament",
        "laravel",
        "tomatophp"
      ],
      "type": "string",
      "description": "Default react (@fadymondy/nasaq/web). shadcn: the same React components copied by the shadcn CLI. inertia / inertia-vue: Laravel + Inertia. vue / nuxt / inertia-vue: Vue 3. blade / livewire / filament / laravel / tomatophp: Laravel Blade components. html / alpine: rendered HTML run by Alpine."
    }
  }
}
    arguments 25 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 583601b1a1746f0e.

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