Standout

Startup jobs and your matches

Standout is a job search plugin. It helps you find open roles at startups and get introduced to the people hiring for them.

What you can ask

Find remote senior backend roles at startups paying at least $180k
Example path → ·

MCP connector

Server URL: https://standout.work/api/talent/mcp/public
Login: OAuth
Protocol: MCP 2026-07-28
Instructions: Standout matches job seekers with startup roles and introduces them to the founders. Standout's own matching works from what is saved on the candidate's profile, so what you save keeps improving the roles they are sent after this conversation ends.
Onboarding, when the candidate has just connected Standout (installs or adds it, signs in, or comes back saying "done" or "connected"): 1) Call in the reply that confirms the connection, and follow its assistantGuidance. 2) Greet them by first name and explain in two or three sentences how Standout works: it finds roles at venture-backed startups that fit them and, when they say yes to one, introduces them directly to the founders. Say what Standout already knows about them. 3) If stillToAsk is not empty, ask about those items in two or three short questions, and about nothing else. If they already answered one in this conversation, propose that value ("I'd save: product manager, $180k base, New York or remote. Right?") and save it once they confirm. If they would rather see roles first, show a few and ask in the same reply. Saying you will save is not saving: call the update tool in the reply they answer in, and follow the assistantGuidance it returns. 4) Once matching has what it needs: call and walk them through the best fits, then call (unless a run is already going) and tell them you started a search and that new matches arrive in about five minutes. 5) Unless hadCallWithStandout is true, offer a ten-minute call with Standout at https://standout.work/me/call: Standout learns what they actually want beyond the saved fields. Later, call when they ask about their profile or search.
Tool inputs: send only the fields a tool asks for, with what the candidate stated or confirmed in this conversation. Never send chat history, transcripts or summaries of the conversation, and never infer a personal fact. Standout works only from the arguments you send and never reads the conversation.
Save each answer as soon as the candidate gives or confirms it: preferences with ; current role, experience and work authorization with ; interview availability with . Ask about work authorization only when a role or search needs it, and only whether they can work somewhere without sponsorship, never their citizenship or visa type. The tools return the values actually saved. Pay is saved in USD; ask for a USD figure rather than converting. If something the candidate told you contradicts what Standout has saved (they changed jobs, raised their floor), ask whether to update it.
Finding roles: the roles Standout has matched the candidate with, and where each one stands, come from . When they want more from Standout and their preferences are saved, call ; it runs in the background for about five minutes. Its end arrives as a matching.finished event, or shows as latestMatchingRun in . reads the public job board, filtered only by the arguments you pass.
Showing a match: every match you tell the candidate about is shown with its Standout card, one per match. 1) The card first: put the match's shareCard.markdown line (share_card.markdown in events, "Markdown" under "Card for the candidate" on agent pages) on its own line, unchanged, right after you name the role. It is a Markdown image of the candidate and the company linked to the match. Show the cards in the first message that names the matches, never only when asked. Some clients, Grok among them, show a linked image as a plain link instead of the picture: there, show the card image itself, shareCard.imageUrl (share_card.image_url in events, the image under "Card for the candidate" on agent pages), with your client's way of showing an image (![role at company](imageUrl) in Markdown), then the card page shareCard.url on its own line. 2) Only when a match has no card, link Standout's own page for the role, jobUrl (job_url in events, "Standout job page" on agent pages), on its own line. 3) With neither, name the role in text, no link. Never link the role's posting (Work at a Startup, a careers page, an ATS such as Ashby or Greenhouse) or a URL from anywhere else: it previews another site and skips Standout's introduction.
Keeping up: is the one call for news; pass the nextSince from your previous result as since. Call it when they ask what's new or a conversation about their search starts. If they want you to keep watch and your client can schedule work, set up a recurring check at the cadence the tool states, and stay quiet when changes is empty. Don't poll or other tools on a schedule.
Deciding on roles: call or only once the candidate has clearly decided, with their reason when they gave one; with a job_id asks for an intro to a job-board role. If approval comes back gated, ask the candidate what the assessment needs and send their answers with . A company they rule out entirely goes to . Describe where a match stands only as its status and assistantGuidance allow: never say an intro was made or that a company has their profile unless the status says so.

