Connect to MyLegend

On the web

Find a person, open their card and ask a question. Websites and compatible hosts can embed the same interface using https://mylegend.id/people/{slug}/card/embed. It works without an MCP connection.

For browsing and HTTP assistants

Find a published person at /api/people?query={name or organisation}. Compare the returned organisation and location, then read their cardDataUrl to build a card or open their cardUrl.

For a live public answer, open /api/people/{slug}/ask?question={URL-encoded question}, or POST JSON { "question": "What do you do?" } to the same path. Both use the same owner-approved information and disclosure rules. Use only public questions in URLs.

Connection metadata · OpenAPI reference · Try Danny's public answer

ChatGPT’s Intelligent UI

Supported ChatGPT modes can create an interactive view using your approved public card data. We supply your portrait, link logos, MyLegend styling guidance and the public answer endpoint. ChatGPT chooses the presentation and which actions it can run. This route works alongside the original MyLegend component and does not give access to private messages or knowledge.

Inside ChatGPT and other AI apps

Connect the public endpoint https://mylegend.id/mcp using Streamable HTTP, with no authentication for public tools. The app must support MCP Apps and load the card’s UI resource. A web search can read the page and return a link; it does not enable native inline rendering. Public app distribution makes the connection easier to access.

Available tools

• find_person — find public profiles by name or public profile words. Try “Morgan Example” to retrieve the demo.
• get_profile — read an approved profile and render its rich card in hosts that support MCP Apps.
• ask_person — extract a bounded answer from approved public facts. It says when the profile lacks an answer.

Trust and scope

Owner publication does not independently verify a person or their claims. Morgan Example is fictional and marked as a demo. This connection has no private record access or delegated action tools. AI platforms choose whether to connect, discover or show a card. Withdrawing information from MyLegend does not remove copies already held elsewhere.

If a connection fails

A missing tool means the current chat has no usable connector. A DNS failure or browser retrieval error without an HTTP status does not establish a MyLegend outage. Check the public profile and HTTP answer independently. MCP clients must use JSON-RPC POST; opening /mcp with GET returns 405 by design. OAuth discovery is for the optional owner connection; public tools need no authentication. A successful answer also does not establish that the host displayed an interactive card.