GitHubCard
REMOTE · GITHUBCARD.COM · 2 COMPONENTS
Create GitHub profile and repository cards for READMEs, link previews and social posts.
Available components
Last scanned (9 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Design and Media
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_card). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1471 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.1.0 → 0.2.0 functional
- 31 Oct 26 66
First indexed and scored.
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 · Probed https://githubcard.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=githubcard.com | CN=WE1,O=Google Trust Services,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 2f4f175f1e3c4cfd13529b26e346c559 |
| SANs: githubcard.com, email.githubcard.com, *.email.githubcard.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of githubcard.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| githubcard.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=0; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://githubcard.com/mcp | Verified | 200 | |
| http (plaintext) | http://githubcard.com/mcp | HTTPS enforced | 301 | https://githubcard.com/mcp |
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 →
create_card Create GitHub 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.
| Name | Type | Req | Description |
|---|---|---|---|
| design | object | – | a design document from get_template_design or get_card_design, possibly edited; replaces template and palette |
| format | string | – | which link to return as url: "svg" (default; best for README embeds) or "png". Both are always in urls |
| palette | string | – | background palette id from list_palettes; omit for the template's own background. For any other colour use design |
| subject | string | yes | GitHub username (e.g. octocat) or owner/repo (e.g. octocat/hello-world) |
| template | string | – | template id from list_templates; omit for the subject's default layout |
| watermark | boolean | – | false removes the watermark (Pro only; ignored on Free) |
No output schema declared.
No examples provided.
delete_card Delete a card ~48
Permanently delete one of the account's cards. Its links stop working everywhere they are embedded. Confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | card id from create_card or list_cards |
No output schema declared.
No examples provided.
get_card_design Get a card's 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).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | card id from create_card or list_cards |
No output schema declared.
No examples provided.
get_template_design Get a template's 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.
| Name | Type | Req | Description |
|---|---|---|---|
| palette | string | – | palette id to apply; replaces the template's background in the returned design |
| subject | string | – | username or owner/repo the card is for; decides profile vs repo layouts |
| template | string | yes | template id from list_templates |
No output schema declared.
No examples provided.
get_usage Get plan and quota ~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 List my cards ~58
List cards this account created through the API, most recently requested first. Paginated with nextCursor.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | nextCursor from a previous call |
| limit | integer | – | page size 1-100 (default 20) |
No output schema declared.
No examples provided.
list_components List widget types ~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 List background 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 List card templates ~92
List card layouts with their ids, scope (profile/repo/all), size, widget types, and whether they need Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| freeOnly | boolean | – | only templates available on the Free plan |
| scope | string | – | profile or repo; omit for all. Results include scope=all templates, which fit both |
| widgets | array | – | only templates containing all of these widget types (from list_components) |
No output schema declared.
No examples provided.
validate_card Check a card request ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| design | object | – | a design document from get_template_design or get_card_design, possibly edited; replaces template and palette |
| format | string | – | which link to return as url: "svg" (default; best for README embeds) or "png". Both are always in urls |
| palette | string | – | background palette id from list_palettes; omit for the template's own background. For any other colour use design |
| subject | string | yes | GitHub username (e.g. octocat) or owner/repo (e.g. octocat/hello-world) |
| template | string | – | template id from list_templates; omit for the subject's default layout |
| watermark | boolean | – | false removes the watermark (Pro only; ignored on Free) |
No output schema declared.
No examples provided.
How do I install the GitHubCard MCP server?
GitHubCard is a hosted endpoint at https://githubcard.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · githubcard.com
claude mcp add --transport http com-githubcard-mcp 'https://githubcard.com/mcp'
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 hosted endpoint (https://githubcard.com/mcp).
Is the GitHubCard MCP server safe to use?
GitHubCard scores 68 out of 100 on VerifyMCP. 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.
Does the GitHubCard MCP server require authentication?
No. We connected to GitHubCard without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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.