FedSalary: official pay data
REMOTE · FEDSALARY.COM
Official pay statistics for any job and place, offer checks and two-offer comparisons.
Available components
Last scanned (19 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1775 tokens (~295/item across 6 items; 6 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_pay" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- “find_jobs” added an optional parameter “pay_basis” cosmetic
- “match_jobs” reworded the description of “min_pay” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.33 ▲ functional
- 17 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.23 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 16 Nov 26 +1
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.23 ▲ functional
- 15 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1344 → 1739 ▼ functional
- New tool “match_jobs” functional
- “find_jobs” added an optional parameter “remote_only” cosmetic
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 21 Nov 2026 · Probed https://fedsalary.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fedsalary.com | CN=YE1,O=Let's Encrypt,C=US | 21 Nov 2026 | 19 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 659f773b190d415000deed918e4c7771d18 |
| SANs: *.fedsalary.com, fedsalary.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fedsalary.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| fedsalary.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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://fedsalary.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://fedsalary.com/api/mcp | HTTPS enforced | 301 | https://fedsalary.com/api/mcp |
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 →
check_pay Check a pay offer or range ~172
Where a job offer's pay, or a posted pay range, sits on the official pay distribution for the same job and place: the percentile span, the median, US take-home pay at the midpoint after federal and state tax, and for US metro areas which Department of Labor wage level (entry to fully competent) the pay meets. Same places as get_pay.
| Name | Type | Req | Description |
|---|---|---|---|
| job | string | yes | Job title, FedSalary slug or occupation code. |
| max | number | – | High end of the range (optional). |
| min | number | yes | Low end of the range, or the only figure. |
| place | string | yes | us, ca, uk, a US state or large metro area, a Canadian province or a UK region. |
| unit | string | – | year or hour. UK places take year only. |
No output schema declared.
No examples provided.
compare_offers Compare two US job offers ~212
Two US job offers, each a pay figure in a state or one of the 50 largest metro areas, compared after federal income tax, Social Security, Medicare and state income tax, then after local prices (BEA regional price parities, rent included). Returns take-home pay, take-home at national prices, which offer is worth more and by how much, and the salary each place would need to match the other. With a job, also where each offer sits on the official pay distribution. City and county income taxes are not included.
| Name | Type | Req | Description |
|---|---|---|---|
| a_pay | number | yes | Offer A's pay. |
| a_place | string | yes | Offer A's place: a US state or large metro area. |
| b_pay | number | yes | Offer B's pay. |
| b_place | string | yes | Offer B's place. |
| job | string | – | Optional job title or slug, to place each offer on the official distribution. |
| unit | string | – | year or hour, for both offers (default year). |
No output schema declared.
No examples provided.
find_jobs Find current job openings with their pay ~455
Current job openings in the US and Canada from employers' own job boards and US federal announcements from USAJOBS (read through their documented APIs, refreshed weekly), matching keywords and a place. Each result: title and employer as posted, places, posting date, the pay range when the employer published one, and when it did not, the official BLS median for the occupation in the US state named (national for US remote jobs); for published US ranges, where the range sits on the official distribution; and the link to apply on the employer's own site. Results are newest first or by published pay. Coverage is strongest for technology, finance, startups and remote work; many hospitals, retailers and state and local governments are not included yet, so few or no results does not mean no such jobs exist. No job descriptions; FedSalary takes no applications.
| Name | Type | Req | Description |
|---|---|---|---|
| federal_only | boolean | – | true = only US federal job announcements (from USAJOBS; apply on USAJOBS). |
| keywords | string | – | Words matched against the job title and employer, all of which must match (data analyst, product manager, Stripe). |
| min_pay | number | – | Minimum yearly pay in USD: the top of the published range must reach it (Canadian ranges converted). Jobs without published pay are left out when this is set. |
| pay_basis | string | – | With min_pay, require the published annual minimum (year) or hourly minimum (hour, compared to min_pay / 2,080). Omit for the top of the annualized range. |
| place | string | – | A US state (texas or TX), a US metro area or large city (austin), remote (US remote jobs), canada, a Canadian province (ontario) or a large Canadian city (toronto). Leave out for everywhere. |
| published_pay_only | boolean | – | true = only jobs that publish a pay range. |
| remote_only | boolean | – | true = only jobs the employer marks remote, on top of any place (remote jobs open to Texas: place texas, remote_only true). For remote jobs anywhere in the US, set place to remote instead. |
| sort | string | – | new (default) or pay. |
No output schema declared.
No examples provided.
get_pay Official pay for a job ~220
Official pay statistics for one job in one place: median, 10th to 90th percentiles, employment, the publisher and reference period, take-home pay where the site shows it, and for US states and metro areas the U.S. Department of Labor's four wage levels (entry to fully competent). Covers the US (national, every state, the 50 largest metro areas), Canada (national, provinces) and the UK (national; regions are a table on the national answer). Returns the page's Markdown copy with a citation line.
| Name | Type | Req | Description |
|---|---|---|---|
| job | string | yes | Job title as people say it (registered nurse, software engineer), a FedSalary page slug (registered-nurses) or an occupation code (SOC 29-1141, NOC 31301). |
| place | string | – | us, ca or uk for a whole country (default us); a US state (texas or TX); a large US metro area (austin, seattle); a Canadian province (ontario); a UK region (london). |
No output schema declared.
No examples provided.
match_jobs Jobs that fit a person's experience ~317
Current US and Canadian openings ranked by how closely they fit a person's work history: the job titles they have held, years of experience, skills, place and minimum pay. Each title is read as the occupation that most employers' current postings with that title fall under; openings are then ranked by title match, same or neighbouring occupation, skills named in the posting's title and seniority fit (intern and junior roles drop for experienced people, senior roles for people starting out). Each result says why it is listed, with the pay range the employer published or the official median when it published none, and the link to apply on the employer's site. No job descriptions are read, so a skill counts only when the employer put it in the job title. Nothing about the person is stored. Same coverage limits as find_jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| include_remote | boolean | – | With a place: also include remote jobs (default true). |
| min_pay | number | – | Minimum of the employer’s posted yearly salary in USD. Hourly estimates and jobs without published salaries are excluded. |
| place | string | – | A US state (texas or TX), a large US metro area (austin), canada or a Canadian province. Leave out for everywhere. |
| skills | array | – | Skills or specialties, twelve at most (ICU, pediatrics, Python). |
| titles | array | – | Job titles the person has held, most recent first, three at most (registered nurse, charge nurse). |
| years_experience | number | – | Years of work experience. |
No output schema declared.
No examples provided.
take_home US take-home pay after tax ~213
Take-home pay on a US salary or hourly wage in a state or one of the 50 largest metro areas: federal income tax, Social Security, Medicare, the state's income tax and the state's employee payroll contributions where it has them (disability insurance, paid family leave, long-term care, employee unemployment insurance), using the state's newest published rules with the federal rules of the same year. Single filer, no dependents, standard deduction, wage income only; city and county income taxes are not included. Returns the yearly, monthly and per-paycheck amounts with each tax line and a link to the state's calculator page.
| Name | Type | Req | Description |
|---|---|---|---|
| pay | number | yes | Pay before tax: a yearly salary, or an hourly wage with unit hour. |
| place | string | yes | A US state (ohio or OH) or a large US metro area (austin, seattle). us gives federal taxes only. |
| unit | string | – | year (default) or hour; hourly pay is annualized at 2,080 hours. |
No output schema declared.
No examples provided.
How do I install the FedSalary: official pay data MCP server?
FedSalary: official pay data is a hosted endpoint at https://fedsalary.com/api/mcp, 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 · fedsalary.com
claude mcp add --transport http com-fedsalary-official-pay 'https://fedsalary.com/api/mcp'
What is the FedSalary: official pay data MCP server?
FedSalary: official pay data is an MCP server listed in the public MCP registry as com.fedsalary/official-pay. Official pay statistics for any job and place, offer checks and two-offer comparisons. This page covers its hosted endpoint (https://fedsalary.com/api/mcp).
Is the FedSalary: official pay data MCP server safe to use?
FedSalary: official pay data scores 71 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 FedSalary: official pay data MCP server expose?
FedSalary: official pay data exposes 6 tools: get_pay, check_pay, compare_offers, find_jobs, match_jobs, take_home. Their descriptions and schemas cost roughly 1,589 tokens of context every time the server is loaded.
Does the FedSalary: official pay data MCP server require authentication?
No. We connected to FedSalary: official pay data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FedSalary: official pay data MCP server still maintained?
FedSalary: official pay data is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the FedSalary: official pay data MCP server?
VerifyMCP ran 13 checks on FedSalary: official pay data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.