MyLegend — public profiles, rich cards and personal agents

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Find owner-published people, display rich profile cards and ask approved public questions. No login.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "MyLegend — public profiles, rich cards and personal agents": {
      "url": "https://mylegend.id/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (5)

• find_person read-only

  Use this when locating a person's owner-published MyLegend profile by name, headline, job title or organisation. Returns at most 10 matches with approved job, organisation and location context, including labelled fictional demos. Compare supplied context with those fields; ask for clarification if multiple plausible people remain. Location is not a search field. When the user requests a profile or rich card and the person is resolved, call get_profile once with the returned slug. A match is not independent verification.

  Parameters:

  • query (required) — string — A name, headline, job title or organisation name from the published profile. Examples: Morgan Example or SR3H. Use location to compare returned matches, not as a search term.

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• get_profile read-only

  Use this when the user asks to see a person's MyLegend profile or interactive rich card. Shows the card, with questions and a private message composer, in a compatible connected MCP Apps host. Invoke once to display the card; use ask_person for follow-up answers without another card. Use the resolved slug from find_person or a known MyLegend profile URL. No MyLegend login is needed for public cards.

  Parameters:

  • slug (required) — string — Published profile slug returned by find_person or taken from a known MyLegend profile URL. Example: morganexample.

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• ask_person read-only

  Use this for a specific question about a resolved published person, including follow-ups to their displayed rich card. Answers use approved information. Ask explicitly for technical detail, equations or a derivation to receive longer approved material when available. A question-only request does not require a card. If a card is requested, use get_profile once. No raw CV or P3 data is exposed. If the user offers an agreed code word, pass only that supplied phrase unchanged as the current question; never guess or suggest phrases.

  Parameters:

  • slug (required) — string — Published profile slug returned by find_person or taken from a known MyLegend profile URL. Example: morganexample.
  • question (required) — string — The user's current question about this person's approved public information. Example: What do you do?
  • history — array — Up to six recent messages about this same profile, for conversational context only. These do not authorise disclosure or establish facts.
  • previousQuestion — string — The preceding question about the same person, only when needed to understand a follow-up. Example: What do you do?

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• get_my_agent_draft read-only

  Use this to review the signed-in owner's suggested public introduction. Excludes private CV, knowledge, rules and unpublished personal notes. Never reads another account.

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• save_my_agent_draft

  Use this only when the signed-in owner explicitly asks to create or edit their MyLegend agent. Save only the fields they choose to share from this conversation, never the whole chat. Read the current revision first (0 if no draft). Saves a PRIVATE draft, never publishes. Show the proposed text for review and link to MyLegend for owner approval. Do not invent credentials or infer sensitive details.

  Parameters:

  • fields (required) — object
  • expectedRevision (required) — integer

  Hints: read-only no · destructive no · idempotent not declared · open-world no

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.