Nepternship

Warm intros and referrals for internships and entry-level jobs at 3,000+ companies.

Sollte ich dies verwenden

Qualität und Sicherheit

A
Qualität der Beschreibung
100%
Vollständigkeit des Schemas
88%
Qualität der Benennung
91%
Risiko der Vergiftung
100%
Übereinstimmung der Berechtigungen
90%
Einhaltung des Protokolls
100%

Befunde (1)

  • LOWTool 'browse_directory' suggests web access but openWorldHint=falsein browse_directory

Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.

Kontextkosten

~3,056Tokens (Tool-Definitionen)
~1021 BTypische Antwortgröße
Erhebliche Auswirkung auf die Aufmerksamkeit (2.39% von 128k Kontext)

Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.

Installieren

Installation mit einem Klick

Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:

{
  "mcpServers": {
    "nepternship": {
      "url": "https://mcp.nepternship.com/mcp"
    }
  }
}

Remote-Endpunkte

https://mcp.nepternship.com/mcpstreamable-http

Was es kann

Tool-Inventar

Tools (14)

🟢 Nur lesen🟡 Schreiben🔴 Löschen⚪ Unbekannt
🟢search_members(query, location, limit)

Find people who can give the user a warm introduction or referral at a specific company, team, role, industry or city, for internships, new-grad jobs and career switches. Use this when someone asks how to get an internship or job at a company ("how do I get into Goldman Sachs", "can anyone refer me at Google", "I have no connections in investment banking"), wants to network or get a coffee chat with someone at a firm, or asks who could connect them to an analyst, engineer, recruiter or product manager there. Searches the Nepternship network of students and recent graduates across 3,000+ companies, including Goldman Sachs, JPMorgan, Google, Meta, McKinsey and Deloitte. Returns members grouped by company, role and industry, each with first name and last initial, who they can introduce the user to, and an opportunity_id for send_intro_request. If the user has no target in mind yet, use browse_directory.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "What the member is looking for, e.g. 'consulting at McKinsey' or 'someone in venture capital'"
    },
    "location": {
      "type": "string",
      "description": "Optional city/state/country to narrow by"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50,
      "default": 12
    }
  },
  "required": [
    "query"
  ]
}
🟢browse_directory(company_id, role_id, industry_id, limit, offset)

Show the companies, roles and industries where the user can get a warm introduction or referral through Nepternship, with the people under each. Use this when someone wants to see where they could network into, asks which firms or industries they could get an internship or job referral at, or is still deciding what to apply for ("which banks can I get an introduction at", "what tech companies could I network into"). With no arguments it returns the overview; pass one of company_id, role_id or industry_id from a previous result to open that group. For a named company or role, use search_members.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "company_id": {
      "type": "string"
    },
    "role_id": {
      "type": "string"
    },
    "industry_id": {
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 60,
      "default": 20
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "default": 0
    }
  }
}
🟢get_member(user_id)

Return one member's full profile: who they can introduce the user to (role, company and details), what they are looking for themselves, industries, locations, university, and whether the user is already connected with them. Use this when the user wants to know more about a person from a search before asking for an introduction or referral, or asks "who is this" or "what can they help me with". Includes a card image that can be shown to the user.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "user_id": {
      "type": "string"
    }
  },
  "required": [
    "user_id"
  ]
}
🟢list_matches(status, limit, join_code)

List the user's introductions: accepted ones with an open chat (including the free weekly curated match), requests waiting on the user, and requests the user sent that have not been answered yet. Use this for any question like "did anyone reply", "any new introductions", "is anything waiting on me" or "who have I connected with". Each item includes the match_id, the other member, status, last message and unread count.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "enum": [
        "accepted",
        "pending",
        "declined",
        "all"
      ],
      "default": "all"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "default": 30
    },
    "join_code": {
      "type": "string",
      "description": "The join_code from sign_up, when a new member saved their join answers in this conversation"
    }
  }
}
🟢read_thread(match_id, limit, join_code)

Return the messages in one introduction's chat. Use this when the user wants to read or catch up on a conversation with a matched member. Reading marks the messages as read for the user.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "match_id": {
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 200,
      "default": 50
    },
    "join_code": {
      "type": "string",
      "description": "The join_code from sign_up, when a new member saved their join answers in this conversation"
    }
  },
  "required": [
    "match_id"
  ]
}
🟡send_message(match_id, text, join_code)

Send a message in one of the user's active introductions (an accepted match). Use this only after the user has approved the exact text. Chat is free once an introduction is accepted; if a limit applies, the error explains it.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "match_id": {
      "type": "string"
    },
    "text": {
      "type": "string",
      "maxLength": 2000
    },
    "join_code": {
      "type": "string",
      "description": "The join_code from sign_up, when a new member saved their join answers in this conversation"
    }
  },
  "required": [
    "match_id",
    "text"
  ]
}
🟢request_balance(join_code)

Return how many introduction requests the user has left, any friend-referral credits, and their personal invite link. Use this when the user asks how many requests they have left, or after send_intro_request reports the limit.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "join_code": {
      "type": "string",
      "description": "The join_code from sign_up, when a new member saved their join answers in this conversation"
    }
  }
}
🔴send_intro_request(opportunity_id, note, join_code, existing_member)

