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

githubcard

https://githubcard.com

Registry code: 3037dcc528fa346c

api record

GitHubCard turns a GitHub user or repository into an embeddable card image.

Typical flow:

endpoint
https://githubcard.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 githubcard live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is githubcard free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does githubcard have?
10 tools: create_card, validate_card, list_templates, list_palettes, get_template_design, get_card_design, delete_card, list_components, ….
Is githubcard 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
346ms

last good check

priced tools
0

of 10 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 10 tools
1 open2 auth-required 7 never probed 3 of 10 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 open 2h ago

    List the widget (layer) types a design can contain, with the scope (profile/repo) each fits.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_usage auth-required 2h ago

    Show the account's plan (free/pro) and how many cards it can still create today (cards.remaining, resets 00:00 UTC). The ai quota is reserved for future AI tools.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • list_cards auth-required 2h ago

    List cards this account created through the API, most recently requested first. Paginated with nextCursor.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": -9007199254740991,
          "description": "page size 1-100 (default 20)"
        },
        "cursor": {
          "type": "string",
          "description": "nextCursor from a previous call"
        }
      }
    }
    arguments 16 lines
  • create_card unknown never probed

    Create (or reuse) a published card image for a GitHub profile or repository. Returns svg/png URLs and markdown/html embed snippets. Idempotent; counts once against the daily quota.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "subject"
      ],
      "properties": {
        "design": {
          "type": "object",
          "description": "a design document from get_template_design or get_card_design, possibly edited; replaces template and palette",
          "propertyNames": {
            "type": "string"
          },
          "additionalProperties": {}
        },
        "format": {
          "type": "string",
          "description": "which link to return as url: \"svg\" (default; best for README embeds) or \"png\". Both are always in urls"
        },
        "palette": {
          "type": "string",
          "description": "background palette id from list_palettes; omit for the template's own background. For any other colour use design"
        },
        "subject": {
          "type": "string",
          "description": "GitHub username (e.g. octocat) or owner/repo (e.g. octocat/hello-world)"
        },
        "template": {
          "type": "string",
          "description": "template id from list_templates; omit for the subject's default layout"
        },
        "watermark": {
          "type": "boolean",
          "description": "false removes the watermark (Pro only; ignored on Free)"
        }
      }
    }
    arguments 37 lines
  • validate_card unknown never probed

    Dry run of create_card with the same inputs: checks template/palette ids, Pro features and the design document, without creating anything or using quota. warnings lists layers that reach outside the artboard (they would be clipped); fix those before create_card.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "subject"
      ],
      "properties": {
        "design": {
          "type": "object",
          "description": "a design document from get_template_design or get_card_design, possibly edited; replaces template and palette",
          "propertyNames": {
            "type": "string"
          },
          "additionalProperties": {}
        },
        "format": {
          "type": "string",
          "description": "which link to return as url: \"svg\" (default; best for README embeds) or \"png\". Both are always in urls"
        },
        "palette": {
          "type": "string",
          "description": "background palette id from list_palettes; omit for the template's own background. For any other colour use design"
        },
        "subject": {
          "type": "string",
          "description": "GitHub username (e.g. octocat) or owner/repo (e.g. octocat/hello-world)"
        },
        "template": {
          "type": "string",
          "description": "template id from list_templates; omit for the subject's default layout"
        },
        "watermark": {
          "type": "boolean",
          "description": "false removes the watermark (Pro only; ignored on Free)"
        }
      }
    }
    arguments 37 lines
  • list_templates unknown never probed

    List card layouts with their ids, scope (profile/repo/all), size, widget types, and whether they need Pro.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "scope": {
          "type": "string",
          "description": "profile or repo; omit for all. Results include scope=all templates, which fit both"
        },
        "widgets": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "only templates containing all of these widget types (from list_components)"
        },
        "freeOnly": {
          "type": "boolean",
          "description": "only templates available on the Free plan"
        }
      }
    }
    arguments 21 lines
  • list_palettes unknown never probed

    List background palette ids accepted by create_card.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_template_design unknown never probed

    Return a template's layout as an editable design document (artboard + layers). Costs no quota. Edit it and pass it to create_card as design.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "template"
      ],
      "properties": {
        "palette": {
          "type": "string",
          "description": "palette id to apply; replaces the template's background in the returned design"
        },
        "subject": {
          "type": "string",
          "description": "username or owner/repo the card is for; decides profile vs repo layouts"
        },
        "template": {
          "type": "string",
          "description": "template id from list_templates"
        }
      }
    }
    arguments 21 lines
  • get_card_design unknown never probed

    Return the design document of one of the account's cards, to edit and re-submit through create_card as design (which creates a new card; the original is unchanged).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "card id from create_card or list_cards"
        }
      }
    }
    arguments 13 lines
  • delete_card unknown never probed

    Permanently delete one of the account's cards. Its links stop working everywhere they are embedded. Confirm with the user first.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "card id from create_card or list_cards"
        }
      }
    }
    arguments 13 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 3037dcc528fa346c.

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