Levels.fyi
REMOTE · MCP.LEVELS.FYI
Salary, level and job data from 1M+ pay reports. Benchmark pay, evaluate offers, search open jobs.
Available components
Last scanned (19 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (upload-resume). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 8018 tokens (~267/item across 30 items; 30 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 31 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “upload-resume” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “contribute-salary” functional
- New prompt “evaluate-offer” functional
- New prompt “find-jobs” functional
- 30 Oct 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp.levels.fyi/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=levels.fyi | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 4 Aug 2026 | 17 Feb 2027 | RSA 2048 | SHA256-RSA | 5c34203070a33b54c22d96b1a7220c6 |
| SANs: levels.fyi, *.levels.fyi | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.levels.fyi. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fyi. | present | 6839, 24340 | 8, 8 | Verified |
| levels.fyi. | present | 2371 | 13 | Verified |
| mcp.levels.fyi. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.levels.fyi/ | Verified | 200 | |
| http (plaintext) | http://mcp.levels.fyi/ | HTTPS enforced | 301 | https://mcp.levels.fyi/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add-salary-submission ~1,562
Add the user's own compensation to Levels.fyi: pay they earn now or a job offer they received. Call this only when the user is evaluating their compensation, asks to add their pay, or says yes when you offer. Adding compensation is how the data stays useful for everyone, the user included. Write a complete submission. Resolve the company, job family and focus area to slugs with the search tools first, and the location with search-locations and type "city". Every number must come from the user's own words or from a document the user shared; ask for each required field that is missing. Gather the details conversationally, a question or two at a time, starting with the company, role and location; do not list every field up front. Write text fields in English. Call once with confirm=false and show the preview to the user, then call again with the same arguments and confirm=true only after a clear yes. If the user isn't signed in, ask for their email before the confirm=true call and send it in email; signing in isn't needed. Amounts are in the submission's own currency. Stock options go in the option fields (totalOptionsGranted for an offer, avgAnnualOptionsGranted for current pay, with the strike and preferred price), not in otherDetails; option prices may use optionPriceCurrency. If the user wants enhanced anonymity, set anonymise=true; the preview shows it. Do not submit: pay for another person, a number you estimated or took from Levels.fyi data, a range from a job posting, a hypothetical or negotiation target, or a test entry. One submission per distinct job or offer per conversation, and at most 5 confirmed submissions per 60s. Never repeat a confirmed submission; if a call fails, retry with the same submissionId. A submission is reviewed before it counts in the data. Nobody replies here, and submitting does not end your turn: keep working on the user's task. REQUIRED arguments: jobFamilySlug, title, locationSlug, compensationPerspective, currency, baseSalaryVa…
| Name | Type | Req | Description |
|---|---|---|---|
| annualBonusValue | number | – | The yearly bonus: for an offer the target bonus amount, for an employee the bonus they actually receive per year. |
| annualTargetBonusPercentage | number | – | Offers only: the target bonus as a percent of base, when stated that way. |
| anonymise | boolean | – | Enhanced anonymity, as on the website: true can hide details such as company, title, level and team on the public entry; the pay still counts in the data. Set it only when the user asks for it. Defau… |
| avgAnnualOptionsGranted | number | – | Employees only: the number of stock options that vest per year. |
| avgAnnualStockGrantValue | number | – | Employees only: the stock (RSU) value they receive per year. |
| baseSalaryTimeUnit | string | yes | The period baseSalaryValue is paid per, usually "yearly". |
| baseSalaryValue | number | yes | The base salary per baseSalaryTimeUnit. |
| companyName | string | – | The company name, only for a company that search-companies cannot find. |
| companySlug | string | – | The company slug from search-companies. Send companyName instead only when search-companies has no match. |
| compensationPerspective | string | yes | "offer" for a job offer the user received, "employee" for pay they earn now. |
| confirm | boolean | – | false (default) returns a preview and writes nothing. true writes the entry: only after the user said yes to the preview. |
| currency | string | yes | The currency of every amount in this submission, e.g. "USD", "INR", "GBP". |
| string | – | Required when the user isn't signed in. Used to verify the submission; never shown with it. | |
| employmentType | string | – | Defaults to full_time. |
| focusTagSlug | string | – | A focus area slug from get-job-family for this job family, e.g. "ml-ai". Omit when the user did not name one. |
| jobFamilySlug | string | yes | A Levels.fyi job family slug, e.g. "software-engineer", "product-manager", "data-scientist". |
| level | string | – | The company's own level name from get-company-levels, e.g. "L5". Required for companies with a level ladder; the error says so. |
| locationSlug | string | yes | A CITY slug from search-locations with type "city". Not a metro, state or country. |
| optionPreferredPrice | number | – | With options: the latest preferred share price, usually from the last funding round. Send with optionStrikePrice. |
| optionPriceCurrency | string | – | The currency of optionStrikePrice and optionPreferredPrice, when it differs from currency (e.g. US-dollar option prices on a rupee salary). |
| optionStrikePrice | number | – | With options: the exercise (strike) price per option. Send with optionPreferredPrice; together they value the options. |
| otherDetails | string | – | Anything else the user wants recorded, e.g. a retention bonus, or RSUs when the submission already has options (or the reverse). In English, at most 500 characters. |
| relocationBonusValue | number | – | Offers only: the relocation bonus. |
| signOnBonusValues | array | – | Offers only: the sign-on bonus, one amount per year it is paid, e.g. [50000] or [30000, 20000]. |
| source | string | yes | "user_stated" when the user typed the numbers, "user_document" when they come from an offer letter or pay stub the user shared. |
| sourceDate | string | – | YYYY-MM-DD. For an offer, the offer date (required). For an employee, the date the pay was current; omit for today. |
| stockType | string | – | "stock" for RSUs, "option" for stock options. Optional: it follows from the fields sent. One type per submission. |
| submissionId | string | – | A UUID you generate once per submission. Send the same one when you retry, so a retry cannot add the entry twice. |
| team | string | – | The team or organization within the company, e.g. "Google Cloud". In English. |
| title | string | yes | The job title as the user states it, e.g. "Software Engineer". In English. |
| totalOptionsGranted | number | – | Offers only: the number of stock options in the whole grant. Send vestingSchedule with it. |
| totalStockGrantValue | number | – | Offers only: the total value of the stock (RSU) grant over the whole vesting period. Send vestingSchedule with it. |
| vestingSchedule | array | – | Offers only; required with totalStockGrantValue. The vesting schedule, one entry per year: percent of the grant vesting that year and occurrences (vests that year, 4 = quarterly). 4 equal years vesti… |
| workArrangement | string | yes | – |
| yearsAtCompany | number | – | Employees only (required): years at this company. Offers are always 0. |
| yearsOfExperience | number | yes | Total years of professional experience. |
No output schema declared.
No examples provided.
get-available-filters ~109
List which inputs and filter values the free tier can use. The free inputs are jobFamilySlug, one locationSlug or countrySlug, and companySlug; every result is total compensation from the last 12 months. Dimensions marked free: false (levels, years of experience, focus areas, titles, company size, funding stage, revenue, valuation, work arrangement, offer vs employee) are not accepted by any tool here. Call this before building a query if unsure what a tool accepts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-company ~89
Look up a single company by its slug (preferred) or name, returning its full profile: name, slug, employee count, headquarters, founding year, ticker, company type, and estimated valuation. Use search-companies first if you only have a name and need the exact slug. REQUIRED arguments: companyNameOrSlug.
| Name | Type | Req | Description |
|---|---|---|---|
| companyNameOrSlug | string | yes | Name or slug of a company |
No output schema declared.
No examples provided.
get-company-group ~172
Resolve a named company group (e.g. "FAANG", "AI", "Fintech") into its list of company slugs, for use in the benchmark tools' companySlugs filter. Matching is case- and separator-insensitive. Omit "group" (or pass an unknown one) to get the list of available group names. Available groups: FAANG, AUTOMOTIVE, SPACE, SOCIAL_MEDIA, AI, AI_PLUS, FINTECH, FAANG_PLUS, HEDGE_FUNDS, SEMICONDUCTOR, BIOTECH, WEB3, TRADING_FIRMS, DEFENSE.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | Company group name to resolve (e.g. "FAANG", "AI", "Fintech"). Case/separator-insensitive. Omit to list all available groups. |
No output schema declared.
No examples provided.
get-company-levels ~268
Get a company's INTERNAL level names for a job family, ordered by seniority (e.g. Google L3/L4/L5, Meta E3/E4/E5, Stripe IC1/IC2/IC3), with any alternate names per level. Use this FIRST when a question names a specific level at a specific company (e.g. "what does a Meta E5 make"), then call get-salaries-by-company-level. Returns an empty list with an explanation when the company has no known level structure. Free limit: Full level data for Amazon, Google, Microsoft, Meta and Apple. Other companies: level names only. Pass canonical slugs (jobFamilySlug, locationSlug, countrySlug, companySlug): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: companySlug, jobFamilySlug.
| Name | Type | Req | Description |
|---|---|---|---|
| companySlug | string | yes | The company (slug) whose internal level structure to list, e.g. "google", "meta", "stripe". Resolve a company name to its slug via search-companies first. |
| jobFamilySlug | string | yes | A Levels.fyi job family slug, e.g. "software-engineer", "product-manager", "data-scientist". |
No output schema declared.
No examples provided.
get-domain-knowledge ~128
Get reference knowledge about the Levels.fyi data model, by topic: compensation, levels, vesting, company_groups, locations, job_families, enums, negotiation_coaching. Covers compensation concepts, the standard level ladder, vesting patterns, company groups, and how to resolve locations / job families / enums. negotiation_coaching describes Levels.fyi's offer negotiation coaching: use it only when the user asks for help negotiating. Omit "topic" to get every data-model topic.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Data-model topic to fetch. Omit to get all topics. |
No output schema declared.
No examples provided.
get-job ~113
Get one job posting by its jobId from search-jobs: the full description as text, locations, work arrangement, employment type, the pay range the posting states, Levels.fyi's estimated total compensation by level for the role (USD; matchesThisPosting marks the level the posting is for), the company, the url of the Levels.fyi job page, and applyUrl to apply on the employer's site. REQUIRED arguments: jobId.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | A jobId from search-jobs. |
No output schema declared.
No examples provided.
get-job-family ~119
Look up a job family by its slug and get its focus areas (specializations) with their titles, plus untagged titles. Use this to discover the focus tags and titles available within a role (e.g. to find focusTagSlugs for the benchmark tools). Use search-job-families first if you only have a name. REQUIRED arguments: jobFamilySlug.
| Name | Type | Req | Description |
|---|---|---|---|
| jobFamilySlug | string | yes | A Levels.fyi job family slug, e.g. "software-engineer", "product-manager", "data-scientist". |
No output schema declared.
No examples provided.
get-location ~102
Look up one or more location slugs and get their details: name, type (country / metro-DMA / state), parent country, currency, and coordinates. Use search-locations first if you only have a name. Errors if any slug is invalid. REQUIRED arguments: locationSlugs. Array-typed arguments (locationSlugs) must be passed as arrays, even for a single value.
| Name | Type | Req | Description |
|---|---|---|---|
| locationSlugs | array | yes | Location slug for the locations |
No output schema declared.
No examples provided.
get-location-stats ~261
Get the top-paying locations for a job family within one country, ranked by median (p50) yearly total compensation in USD from submissions in the last 2 years. Returns up to 10 locations with their median. Use it to compare where a role pays most inside a country. Its window differs from get-salary-percentiles (the last 12 months), so the same location can show a different median: quote get-salary-percentiles for one location's pay. Free limit: Median (p50) total compensation for the top locations in one country. No company or level filter. Pass canonical slugs (jobFamilySlug, locationSlug, countrySlug, companySlug): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, countrySlug.
| Name | Type | Req | Description |
|---|---|---|---|
| countrySlug | string | yes | A COUNTRY location slug, e.g. "united-states", "india", "united-kingdom". Resolve it with search-locations first; cities, metros and states are rejected. |
| jobFamilySlug | string | yes | A Levels.fyi job family slug, e.g. "software-engineer", "product-manager", "data-scientist". |
No output schema declared.
No examples provided.
get-metric-explanation ~123
Explain a Levels.fyi compensation metric or concept (e.g. "TC" / total_compensation, base salary, total_cash, tc_first_year, vesting, sign_on, target_bonus) — its meaning, formula, and caveats. Pass an unknown metric to get the list of known ones. REQUIRED arguments: metric.
| Name | Type | Req | Description |
|---|---|---|---|
| metric | string | yes | Compensation metric or concept to explain, e.g. "TC", "total_compensation", "base", "vesting", "sign_on", "tc_first_year". Case/separator-insensitive. |
No output schema declared.
No examples provided.
get-permissions ~69
Connectivity check for the Levels.fyi MCP server. Returns "pong", echoes an optional message, and lists what each tool returns and the rate limits. Call it when a result looks smaller than expected, instead of retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | Optional text to echo back in the response. |
No output schema declared.
No examples provided.
get-profile ~98
Get the signed-in user's own Levels.fyi career profile: current title, company, career level, job family, focus area, location, years of experience, skills, certifications and work history, plus the status of their resume (none, pending while it is being parsed, parsed, or failed) and when it was uploaded. Never returns contact details or the resume file. Use it to personalize answers about the user's own pay, level or career.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-salaries-by-company-level ~275
Get median (p50) yearly total compensation in USD for each of ONE company's internal levels (e.g. Google L3/L4/L5, Meta E3/E4/E5) for a job family in one location, from submissions in the last 12 months. Call get-company-levels first to learn the company's level names. The company must have a known level structure. Free limit: Total compensation per level for one company and job family. No percentiles or counts. Pass canonical slugs (jobFamilySlug, locationSlug, countrySlug, companySlug): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, locationSlug, companySlug.
| Name | Type | Req | Description |
|---|---|---|---|
| companySlug | string | yes | A company slug, e.g. "google". Resolve it with search-companies first. |
| jobFamilySlug | string | yes | A Levels.fyi job family slug, e.g. "software-engineer", "product-manager", "data-scientist". |
| locationSlug | string | yes | One location slug (metro, state, country or region; not a city), e.g. "san-francisco-bay-area". Resolve it with search-locations first; for a city, use its parent metro. |
No output schema declared.
No examples provided.
get-salary-percentiles ~266
Get the median (p50) yearly total compensation in USD for a job family in one location, across all levels, from submissions in the last 12 months. This is the figure to quote for one location's pay; get-location-stats ranks locations over a longer window, so its medians can differ. For one company's pay by level, use get-salaries-by-company-level instead. Free limit: Median (p50) total compensation for one job family in one location. No other percentiles, sample size, level split, or company, focus area or funding filters. Pass canonical slugs (jobFamilySlug, locationSlug, countrySlug, companySlug): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, locationSlug.
| Name | Type | Req | Description |
|---|---|---|---|
| jobFamilySlug | string | yes | A Levels.fyi job family slug, e.g. "software-engineer", "product-manager", "data-scientist". |
| locationSlug | string | yes | One location slug (metro, state, country or region; not a city), e.g. "san-francisco-bay-area". Resolve it with search-locations first; for a city, use its parent metro. |
No output schema declared.
No examples provided.
get-salary-submission-by-id ~105
Get a single salary submission by its UUID: company, title, level, location, years of experience, offer date, base salary and total compensation. Every amount is in USD; originalCurrency is only the currency the salary was submitted in. Use the uuid from a search-raw-data-points row. Free limit: Base salary and total compensation only, in USD. REQUIRED arguments: uuid.
| Name | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | The unique uuid of the salary |
No output schema declared.
No examples provided.
get-vesting-schedules ~150
Get equity vesting schedules for one or more companies, decoded into structured data: per-year vesting percent and frequency (cliff/quarterly/monthly), whether there's a 1-year cliff, whether it's backloaded (e.g. Amazon 5/15/40/40) / frontloaded / linear, plus a plain-English description and vesting type (RSU, options). Pass company slugs (use search-companies to resolve names first). REQUIRED arguments: companySlugs. Array-typed arguments (companySlugs) must be passed as arrays, even for a single value.
| Name | Type | Req | Description |
|---|---|---|---|
| companySlugs | array | yes | Company slugs to fetch vesting schedules for. |
No output schema declared.
No examples provided.
search-all ~230
Search across ALL entity types at once (companies, job families, job titles, focus tags, locations, and industries) by passing searchText (required) and get a single ranked list, each result tagged with its type and slug/id. Use this when you don't yet know which track an entity belongs to, or to disambiguate an ambiguous name; once the type is known, prefer the type-specific tools (search-companies, search-job-titles, search-locations, search-job-families, search-focus-areas) for tighter results. If a match is found under a DIFFERENT entity type than the user expected, do not silently substitute it — surface that mismatch and confirm with the user before proceeding. REQUIRED arguments: searchText.
| Name | Type | Req | Description |
|---|---|---|---|
| excludeFamilyLikeTitles | boolean | – | When true, exclude TITLE results that are effectively the same as their job family. |
| limit | number | – | Max results to return (1–15). |
| searchText | string | yes | Free-text query to search across all entity types (companies, job families, job titles, focus tags, locations, industries). |
No output schema declared.
No examples provided.
search-companies ~160
Search companies using searchText input (required) and get their Levels.fyi slugs. Use this FIRST to resolve a company name (e.g. "Google", "Meta") into the slug that the benchmark tools require in their companySlugs filter. Also matches former names and aliases, so a renamed company is found under its old name. Returns an array of { name, slug } matches. If this returns no matches, fall back to search-all, which searches every entity type and applies a fuzzy fallback. REQUIRED arguments: searchText.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results to return (1–15). |
| searchText | string | yes | Company name to search for, current or former (e.g. "Google", "Pure Storage"). |
No output schema declared.
No examples provided.
search-companies-by-vesting ~231
Find companies by their equity vesting characteristics: vesting/equity type (e.g. "RSU"), vesting shape (frontloaded, backloaded like Amazon, linear, one/two/three_year, or extended 5+ years), total years, and whether there's a 1-year cliff. Returns matching companies (most data-rich first) with their decoded vesting schedules.
| Name | Type | Req | Description |
|---|---|---|---|
| hasCliff | boolean | – | Filter by whether the schedule has a 1-year cliff. |
| limit | number | – | Max companies to return (1–50). |
| maxYears | number | – | Maximum total vesting years. |
| minYears | number | – | Minimum total vesting years. |
| vestingPattern | string | – | Filter by vesting shape: frontloaded, backloaded (e.g. Amazon), linear (equal each year), one_year / two_year / three_year (total length), or extended (5+ years). |
| vestingType | string | – | Filter by vesting/equity type substring, e.g. "RSU", "Stock Options". |
No output schema declared.
No examples provided.
search-focus-areas ~152
Search focus tags (specializations within a role, e.g. "mobile-ios-android", "ml-ai", "devops", "security") using searchText input (required) and get their slugs. Use this to resolve a specialization into the focusTagSlugs the benchmark tools accept. Returns matching focus tags with their slugs. If this returns no matches, fall back to search-all, which searches every entity type and applies a fuzzy fallback. REQUIRED arguments: searchText.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results to return (1–15). |
| searchText | string | yes | Focus tag / specialization name to search for (e.g. "mobile", "ml", "devops"). |
No output schema declared.
No examples provided.
search-job-families ~164
Search job families / roles using searchText input (required) and get their Levels.fyi slugs. Use this to resolve a role name (e.g. "software engineer", "product manager", "data scientist") into the jobFamilySlug the benchmark tools require. Returns matching job families with their slugs. A specific title (e.g. "UX designer") is not a job family: if this returns no matches, use search-role-terms, which returns the title with its job family slug, then search-all. REQUIRED arguments: searchText.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results to return (1–15). |
| searchText | string | yes | Job family / role name to search for (e.g. "software engineer", "product"). |
No output schema declared.
No examples provided.
search-job-titles ~181
Search specific job titles by name. Each result includes its id (the titleId the benchmark tools accept in the jobTitleIds filter) and its parent job family, so use this to narrow a benchmark query to an exact title (e.g. "Forward Deployed Software Engineer") within a job family. Set excludeFamilyLikeTitles to drop titles that are effectively just the job family. If this returns no matches, fall back to search-all, which searches every entity type and applies a fuzzy fallback. REQUIRED arguments: searchText.
| Name | Type | Req | Description |
|---|---|---|---|
| excludeFamilyLikeTitles | boolean | – | When true, exclude titles that are effectively the same as their job family. |
| limit | number | – | Max results to return (1–15). |
| searchText | string | yes | Job title to search for (e.g. "forward deployed engineer", "iOS engineer"). |
No output schema declared.
No examples provided.
search-jobs ~650
Search open jobs on Levels.fyi, with the pay range each posting states. Returns { jobs, totalMatchingJobs, nextOffset }; each job has its title, company, locations, work arrangement, posting date, pay range, url (the Levels.fyi job page) and applyUrl. Simplify the user's request to role names and terms that appear in job posts. Pass at most one location per call, and only one the user named: resolve it with search-locations, and never use the user's own position. Resolve companies and job families with search-companies and search-job-families. If nothing matches, widen the search (drop a filter or simplify the query) and try once more; if there's still nothing, say so rather than listing unrelated jobs. When the user asks for jobs without saying which role, offer to search from their Levels.fyi profile. If they agree, call get-profile and draft the query from its title, job family and location (locationSlug). Before searching, show the user the values you will use and ask them to confirm or change them: a profile describes the job they have, not necessarily the one they want next. Do not call get-profile without asking. Results come up to 2 jobs per company; limit counts companies, except with a single companySlug, where it counts jobs. A page can hold fewer than limit; keep paging while nextOffset is not null. Put each job's url on its title and keep URLs complete. When the client shows results as cards, do not list them again in text: summarise the patterns instead. Call get-job for a posting's full description. REQUIRED arguments: query. Array-typed arguments (e.g. companySlugs, jobFamilySlugs) must be passed as arrays, even for a single value.
| Name | Type | Req | Description |
|---|---|---|---|
| companySlugs | array | – | Company slugs from search-companies, at most 5. |
| employmentTypes | array | – | – |
| jobFamilySlugs | array | – | Job family slugs from search-job-families, at most 10. |
| limit | number | – | Companies per page (default 10, max 25). Each returns up to 2 jobs; with one companySlug it is jobs per page. |
| locationSlug | string | – | One location slug from search-locations (city, metro, state or country). Only a location the user named. |
| minBaseCompensation | number | – | Minimum base salary, compared with the top of the posting's range as posted (most postings are USD). |
| minMedianTotalCompensation | number | – | Minimum total compensation, compared with the top of the posting's range. |
| offset | number | – | Pass the previous result's nextOffset to get the next page. |
| postedWithinDays | number | – | Only jobs posted in the last N days. |
| query | string | yes | Role names and terms that appear in job posts, e.g. "backend engineer" or "product designer fintech". Simplify the user's words; leave out locations and salary. |
| sortBy | string | – | – |
| standardLevels | array | – | – |
| workArrangements | array | – | – |
No output schema declared.
No examples provided.
search-locations ~264
Search locations (countries, metro areas / DMAs, and US states) using searchText input (required) and get their Levels.fyi slugs. Use this to resolve a location name (e.g. "San Francisco", "United States") into the slug the benchmark tools require in their locationSlugs filter. Each result includes its location type. Optionally restrict to one type. Without a type, a name that matches no country, metro or state is searched as a city: each city comes with its parent location (a metro, or the country where there is none), which is the slug to pass to the pay tools. Several places can share a name: pick the one the user means from context, and ask if unsure. If this returns no matches, fall back to search-all, which searches every entity type and applies a fuzzy fallback. REQUIRED arguments: searchText.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results to return (1–15). |
| searchText | string | yes | Location name to search for (country, metro area / DMA, or US state). |
| type | string | – | Restrict results to one location type. Omit to search countries, metros (DMAs), and states together. Cities are only returned with type "city". |
No output schema declared.
No examples provided.
search-raw-data-points ~275
Get the newest individual salary submissions for a job family, optionally narrowed to one location and/or one company. Each row has the company, title, level, location, years of experience, base salary and total compensation. Every amount is in USD; originalCurrency is only the currency the salary was submitted in. Returns { total, rows }; total counts matches up to 250, and only the newest rows are returned. Free limit: The 3 newest submissions, with base salary and total compensation only. No text search, level, years-of-experience, sort or paging. Pass canonical slugs (jobFamilySlug, locationSlug, countrySlug, companySlug): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug.
| Name | Type | Req | Description |
|---|---|---|---|
| companySlug | string | – | A company slug, e.g. "google". Resolve it with search-companies first. |
| jobFamilySlug | string | yes | A Levels.fyi job family slug, e.g. "software-engineer", "product-manager", "data-scientist". |
| locationSlug | string | – | One location slug (city, metro, state, country or region), e.g. "san-francisco-bay-area". Resolve it with search-locations first. |
No output schema declared.
No examples provided.
search-role-terms ~131
Resolve a role term by searching job families, job titles, and focus tags TOGETHER in one call. Use this when you're unsure whether a term (e.g. "ML engineer", "mobile", "SRE") is a job family, a specific title, or a specialization — each result is tagged with its type and slug so you can feed the right one to the benchmark tools. REQUIRED arguments: searchText.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results to return (1–15). |
| searchText | string | yes | Role term to resolve across job families, titles, and focus tags. |
No output schema declared.
No examples provided.
search-top-companies ~217
Get the top-paying companies for a job family within one country, ranked by median (p50) yearly total compensation in USD. Returns up to 10 companies with their median. Companies with too few submissions are left out. Free limit: Median (p50) total compensation for the top companies in one country. No sample size, level or years-of-experience filter. Pass canonical slugs (jobFamilySlug, locationSlug, countrySlug, companySlug): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, countrySlug.
| Name | Type | Req | Description |
|---|---|---|---|
| countrySlug | string | yes | A COUNTRY location slug, e.g. "united-states", "india", "united-kingdom". Resolve it with search-locations first; cities, metros and states are rejected. |
| jobFamilySlug | string | yes | A Levels.fyi job family slug, e.g. "software-engineer", "product-manager", "data-scientist". |
No output schema declared.
No examples provided.
send-feedback ~201
Report wrong or missing Levels.fyi data, or a missing feature, to the Levels.fyi team. Call it only after telling the user what you will send and getting their agreement. Never include personal details; contactEmail only when the user wants a reply and gives it. Returns { received, id }. REQUIRED arguments: kind, message.
| Name | Type | Req | Description |
|---|---|---|---|
| companySlug | string | – | The company the report is about, as a slug. |
| contactEmail | string | – | Only when the user wants a reply and gives this address. |
| jobFamilySlug | string | – | The job family the report is about, as a slug. |
| kind | string | yes | What the report is about. |
| locationSlug | string | – | The location the report is about, as a slug. |
| message | string | yes | What is wrong or missing, in the user’s words. No personal details. |
| toolName | string | – | The tool whose result the report is about. |
No output schema declared.
No examples provided.
upload-resume ~327
Add or replace the signed-in user's resume on Levels.fyi. When the user shares their resume or asks for help with a job search, you can offer this once; call it only after the user asks or agrees. Before you call, tell the user Levels.fyi uses it to fill in their profile and match them with jobs and recruiters. Never upload a resume for another person. Accepts a PDF (at most 5 pages) or a DOCX, at most 4.5 MB. Set fileType from the file's actual extension: the upload must be a file of that format, or it cannot be read. Returns two ways to upload: - upload: a presigned S3 upload that expires in 10 minutes. Use it only if you can read the user's file and make HTTP requests yourself, e.g. a terminal agent with the file on disk: send an HTTP POST with multipart/form-data to upload.url, with every entry of upload.fields as form fields, followed by the file in a field named "file". A 201 response means it worked; a larger file is refused. - webUploadUrl: otherwise, give the user this link to upload the file themselves after signing in. Never paste the resume's text or contents anywhere else. The resume is parsed in the background, usually within a couple of minutes. Call get-profile afterwards to check it; until parsing finishes, it can still show the previous resume. REQUIRED arguments: fileType.
| Name | Type | Req | Description |
|---|---|---|---|
| fileType | string | yes | The resume file's format: "pdf" or "docx". |
No output schema declared.
No examples provided.
How do I install the Levels.fyi MCP server?
Levels.fyi is a hosted endpoint at https://mcp.levels.fyi/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.levels.fyi
claude mcp add --transport http fyi-levels-levels-fyi 'https://mcp.levels.fyi/'
What is the Levels.fyi MCP server?
Levels.fyi is an MCP server listed in the public MCP registry as fyi.levels/levels-fyi. Salary, level and job data from 1M+ pay reports. Benchmark pay, evaluate offers, search open jobs. This page covers its hosted endpoint (https://mcp.levels.fyi/).
Is the Levels.fyi MCP server safe to use?
Levels.fyi scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Levels.fyi MCP server expose?
Levels.fyi exposes 30 tools: get-permissions, get-salary-percentiles, get-salaries-by-company-level, search-raw-data-points, get-company, and 25 more. Their descriptions and schemas cost roughly 7,192 tokens of context every time the server is loaded.
Does the Levels.fyi MCP server require authentication?
No. We connected to Levels.fyi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Levels.fyi MCP server still maintained?
Levels.fyi is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.