Interactive business cards for the terminal — npx yourname. Create yours with on
Interactive business cards for the terminal — npx yourname. Create yours with one command or by chatting with Claude. 14 languages, seasonal themes, MCP server, zero dependencies.
active Production-safe Score 97/100 http no auth
At a glance
| Endpoint | https://mcp.termcard.dev/mcp |
|---|---|
| Source | https://github.com/aepasahan/termcard |
| Transport | http |
| Tools | 7 |
| Auth | none |
| First seen | 2026-11-10 22:10:59 |
| Last checked | 2026-11-17 21:45:22 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 195 / 406 ms |
| Last successful check | 2026-11-17 21:45:22 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (7)
get_card— Returns a person's Termcard business card: name, role, description, location, email, phone, website and profile links.get_vcard— Returns the person's contact details as a vCard 3.0 text that can be saved to an address book.compose_email— 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.list_card_options— Explains what a Termcard card can contain — fields, limits, templates, color themes, icon sets, languages and menu items — with an example cpreview_card— 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 scheck_name— 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.export_card_config— Returns the finished card.config.json for the user to save, with the commands that turn it into a published card. Use it where files cannot
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:45:22 | ✓ | ✓ | 434 ms | 91 | active |
| 2026-11-17 21:30:15 | ✓ | ✓ | 146 ms | 94 | active |
| 2026-11-17 21:14:56 | ✓ | ✓ | 161 ms | 94 | active |
| 2026-11-17 20:59:40 | ✓ | ✓ | 132 ms | 94 | active |
| 2026-11-17 20:44:38 | ✓ | ✓ | 155 ms | 94 | active |
| 2026-11-17 20:29:37 | ✓ | ✓ | 213 ms | 94 | active |
| 2026-11-17 20:14:33 | ✓ | ✓ | 346 ms | 91 | active |
| 2026-11-17 19:58:34 | ✓ | ✓ | 169 ms | 94 | active |
| 2026-11-17 19:43:26 | ✓ | ✓ | 217 ms | 94 | active |
| 2026-11-17 19:28:22 | ✓ | ✓ | 343 ms | 91 | active |
| 2026-11-17 19:13:20 | ✓ | ✓ | 409 ms | 91 | active |
| 2026-11-17 18:56:00 | ✓ | ✓ | 452 ms | 91 | active |
| 2026-11-17 18:40:53 | ✓ | ✓ | 424 ms | 91 | active |
| 2026-11-17 18:25:45 | ✓ | ✓ | 151 ms | 94 | active |
| 2026-11-17 18:10:30 | ✓ | ✓ | 176 ms | 94 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://mcp.termcard.dev/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/mcp-termcard-dev-mcp # JSON