io.github.atlasbyauro/fairsession
REMOTE · FAIRSESSION.COM · SCANNED SEP 21
Live healthcare pay data: advertised ranges by role/state/city, offer checks, transparency scores.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 397 tokens (~99/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_pay_range" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 5 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
How do I install the io.github.atlasbyauro/fairsession MCP server?
io.github.atlasbyauro/fairsession is a hosted endpoint at https://fairsession.com/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 · fairsession.com
claude mcp add --transport http atlasbyauro-fairsession 'https://fairsession.com/mcp'
{
"mcpServers": {
"atlasbyauro-fairsession": {
"url": "https://fairsession.com/mcp"
}
}
} {
"servers": {
"atlasbyauro-fairsession": {
"type": "http",
"url": "https://fairsession.com/mcp"
}
}
} [mcp_servers.atlasbyauro-fairsession] url = "https://fairsession.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"atlasbyauro-fairsession": {
"type": "remote",
"url": "https://fairsession.com/mcp",
"enabled": true
}
}
} openclaw mcp add atlasbyauro-fairsession --url 'https://fairsession.com/mcp' --transport streamable-http
mcp_servers:
atlasbyauro-fairsession:
url: "https://fairsession.com/mcp" {
"McpServers": {
"atlasbyauro-fairsession": {
"Transport": "http",
"Url": "https://fairsession.com/mcp"
}
}
} assistant mcp add atlasbyauro-fairsession -t streamable-http -u 'https://fairsession.com/mcp'
{
"mcpServers": {
"atlasbyauro-fairsession": {
"type": "http",
"url": "https://fairsession.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 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.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
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 Sept 2026 · Probed https://fairsession.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fairsession.com | CN=WE1,O=Google Trust Services,C=US | 27 Aug 2026 | 25 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 2db2ccbe7d2ad71b1320a926b33e9f25 |
| SANs: fairsession.com, www.fairsession.com, *.www.fairsession.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fairsession.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| fairsession.com. | absent | 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://fairsession.com/mcp | Verified | 200 | |
| http (plaintext) | http://fairsession.com/mcp | Inconclusive | 302 | /about/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_offer ~125
Where a specific job offer sits against advertised pay for a role in a state: percentile vs live posting ranges, with an honest fallback to national data when the state sample is under 25 disclosed postings. Advertised ranges are not settled offers.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Offer amount, e.g. 42.5 (hourly) or 78000 (annual) |
| basis | string | yes | Pay basis of the offer |
| role | string | yes | Role, e.g. 'RN', 'BCBA' |
| state | string | yes | Two-letter US state code |
No output schema declared.
No examples provided.
get_employer_score ~66
An employer's Pay Transparency Score: the percentage of its active postings that state pay, computed weekly from its own public career board. Includes posting counts and advertised ranges by role. Scores cannot be bought.
| Name | Type | Req | Description |
|---|---|---|---|
| employer | string | yes | Employer name, e.g. 'Mount Sinai' |
No output schema declared.
No examples provided.
get_pay_range ~102
Advertised pay range for a healthcare role in a US state, computed weekly from employers' own live job postings (never surveys). Returns hourly and salary ranges separately, sample sizes, city-level ranges where available, and honest labels when data is thin.
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | yes | Role, e.g. 'RN', 'BCBA', 'physical therapist', 'financial analyst' |
| state | string | yes | Two-letter US state code, e.g. NY |
No output schema declared.
No examples provided.
list_employers ~34
All employers Fair Session currently tracks and scores, with Transparency Scores, plus the identified-but-not-yet-ingested pipeline.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.atlasbyauro/fairsession MCP server?
io.github.atlasbyauro/fairsession is an MCP server listed in the public MCP registry as io.github.atlasbyauro/fairsession. Live healthcare pay data: advertised ranges by role/state/city, offer checks, transparency scores. This page covers its hosted endpoint (https://fairsession.com/mcp).
Is the io.github.atlasbyauro/fairsession MCP server safe to use?
io.github.atlasbyauro/fairsession 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 io.github.atlasbyauro/fairsession MCP server expose?
io.github.atlasbyauro/fairsession exposes 4 tools: get_pay_range, check_offer, get_employer_score, list_employers. Their descriptions and schemas cost roughly 327 tokens of context every time the server is loaded.
Does the io.github.atlasbyauro/fairsession MCP server require authentication?
No. We connected to io.github.atlasbyauro/fairsession without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.atlasbyauro/fairsession MCP server still maintained?
io.github.atlasbyauro/fairsession is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.