_ registry / mcp http-sse · checked 21m ago

Drawcall

https://mcp.drawcall.ai

Registry code: baaf902fb9c13424

api record

Drawcall command-line tools find and generate assets; its libraries integrate them into interactive 3D apps. Use search_skills to discover the relevant workflow, then read its guides and API declarations before choosing an implementation. Search works across the supported ecosystem without package selection or an existing project.

endpoint
https://mcp.drawcall.ai/
protocol
http-sse ·2025-06-18
authentication
bearer
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 Drawcall live?
Yes — it answered the hub's last check (checked 21m ago). It answered 99% of checks over the last 30 days.
Is Drawcall free to use?
Yes — the hub reached it with no key and no payment.
What tools does Drawcall have?
3 tools: approve_login, read_skills, search_skills.
Is Drawcall 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.5%· all time 99.5%

latency
362ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 409 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
  • create and edit 3d content
  • find 3d assets
  • generate 3d assets
takes → gives
text → 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

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

  • approve_login unknown never probed

    Approve a pending Drawcall CLI login as your connected account. This grants the CLI a full account session. Only approve the user_code printed by the user's current drawcall auth login command. After approval, run drawcall auth complete in that CLI.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "user_code"
      ],
      "properties": {
        "user_code": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • read_skills unknown 21m ago

    Read a guide for its workflow and prerequisites, or a declaration for API details. When the workflow needs user action, give the documented command or URL as the next step. A package path lists its skills and declaration sources; a SKILL.md gives its full guide. Paths come from search results and read_skills listings; listing names are relative to the path that was read.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "path"
      ],
      "properties": {
        "path": {
          "type": "string",
          "minLength": 1,
          "description": "A path from search or a listing, e.g. /@drawcall/physics/"
        }
      }
    }
    arguments 14 lines
  • search_skills unknown 21m ago

    Search Drawcall workflows and APIs for apps, games and assets. Discover asset sourcing as well as runtime libraries. Source visual content from @drawcall/market first. When its candidates do not fit, consult @drawcall/generate for generation options and prerequisites before settling on a fallback. Reserve hand-authored geometry for gameplay structure or explicitly procedural content. @drawcall/rig adds skeletons and skin weights when needed. This searches documentation, not Market inventory: read the guides to find and inspect actual assets. Search covers all supported packages automatically, including in an empty project. Returns up to five paths with excerpts; read_skills provides the full workflows and APIs.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "What you want to implement or learn how to do"
        }
      },
      "additionalProperties": false
    }
    arguments 16 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 baaf902fb9c13424.

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