Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

GitHubCard

NPM · @GHCARDHQ/GHCARD · 2 COMPONENTS

Create GitHub profile and repository cards for READMEs, link previews and social posts.

71 Trust /100

Last scanned (9 hours ago)

Scores higher than 41% of npm servers

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale. View diagnostics → Unverified
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1476 tokens (~147/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +15
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 31 Oct 26 54

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@ghcardhq/ghcard@0.2.1

Provenance Repository mismatch

The attestation is cryptographically sound but binds a different repository to the one the registry declares. Most often the declared URL is simply stale.

Result Repository mismatch
Ecosystem npm
Reason Repository mismatch
Discovered via Registry attestation endpoint
Source repo ghcardhq/ghcard
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ghcardhq/ghcard/.github/workflows/release.yml@refs/tags/v0.2.1
Rekor log index 3629743442
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:604f8a8d26aea29f03bca55dc6f69403b5c16c1391a093f80dd1e95e4aa6e4fc653f1c3b55ab4dbf5c2451beebf9e13aa636f7401bb09595ac18f4c2d

Background: How many MCP packages publish verified provenance →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~866 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_card ~203

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.

NameTypeReqDescription
designobject–a design document from get_template_design or get_card_design, possibly edited; replaces template and palette
formatstring–which link to return as url: "svg" (default; best for README embeds) or "png". Both are always in urls
palettestring–background palette id from list_palettes; omit for the template's own background. For any other colour use design
subjectstringyesGitHub username (e.g. octocat) or owner/repo (e.g. octocat/hello-world)
templatestring–template id from list_templates; omit for the subject's default layout
watermarkboolean–false removes the watermark (Pro only; ignored on Free)

No output schema declared.

No examples provided.

delete_card ~48

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

NameTypeReqDescription
idstringyescard id from create_card or list_cards

No output schema declared.

No examples provided.

get_card_design ~58

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

NameTypeReqDescription
idstringyescard id from create_card or list_cards

No output schema declared.

No examples provided.

get_template_design ~95

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.

NameTypeReqDescription
palettestring–palette id to apply; replaces the template's background in the returned design
subjectstring–username or owner/repo the card is for; decides profile vs repo layouts
templatestringyestemplate id from list_templates

No output schema declared.

No examples provided.

get_usage ~47

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_cards ~58

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

NameTypeReqDescription
cursorstring–nextCursor from a previous call
limitinteger–page size 1-100 (default 20)

No output schema declared.

No examples provided.

list_components ~31

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_palettes ~18

List background palette ids accepted by create_card.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_templates ~92

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

NameTypeReqDescription
freeOnlyboolean–only templates available on the Free plan
scopestring–profile or repo; omit for all. Results include scope=all templates, which fit both
widgetsarray–only templates containing all of these widget types (from list_components)

No output schema declared.

No examples provided.

validate_card ~216

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.

NameTypeReqDescription
designobject–a design document from get_template_design or get_card_design, possibly edited; replaces template and palette
formatstring–which link to return as url: "svg" (default; best for README embeds) or "png". Both are always in urls
palettestring–background palette id from list_palettes; omit for the template's own background. For any other colour use design
subjectstringyesGitHub username (e.g. octocat) or owner/repo (e.g. octocat/hello-world)
templatestring–template id from list_templates; omit for the subject's default layout
watermarkboolean–false removes the watermark (Pro only; ignored on Free)

No output schema declared.

No examples provided.

Install

How do I install the GitHubCard MCP server?

GitHubCard runs locally as an npm package, launched with npx -y @ghcardhq/ghcard. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @ghcardhq/ghcard

# add to Claude Code
claude mcp add com-githubcard-mcp -- npx -y @ghcardhq/ghcard
Common questions

What is the GitHubCard MCP server?

GitHubCard is an MCP server listed in the public MCP registry as com.githubcard/mcp. Create GitHub profile and repository cards for READMEs, link previews and social posts. This page covers its npm package (@ghcardhq/ghcard).

Is the GitHubCard MCP server safe to use?

GitHubCard scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the GitHubCard MCP server expose?

GitHubCard exposes 10 tools: create_card, validate_card, list_templates, list_palettes, list_components, and 5 more. Their descriptions and schemas cost roughly 866 tokens of context every time the server is loaded.

Is the GitHubCard MCP server still maintained?

GitHubCard is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the GitHubCard MCP server under?

GitHubCard declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.