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.

Termcard

NPM · TERMCARD · 2 COMPONENTS

Create terminal business cards (npx <name>) in a chat, or look up anyone's card.

+3 this week 89 Trust /100

Last scanned (14 hours ago)

Scores higher than 83% of npm servers

Category Productivity and Notes

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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to aepasahan/termcard). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 9 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 735 tokens (~105/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 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
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

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

  • 14 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.

  • 12 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 11 Nov 26 0
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.7.0 → 1.0.0 functional
  • 10 Nov 26 −3
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
    • Package version: 0.6.1 → 0.7.0 functional
    • Package version: 0.6.1 → 0.6.2 functional
  • 9 Nov 26 72

    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 21 Nov 2026 · Analysed npm/termcard@1.0.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo aepasahan/termcard
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/aepasahan/termcard/.github/workflows/release.yml@refs/heads/main
Rekor log index 3817143670
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:bb3f7d68b9ad1f8398ad418451180532468b0c3c72c29f47d0c374ab51d6929bcd6c217c391878fdf17e1a35e7f0f48b3f9f415dd9ee40f968d72cef2

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~582 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
check_name ~60

Checks whether a name can be used as the card's npm package (people will run `npx <name>`) and whether it is still free on npm.

NameTypeReqDescription
namestringyesProposed npm package name, e.g. "janedoe".

No output schema declared.

No examples provided.

compose_email ~99

Prepares an email to the card's owner and returns a mailto: link for the user to open, review and send. Nothing is sent automatically.

NameTypeReqDescription
bodystringyesMessage text (max 4000 characters).
namestringyesnpm package name of the card, as in `npx <name>` (e.g. "aepasahan").
subjectstringyesSubject line (max 200 characters).

No output schema declared.

No examples provided.

create_card_project ~131

Writes a ready-to-publish card package (card.config.json, package.json, README, license) into a new, empty folder on the user's computer. It never overwrites files and never publishes. Ask the user to confirm the details, the name and the folder first.

NameTypeReqDescription
configobjectyesThe card configuration (card.config.json). Call list_card_options for the fields.
directorystring–Absolute path (or ~/…) of a new or empty folder. Defaults to ~/termcard-cards/<name>.
packageNamestringyesnpm package name, checked with check_name.

No output schema declared.

No examples provided.

get_card ~82

Returns a person's Termcard business card: name, role, description, location, email, phone, website and profile links.

NameTypeReqDescription
languagestring–Optional language code such as "en" or "tr".
namestringyesnpm package name of the card, as in `npx <name>` (e.g. "aepasahan").

No output schema declared.

No examples provided.

get_vcard ~81

Returns the person's contact details as a vCard 3.0 text that can be saved to an address book.

NameTypeReqDescription
languagestring–Optional language code such as "en" or "tr".
namestringyesnpm package name of the card, as in `npx <name>` (e.g. "aepasahan").

No output schema declared.

No examples provided.

list_card_options ~48

Explains what a Termcard card can contain — fields, limits, templates, color themes, icon sets, languages and menu items — with an example config. Call this before drafting a card.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

preview_card ~81

Validates a card config and returns a text preview of the card and its menu, or the list of problems to fix. Use it after every change and show the preview to the user.

NameTypeReqDescription
configobjectyesThe card configuration (card.config.json). Call list_card_options for the fields.
languagestring–Optional language code for the preview.

No output schema declared.

No examples provided.

Install

How do I install the Termcard MCP server?

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

npm · termcard

# add to Claude Code
claude mcp add aepasahan-termcard -- npx -y termcard mcp
Common questions

What is the Termcard MCP server?

Termcard is an MCP server listed in the public MCP registry as io.github.aepasahan/termcard. Create terminal business cards (npx <name>) in a chat, or look up anyone's card. This page covers its npm package (termcard).

Is the Termcard MCP server safe to use?

Termcard scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Termcard MCP server expose?

Termcard exposes 7 tools: get_card, get_vcard, compose_email, list_card_options, preview_card, and 2 more. Their descriptions and schemas cost roughly 582 tokens of context every time the server is loaded.

Is the Termcard MCP server still maintained?

Termcard is still listed as active in the MCP registry. We last reached this channel on 21 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 Termcard MCP server under?

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

What did VerifyMCP test on the Termcard MCP server?

VerifyMCP ran 16 checks on Termcard, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.