mcp.termcard.dev
https://mcp.termcard.dev/
active Production-safe Score 98/100 http no auth
At a glance
| Endpoint | https://mcp.termcard.dev/ |
|---|---|
| Source | https://termcard.dev/ |
| Transport | http |
| Tools | 7 |
| Auth | none |
| First seen | 2026-11-11 12:58:40 |
| Last checked | 2026-11-17 21:46:12 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 172 / 378 ms |
| Last successful check | 2026-11-17 21:46:12 |
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:46:12 | ✓ | ✓ | 424 ms | 91 | active |
| 2026-11-17 21:31:07 | ✓ | ✓ | 138 ms | 94 | active |
| 2026-11-17 21:15:55 | ✓ | ✓ | 317 ms | 91 | active |
| 2026-11-17 21:00:40 | ✓ | ✓ | 446 ms | 91 | active |
| 2026-11-17 20:45:38 | ✓ | ✓ | 153 ms | 94 | active |
| 2026-11-17 20:30:36 | ✓ | ✓ | 153 ms | 94 | active |
| 2026-11-17 20:15:30 | ✓ | ✓ | 331 ms | 91 | active |
| 2026-11-17 19:59:23 | ✓ | ✓ | 146 ms | 94 | active |
| 2026-11-17 19:44:17 | ✓ | ✓ | 447 ms | 91 | active |
| 2026-11-17 19:29:15 | ✓ | ✓ | 161 ms | 95 | active |
| 2026-11-17 19:14:13 | ✓ | ✓ | 271 ms | 94 | active |
| 2026-11-17 18:58:28 | ✓ | ✓ | 139 ms | 94 | active |
| 2026-11-17 18:43:26 | ✓ | ✓ | 150 ms | 94 | active |
| 2026-11-17 18:28:24 | ✓ | ✓ | 325 ms | 91 | active |
| 2026-11-17 18:13:23 | ✓ | ✓ | 158 ms | 94 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://mcp.termcard.dev/") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/mcp-termcard-dev # JSON