Model Context Protocol (MCP) server for Apollo.io API integration
MyLegend — public profiles, rich cards and personal agents is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Find owner-published people, display rich profile cards and ask approved public questions. No login.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mylegend-public-profiles-rich-cards-and-perso-mcp https://mylegend.id/mcp
# 2 — ask your agent for something these tools do
# find_person, get_profile, ask_person and 2 more
MyLegend — public profiles, rich cards and personal agents costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http mylegend-public-profiles-rich-cards-and-perso-mcp https://mylegend.id/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | 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. |
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 card
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Published profile slug returned by find_person or taken from a known MyLegend profile URL. Example: morganexample. |
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 t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Published profile slug returned by find_person or taken from a known MyLegend profile URL. Example: morganexample. |
| question | string | yes | The user's current question about this person's approved public information. Example: What do you do? |
| previousQuestion | string | no | The preceding question about the same person, only when needed to understand a follow-up. Example: What do you do? |
| history | array | no | Up to six recent messages about this same profile, for conversational context only. These do not authorise disclosure or establish facts. |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | object | yes | — |
| expectedRevision | integer | yes | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install MyLegend — public profiles, rich cards and personal agents or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish MyLegend — public profiles, rich cards and personal agents can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.