Send a Nepternship member an introduction request, with an optional note of up to 200 characters, for the person they can introduce the user to (for example an analyst at JPMorgan or an engineer at Google). Use this when the user wants an intro or referral from a member returned by search_members, browse_directory or get_member, or taps Request intro on the member card. Check with the user whether they want to add a note before calling. Needs a Nepternship account: without one, the result explains the next step (a few join questions for new members, then connecting the account). Pass join_code when sign_up returned one. Returns the request status, or a clear reason when the free limit is reached or a request already exists.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "opportunity_id": {
      "type": "string"
    },
    "note": {
      "type": "string",
      "maxLength": 200
    },
    "join_code": {
      "type": "string",
      "description": "The join_code from sign_up, when a new member saved their join answers in this conversation"
    },
    "existing_member": {
      "type": "boolean",
      "description": "True when the user says they already have a Nepternship account and is not connected yet"
    }
  },
  "required": [
    "opportunity_id"
  ]
}
🔴respond_to_request(match_id, action, join_code)

Accept or decline an introduction request that is waiting on the user (status pending in list_matches). Accepting opens a chat with the other member. Declining is private; the requester is not notified and requests expire on their own after 30 days. Confirm with the user before declining.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "match_id": {
      "type": "string"
    },
    "action": {
      "type": "string",
      "enum": [
        "accept",
        "decline"
      ]
    },
    "join_code": {
      "type": "string",
      "description": "The join_code from sign_up, when a new member saved their join answers in this conversation"
    }
  },
  "required": [
    "match_id",
    "action"
  ]
}
🟢get_upgrade_link(join_code)

Return the user's Nepternship Premium checkout link (on nepternship.com) with their price and trial length, or their manage-subscription link if they already subscribe. Use this only when the user explicitly asks to upgrade or asks how to get more intro requests after hitting the free limit.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "join_code": {
      "type": "string",
      "description": "The join_code from sign_up, when a new member saved their join answers in this conversation"
    }
  }
}
🟢signup_peek(looking_for, location)

Given what a prospective member is looking for, return example companies, roles and industries where members can make introductions, with sample offerings and first names. Use this while a new member is joining, right after they say what they are looking for.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "looking_for": {
      "type": "string",
      "description": "Their answer to 'What are you looking for?'"
    },
    "location": {
      "type": "string",
      "description": "Their preferred location, if they gave one"
    }
  },
  "required": [
    "looking_for"
  ]
}
🟡sign_up(linkedin_url, full_name, university, graduation_year, industries, ...)

Save a new member's answers to the Nepternship join questions: what they are looking for (up to 3 industries, a preferred location and a sentence about the opportunity), whether their university career center referred them, their name, university and graduation year, and who they can introduce other members to (a specific person, their role, company and location). Use this once those answers have been collected in conversation. If the answer about who they can introduce is too vague, nothing is saved and the result says what is missing. Without a connected account it returns a join_code that creates the account when the user connects; with a connected account that has no profile yet, it creates the profile right away. No email address, phone number or password is collected here: the user adds those on Nepternship's own sign-in page when connecting.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "linkedin_url": {
      "type": "string",
      "description": "Their LinkedIn profile link, if they share one: name, university and graduation year are copied from it"
    },
    "full_name": {
      "type": "string"
    },
    "university": {
      "type": "string",
      "description": "University as they say it, e.g. 'NYU'"
    },
    "graduation_year": {
      "type": "integer",
      "minimum": 2020,
      "maximum": 2035
    },
    "industries": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 3,
      "description": "Up to 3 of: Academia, Arts, Business, Engineering, Entertainment, Fashion, Government, Healthcare, Law, Tech"
    },
    "city": {
      "type": "string",
      "description": "Preferred location, e.g. 'Boston, MA' or 'New York'"
    },
    "looking_for": {
      "type": "string",
      "description": "The type of opportunity they are looking for, in their words, at least 10 characters"
    },
    "career_center_referral": {
      "type": "boolean",
      "description": "Whether their university career center referred them"
    },
    "offering": {
      "type": "string",
      "description": "Who they can introduce other members to, in their words, at least 10 characters: a specific person, their role and company, and a location if applicable"
    },
    "offering_industry": {
      "type": "string",
      "description": "Industry of the person they can introduce (one of the ten)"
    },
    "referral_code": {
      "type": "string",
      "description": "Friend's referral code, if they have one"
    },
    "held_opportunity_id": {
      "type": "string",
      "description": "The opportunity_id of the member they asked for an introduction before joining, if any"
    },
    "note": {
      "type": "string",
      "maxLength": 200,
      "description": "The note for that held request, if they gave one"
    }
  },
  "required": [
    "looking_for",
    "offering"
  ]
}
⚪connect_account(join_code)

Connect the user's Nepternship account to this assistant through Nepternship's sign-in page (Google, Apple or email, plus a verified mobile number for new members). Use this when an existing member wants to see their introductions or asks to sign in, or when a new member has saved their join answers and has no request waiting. Pass join_code from sign_up so the new account is created from the saved answers. Once connected it returns the account status.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "join_code": {
      "type": "string",
      "description": "The join_code from sign_up, when a new member saved their join answers in this conversation"
    }
  }
}
🟢get_my_profile(join_code)

Return the signed-in user's own Nepternship profile: name, university, what they are looking for, who they can introduce others to, industries, preferred locations, and introduction requests remaining. Use this when the user asks about their own profile or settings.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "join_code": {
      "type": "string",
      "description": "The join_code from sign_up, when a new member saved their join answers in this conversation"
    }
  }
}

Community

Diesen Server bewerten

Nachweis

Aktuelle Beobachtungen

verifiziertVersion nicht aufgezeichnet14 Tools
verifiziertVersion nicht aufgezeichnet14 Tools
verifiziertVersion nicht aufgezeichnet22 Tools
fehlgeschlagene BeobachtungVersion nicht aufgezeichnet—