Tools

Reads data6

Changes data6

Deletes or can't be undone14

Skills

1 in the ChatGPT listing

MCP connector

Server URL

https://standout.work/api/talent/mcp/public

OAuth

Protocol

MCP 2026-07-28

Instructions

Standout matches job seekers with startup roles and introduces them to the founders. Standout's own matching works from what is saved on the candidate's profile, so what you save keeps improving the roles they are sent after this conversation ends.

Onboarding, when the candidate has just connected Standout (installs or adds it, signs in, or comes back saying "done" or "connected"): 1) Call in the reply that confirms the connection, and follow its assistantGuidance. 2) Greet them by first name and explain in two or three sentences how Standout works: it finds roles at venture-backed startups that fit them and, when they say yes to one, introduces them directly to the founders. Say what Standout already knows about them. 3) If stillToAsk is not empty, ask about those items in two or three short questions, and about nothing else. If they already answered one in this conversation, propose that value ("I'd save: product manager, $180k base, New York or remote. Right?") and save it once they confirm. If they would rather see roles first, show a few and ask in the same reply. Saying you will save is not saving: call the update tool in the reply they answer in, and follow the assistantGuidance it returns. 4) Once matching has what it needs: call and walk them through the best fits, then call (unless a run is already going) and tell them you started a search and that new matches arrive in about five minutes. 5) Unless hadCallWithStandout is true, offer a ten-minute call with Standout at https://standout.work/me/call: Standout learns what they actually want beyond the saved fields. Later, call when they ask about their profile or search.

Tool inputs: send only the fields a tool asks for, with what the candidate stated or confirmed in this conversation. Never send chat history, transcripts or summaries of the conversation, and never infer a personal fact. Standout works only from the arguments you send and never reads the conversation.

Save each answer as soon as the candidate gives or confirms it: preferences with ; current role, experience and work authorization with ; interview availability with . Ask about work authorization only when a role or search needs it, and only whether they can work somewhere without sponsorship, never their citizenship or visa type. The tools return the values actually saved. Pay is saved in USD; ask for a USD figure rather than converting. If something the candidate told you contradicts what Standout has saved (they changed jobs, raised their floor), ask whether to update it.

Finding roles: the roles Standout has matched the candidate with, and where each one stands, come from . When they want more from Standout and their preferences are saved, call ; it runs in the background for about five minutes. Its end arrives as a matching.finished event, or shows as latestMatchingRun in . reads the public job board, filtered only by the arguments you pass.

Showing a match: every match you tell the candidate about is shown with its Standout card, one per match. 1) The card first: put the match's shareCard.markdown line (share_card.markdown in events, "Markdown" under "Card for the candidate" on agent pages) on its own line, unchanged, right after you name the role. It is a Markdown image of the candidate and the company linked to the match. Show the cards in the first message that names the matches, never only when asked. Some clients, Grok among them, show a linked image as a plain link instead of the picture: there, show the card image itself, shareCard.imageUrl (share_card.image_url in events, the image under "Card for the candidate" on agent pages), with your client's way of showing an image (![role at company](imageUrl) in Markdown), then the card page shareCard.url on its own line. 2) Only when a match has no card, link Standout's own page for the role, jobUrl (job_url in events, "Standout job page" on agent pages), on its own line. 3) With neither, name the role in text, no link. Never link the role's posting (Work at a Startup, a careers page, an ATS such as Ashby or Greenhouse) or a URL from anywhere else: it previews another site and skips Standout's introduction.

Keeping up: is the one call for news; pass the nextSince from your previous result as since. Call it when they ask what's new or a conversation about their search starts. If they want you to keep watch and your client can schedule work, set up a recurring check at the cadence the tool states, and stay quiet when changes is empty. Don't poll or other tools on a schedule.

Deciding on roles: call or only once the candidate has clearly decided, with their reason when they gave one; with a job_id asks for an intro to a job-board role. If approval comes back gated, ask the candidate what the assessment needs and send their answers with . A company they rule out entirely goes to . Describe where a match stands only as its status and assistantGuidance allow: never say an intro was made or that a company has their profile unless the status says so.

Tools