SERVICE CARD / tapcard-mcp

TapCard MCP

A self-hosted NFC and QR business card with a private AI card wall — public page on tap, received cards stored in your own account

DECIDE FIRST

What is this project

A self-hosted NFC/QR business card and private card-wall MCP

What problem does it solve

Paper cards become outdated, while public profile sharing and received contacts lack one controlled entry point

Who it is for

  • Consultants, sales professionals and freelancers
  • Small teams that need public profiles and private contact storage

What it can do

  • Publish an NFC/QR public business card
  • Share a public profile and download vCards
  • Preview, confirm, import, search and export private cards

Before you deploy

  • Your own Workers, D1, R2 and KV
  • The deployer manages the admin credential and private MCP keys

What to know first

  • Vector search, multi-user teams and an NFC-writing app are not in the current scope
  • URL import is limited to public TapCards that meet the contract

WHAT HAS BEEN CHECKED

Discovered1 EVIDENCESPEC 0.3.02026-08-03
Public evidence, scoped to this version and date.

How it runs

TapCard MCP verified service screenshot
Screenshot referenced by the published Evidence Pack
TapCard MCP 架構與資料流（依部署契約機械生成）使用者WorkerD1 資料庫R2 物件儲存KV 儲存使用者指定端點
Architecture generated from the Service Card data flow.

Where it runs and what it touches

Upstream
ai-cooperation/tapcard-mcp
License
Apache-2.0
Profile
small-app
External services
(user-directed)
Data flow
NFC and QR profile pages are public; received contacts, thumbnails and MCP keys stay private in your own D1, R2 and KV

Source evidence

← Back to service index