Skip to content
GitHubCard logo

GitHubCard MCP server

Which MCP servers are GitHubCard's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-31

← Back to GitHubCard

Whose server it is
  • Registry namecom.githubcard/mcpverified in the MCP registry

The registry name sits under githubcard.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-31
  • Stateanswerschecked 2026-10-31
  • Tools10
  • Server calls itselfgithubcard
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-31 the server answered initialize and tools/list without a sign-in. First answer in 73 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: embed a live repository card in a README; export a profile card as SVG or PNG.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "embed a live repository card in a README", the likely first call is create_card.
  • For "export a profile card as SVG or PNG", the likely first call is create_card.
  • create_card, delete_card change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-31
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it2 of 2 use cases
  • Use13 GitHub stars
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer354 ms
  • Space in an agent's context≈ 1,378 tokensthe definitions of all its tools (10), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 10 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • not sure · combine GitHub stats and contribution heatmaps into one card
  • can do · embed a live repository card in a README
  • can do · export a profile card as SVG or PNG

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: create_card, delete_card

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers10 tools · read 2026-10-31
  • create_card

    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.

  • validate_card

    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…

  • list_templates

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

  • list_palettes

    List background palette ids accepted by create_card.

  • list_components

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

  • get_template_design

    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.

  • get_card_design

    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).

  • list_cards

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

  • delete_card

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

  • get_usage

    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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "githubcard": {
      "type": "http",
      "url": "https://githubcard.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http githubcard https://githubcard.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://githubcard.com/mcp as a custom connector in the settings.

Also shipped through: npm

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.