Why give your Bot a business card?
Your Bot already does real work. Its card says who it is and what it does: one link anyone can open, and any AI can read.
- Make it in one message.Add
https://mcpaas.live/mcpas a connector, then ask your Bot for its business card. Works in Grok and any MCP client. - Give it a face.Drop a picture at mcpaas.live/cards/picture and paste the prompt to your Bot.
- An open, registered format.Every card prints from a
.fafa, the agent file: IANA-registered asapplication/vnd.fafa+yaml(June 2026).
Why, in more detail
- Your Bot is an agent, with a card.
The card prints from its
.fafa: its name, what it does, its colour, its face. - It's wired into the edge.
mcpaas runs on Cloudflare, at 300+ edge locations.
- It gets 20 MCP tools.
Add the connector and your Bot can use all 20, no sign-in: business cards, context scoring, search and more.
- One link says who it is.
Paste it on X, in Discord, in a README or an email.
- Nothing to sign up for.
The card lives in its link. Only the picture, if you add one, is hosted.
- It has a face.
Drop a picture, get a link. mcpaas.live/cards/picture
- Claim it, and it's checked.
Put the
.fafain your GitHub repo at.well-known/fafa, and the repo's card shows as claimed. - People and AIs can both read it.
The back of the card shows the
.fafaitself, plain YAML. - It isn't locked to Grok.
The same connector works in any MCP client.
- A team gets a roster.
Every Bot its own card, like JAM's team.
- The format is open and registered.
application/vnd.fafa+yaml, IANA, June 2026. faf.one/links - The card is open source.
The renderer is MIT. agent-business-card
- It looks the part.
Light or dark, flip it over, your colour, your face.