Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Lineup

REMOTE · LINEUP-BF157E35.ALPIC.LIVE

Turn one sentence into an event pack: event card, identity badges, QR codes, and .ics.

+62 this week 85 Trust /100

Last scanned (8 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability74
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 541 tokens (~135/item across 4 items; 2 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 0
    • Resource “generate-lineup” now points somewhere else: ui://views/apps-sdk/generate-lineup.html?v=1fb13dbd → ui://views/ext-apps/generate-lineup.html?v=1fb13dbd security
  • 4 Nov 26 0
    • Resource “generate-lineup” now points somewhere else: ui://views/apps-sdk/generate-lineup.html?v=1fb13dbd → ui://views/ext-apps/generate-lineup.html?v=1fb13dbd security
  • 3 Nov 26 0
    • Resource “generate-lineup” now points somewhere else: ui://views/apps-sdk/generate-lineup.html?v=1fb13dbd → ui://views/ext-apps/generate-lineup.html?v=1fb13dbd security
  • 2 Nov 26 0
    • Resource “generate-lineup” now points somewhere else: ui://views/apps-sdk/generate-lineup.html?v=1fb13dbd → ui://views/ext-apps/generate-lineup.html?v=1fb13dbd security
  • 1 Nov 26 +62
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Resource “generate-lineup” now points somewhere else: ui://views/apps-sdk/generate-lineup.html?v=1fb13dbd → ui://views/ext-apps/generate-lineup.html?v=1fb13dbd security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 14 Oct 26 −62
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 13 Oct 26 0
    • Resource “generate-lineup” now points somewhere else: ui://views/apps-sdk/generate-lineup.html?v=1fb13dbd → ui://views/ext-apps/generate-lineup.html?v=1fb13dbd security
  • 12 Oct 26 0
    • Resource “generate-lineup” now points somewhere else: ui://views/apps-sdk/generate-lineup.html?v=1fb13dbd → ui://views/ext-apps/generate-lineup.html?v=1fb13dbd security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://lineup-bf157e35.alpic.live

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.alpic.live CN=Amazon RSA 2048 M04,O=Amazon,C=US 23 Sept 2026 8 Apr 2027 RSA 2048 SHA256-RSA 41ca0c3068063f7c713f936a81919aa
SANs: *.alpic.live
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of lineup-bf157e35.alpic.live. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
live. present 4724, 36322 8, 8 Verified
alpic.live. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 3 probes
Transport URL Outcome Status Location
streamable-http https://lineup-bf157e35.alpic.live Verified 200
sse https://lineup-bf157e35.alpic.live Verified 200
http (plaintext) http://lineup-bf157e35.alpic.live HTTPS enforced 301 https://lineup-bf157e35.alpic.live/
MCP tools · 2 exposed · ~515 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
generate-lineup ~304

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.

NameTypeReqDescription
accentHexstring–Hex color for accent (e.g. '#ef4444'). Defaults to indigo.
attendeesarrayyesAttendees to generate identity badges for
avatarStylestring–Avatar style for the whole crew. 'notionists' = Notion-style sketch (default, friendly meetups), 'lorelei' = monochrome line art (calm/professional), 'bottts' = colorful robots (hackathons / playful…
dateISOstringyesEvent start time as ISO 8601 string (UTC or with offset)
durationHoursnumber–Event duration in hours (default 3)
rsvpUrlstring–URL to encode in the event RSVP QR code
titlestringyesEvent title
venuestring–Venue / location text
NameTypeReqDescription
badgesarrayyesOne identity badge per attendee
eventobjectyesEvent card data (title, date, venue, accent, RSVP QR, .ics)

No examples provided.

render-badge-png ~211

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.

NameTypeReqDescription
accentHexstring–Accent hex color
avatarStylestring–Avatar style (same options as generate-lineup). Match the event's style.
eventTitlestring–Event title (printed on the badge)
genderstring–Gender hint (same as generate-lineup). Match the badge.
namestringyesAttendee full name
rolestring–Role label
seedstring–Avatar seed override (defaults to name). Used when the user re-rolled this face.
NameTypeReqDescription
pngDataUrlstringyesThe rendered badge as a base64 PNG data URL

No examples provided.

Install

How do I install the Lineup MCP server?

Lineup is a hosted endpoint at https://lineup-bf157e35.alpic.live/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · lineup-bf157e35.alpic.live

# add to Claude Code
claude mcp add --transport http live-alpic-lineup-bf157e35-lineup 'https://lineup-bf157e35.alpic.live/'
Common questions

What is the Lineup MCP server?

Lineup is an MCP server listed in the public MCP registry as live.alpic.lineup-bf157e35/lineup. Turn one sentence into an event pack: event card, identity badges, QR codes, and .ics. This page covers its hosted endpoint (https://lineup-bf157e35.alpic.live).

Is the Lineup MCP server safe to use?

Lineup scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Lineup MCP server expose?

Lineup exposes 2 tools: generate-lineup, render-badge-png. Their descriptions and schemas cost roughly 515 tokens of context every time the server is loaded.

Does the Lineup MCP server require authentication?

No. We connected to Lineup without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Lineup MCP server still maintained?

Lineup is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.