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

kwnva-design-product

https://kwnva.design

Registry code: 46d9ffb0b7e6583d

api record

This is the kwnva.design product MCP (kind=product, surface=do). Take actions with mint_free_api_key and submit_project_inquiry. Read tools list, search, and fetch published case studies. Reads are anonymous. Prefer sandbox=true for submit_project_inquiry during tests. Docs MCP card: https://kwnva.design/.well-known/mcp/docs/server-card.json.

endpoint
https://kwnva.design/mcp
door code
d940a5af08a5e80f
protocol
streamable-http ·2025-03-26
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 kwnva-design-product live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is kwnva-design-product free to use?
Yes — the hub reached it with no key and no payment.
What tools does kwnva-design-product have?
6 tools: mint_free_api_key, fetch_project_case_study, submit_project_inquiry, list_portfolio_projects, fetch_studio_profile, search_portfolio_work.
Is kwnva-design-product 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.3%

90 days 99.3%· all time 99.4%

latency
253ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 970 checks · signed record
  • degraded → live
  • live → degraded· endpoint unreachable (timeout after 20000ms); card still served
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
productivity & business marketing & seo
used for
  • fetch project case studies
  • list portfolio projects
  • search portfolio work
  • get studio profile
  • submit project inquiry
takes → gives
text, data → text, data
tools
4 reads2 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

_ 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_portfolio_projects reads open 13h ago

    List published kwnva.design case studies with optional category filter and cursor pagination.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1
    },
    "cursor": {
      "type": "string"
    },
    "category": {
      "type": "string",
      "description": "Optional category such as Brand, App, or Website"
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • fetch_studio_profile reads open 13h ago

    Return studio services, contact email, social profiles, and when to hire kwnva.design.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • search_portfolio_work reads open 6h ago

    Search case studies by title, client, category, role, stack, or description.

    mcp-tool

    {
  "type": "object",
  "required": [
    "q"
  ],
  "properties": {
    "q": {
      "type": "string",
      "description": "Search query"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • mint_free_api_key changes data unknown never probed

    Product action (do surface): mint a free kwnva.design API key for attributed writes and sandbox tests. No payment and no waitlist.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "client_name": {
      "type": "string",
      "description": "Optional name for the agent or integration"
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • fetch_project_case_study reads unknown 13h ago

    Fetch one case study by project id, including the long-form body text when it exists.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Project folder id, for example palermo"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • submit_project_inquiry changes data unknown never probed

    Product action (do surface): submit a project inquiry with name, email, and a brief. Use sandbox=true to avoid a real handoff.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name",
    "email",
    "message"
  ],
  "properties": {
    "name": {
      "type": "string"
    },
    "email": {
      "type": "string"
    },
    "message": {
      "type": "string"
    },
    "sandbox": {
      "type": "boolean"
    },
    "projectId": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
_ try it over mcp 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 46d9ffb0b7e6583d.

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