Skip to main content
Glama

MyLegend — public profiles, rich cards and personal agents

Server Details

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

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

Score is being calculated.

Available Tools

5 tools
ask_personAsk about a published person
Read-only
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
slugYesPublished profile slug returned by find_person or taken from a known MyLegend profile URL. Example: morganexample.
historyNoUp to six recent messages about this same profile, for conversational context only. These do not authorise disclosure or establish facts.
questionYesThe user's current question about this person's approved public information. Example: What do you do?
previousQuestionNoThe preceding question about the same person, only when needed to understand a follow-up. Example: What do you do?
find_personFind a public profile
Read-only
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesA 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.
get_my_agent_draftReview my agent draft
Read-only
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

get_profileShow a person's interactive rich card
Read-only
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
slugYesPublished profile slug returned by find_person or taken from a known MyLegend profile URL. Example: morganexample.
save_my_agent_draftPrepare my agentInspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
fieldsYes
expectedRevisionYes

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedask_person1 field changed
      • addedInput schema / properties / history
        Added value: +{
        +  "description": "Up to six recent messages about this same profile, for conversational context only. These do not authorise disclosure or establish facts.",
        +  "examples": [
        +    [
        +      {
        +        "content": "What is your research about?",
        +        "role": "user"
        +      },
        +      {
        +        "content": "An approved research overview.",
        +        "role": "assistant"
        +      }
        +    ]
        +  ],
        +  "items": {
        +    "additionalProperties": false,
        +    "properties": {
        +      "content": {
        +        "maxLength": 4000,
        +        "minLength": 1,
        +        "type": "string"
        +      },
        +      "role": {
        +        "enum": [
        +          "user",
        +          "assistant"
        +        ],
        +        "type": "string"
        +      }
        +    },
        +    "required": [
        +      "role",
        +      "content"
        +    ],
        +    "type": "object"
        +  },
        +  "maxItems": 6,
        +  "type": "array"
        +}
  2. 3 tool updates
    • Changedask_person2 fields changed
      • changedInput schema / properties / slug / description
        Previous value: -"Published profile slug returned by find_person or taken from a known MyLegend profile URL. Example: danny-griffin."New value: +"Published profile slug returned by find_person or taken from a known MyLegend profile URL. Example: morganexample."
      • changedInput schema / properties / slug / examples
        Previous value: -[
        -  "danny-griffin"
        -]New value: +[
        +  "morganexample"
        +]
    • Changedfind_person2 fields changed
      • changedInput schema / properties / query / description
        Previous value: -"A name, headline, job title or organisation name from the published profile. Examples: Danny Griffin or SR3H. Use location to compare returned matches, not as a search term."New value: +"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."
      • changedInput schema / properties / query / examples
        Previous value: -[
        -  "Danny Griffin",
        -  "SR3H"
        -]New value: +[
        +  "Morgan Example",
        +  "SR3H"
        +]
    • Changedget_profile2 fields changed
      • changedInput schema / properties / slug / description
        Previous value: -"Published profile slug returned by find_person or taken from a known MyLegend profile URL. Example: danny-griffin."New value: +"Published profile slug returned by find_person or taken from a known MyLegend profile URL. Example: morganexample."
      • changedInput schema / properties / slug / examples
        Previous value: -[
        -  "danny-griffin"
        -]New value: +[
        +  "morganexample"
        +]
  3. 5 tool updates
    • First observedask_person
    • First observedfind_person
    • First observedget_my_agent_draft
    • First observedget_profile
    • First observedsave_my_agent_draft

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables clients to search, read, and verify sealed forecasts and public-record cards, inspect resolution calendars, engine strands, sensor alerts, and wire headlines, and check whether stories are independent events or echoes. All access is read-only and requires no key, account, or dependencies.
    159 npm
    Apache 2.0
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables querying a stateless, read-only MCP endpoint for profile information, projects, CV details, and grounded answers based on published site content.
    Apache 2.0
  • A
    license
    A
    quality
    C
    maintenance
    Enables read-only searches for people, companies, products, and jobs through an authorized discovery endpoint, with optional cosigner filtering and unchanged JSON responses.
    1
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources