mcp server
Lineup
Turn one sentence into an event pack: event card, identity badges, QR codes, and .ics.
Description as published by the maintainer. Source
- version 0.0.1
- active
active — Registry entry last updated 2026-05-28.
What this server can do
2 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
generate-lineup(title, venue, dateISO, rsvpUrl, accentHex, attendees, avatarStyle, durationHours)- Generate an event pack: a Luma-style event card with .ics + RSVP QR, and an identity badge per attendee with a deterministic avatar and vCard-encoded QR. Use when the user describes an event and the people attending (meetup, conference, wedding, hackathon, dinner) and wants shareable cards. Do NOT use to render a single downloadable PNG of one badge — use render-badge-png for that. Output is deterministic: the same attendee name + style always yields the same avatar. Required: title, dateISO, attendees.
render-badge-png(name, role, seed, gender, accentHex, eventTitle, avatarStyle)- Render a single identity badge as a shareable PNG (avatar + name + role + vCard QR) composed with Satori. Use when the user clicks download on one badge, or asks for a single saveable/printable badge image. Do NOT use to build the whole event view — use generate-lineup for that. Match avatarStyle/gender/accentHex to the badge shown in the Lineup so the PNG looks identical. Required: name.
Last successful function declaration observed on . Source: https://lineup-bf157e35.alpic.live. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://lineup-bf157e35.alpic.live.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.0.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-05-28 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-05-28 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 2 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | lineup-bf157e35.alpic.live | |
| mcp endpoint status | ok | The server listed 2 functions when asked. | as of probe | lineup-bf157e35.alpic.live |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json