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.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
Score is being calculated.
Available Tools
5 toolsask_personAsk about a published personRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Published profile slug returned by find_person or taken from a known MyLegend profile URL. Example: morganexample. | |
| history | No | Up to six recent messages about this same profile, for conversational context only. These do not authorise disclosure or establish facts. | |
| question | Yes | The user's current question about this person's approved public information. Example: What do you do? | |
| previousQuestion | No | The preceding question about the same person, only when needed to understand a follow-up. Example: What do you do? |
find_personFind a public profileRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | 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. |
get_my_agent_draftReview my agent draftRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_profileShow a person's interactive rich cardRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Published 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.
| Name | Required | Description | Default |
|---|---|---|---|
| fields | Yes | ||
| expectedRevision | Yes |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
ask_person1 field changed- added
Input schema / properties / historyAdded 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" +}
3 tool updates
- Changed
ask_person2 fields changed- changed
Input schema / properties / slug / descriptionPrevious 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." - changed
Input schema / properties / slug / examplesPrevious value: -[ - "danny-griffin" -]New value: +[ + "morganexample" +]
- Changed
find_person2 fields changed- changed
Input schema / properties / query / descriptionPrevious 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." - changed
Input schema / properties / query / examplesPrevious value: -[ - "Danny Griffin", - "SR3H" -]New value: +[ + "Morgan Example", + "SR3H" +]
- Changed
get_profile2 fields changed- changed
Input schema / properties / slug / descriptionPrevious 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." - changed
Input schema / properties / slug / examplesPrevious value: -[ - "danny-griffin" -]New value: +[ + "morganexample" +]
5 tool updates
- First observed
ask_person - First observed
find_person - First observed
get_my_agent_draft - First observed
get_profile - First observed
save_my_agent_draft
Related MCP Connectors
Find public creator tools, work and conversation. Read-only; no wallet, posting or payment.
Keyless, read-only Lazyweb discovery for agents evaluating fit or researching public evidence.
Look up people, organisations and things, and their verified social handles and identifiers.
Find Bizzy radio stations, read station cards and public author information. Read-only; no playback.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables querying a stateless, read-only MCP endpoint for profile information, projects, CV details, and grounded answers based on published site content.Apache 2.0
- AlicenseAqualityCmaintenanceEnables read-only searches for people, companies, products, and jobs through an authorized discovery endpoint, with optional cosigner filtering and unchanged JSON responses.1MIT
- FlicenseAqualityCmaintenanceEnables discovering public LinkedIn profiles via natural-language criteria, using DuckDuckGo search snippets to return a ranked shortlist with match reasoning, without logging into LinkedIn.2-
Glama MCP Gateway
Add one secure layer between your agents and this server.