Skip to content

MyLegend — public profiles, rich cards and personal agents

by falsalama · remote · no sign-in to list tools · v1.0.0 · published by GitHub user falsalama

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

Changes · 2

5 tools: 2 change things and 3 only read.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http mylegend https://mylegend.id/mcp

Findings

Matches of fixed checks, with the text they matched.

1 info

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 2Claude Code: ask
  • ask_personUse this for a specific question about a resolved published person, including follow-ups to their displayed rich card.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
  • save_my_agent_draftUse this only when the signed-in owner explicitly asks to create or edit their MyLegend agent.1 finding

    Why it is in this group

    • The name "save_my_agent_draft" says "save": a word for a change.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...egend for owner approval. Do not invent credentials or infer sensitive details."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
Only reads 3Claude Code: allow
  • find_personUse this when locating a person's owner-published MyLegend profile by name, headline, job title or organisation.No findings

    Why it is in this group

    • The name "find_person" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
  • get_my_agent_draftUse this to review the signed-in owner's suggested public introduction.No findings

    Why it is in this group

    • The name "get_my_agent_draft" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_profileUse this when the user asks to see a person's MyLegend profile or interactive rich card.No findings

    Why it is in this group

    • The name "get_profile" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http mylegend https://mylegend.id/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__mylegend__find_person",
      "mcp__mylegend__get_profile",
      "mcp__mylegend__get_my_agent_draft"
    ],
    "ask": [
      "mcp__mylegend__ask_person",
      "mcp__mylegend__save_my_agent_draft"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as mylegend. Review it before you use it.