BLS OEWS
REMOTE · BLS-OEWS.1102TOOLS.COM · 2 COMPONENTS
BLS Occupational Employment and Wage Statistics market wages, bundled; no API key. 8 tools.
Available components
Last scanned (14 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Data and Analytics
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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. 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 Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1569 tokens (~196/item across 8 items; 8 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 Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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.
- 4 Nov 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.
- 2 Nov 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.
- 31 Oct 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.
- 29 Oct 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.
- 27 Oct 26 +1
- Server version: 1.1.5 → 1.1.6 functional
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 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.
- 22 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
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 5 Nov 2026 · Probed https://bls-oews.1102tools.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=1102tools.com | CN=WE1,O=Google Trust Services,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6a698f3a61f3487a1322958209e30445 |
| SANs: 1102tools.com, bls-oews.1102tools.com, *.bls-oews.1102tools.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 bls-oews.1102tools.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| 1102tools.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://bls-oews.1102tools.com/mcp | Verified | 200 | |
| http (plaintext) | http://bls-oews.1102tools.com/mcp | Inconclusive | 405 |
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 →
compare_metros ~134
Compare wages for one occupation across multiple metro areas. Pass a list of 5-digit MSA codes (e.g., ['47900', '42660', '12580'] for DC, Seattle, Baltimore). Returns the specified wage measure for each metro. Use list_common_metros() to find codes. datatype: '04' (Annual Mean, default), '13' (Median), '03' (Hourly Mean). Up to 50 metros per call.
| Name | Type | Req | Description |
|---|---|---|---|
| datatype | – | – | – |
| metro_codes | array | yes | – |
| occ_code | – | yes | – |
| year | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
compare_occupations ~92
Compare wages across multiple occupations in one location. Pass a list of 6-digit SOC codes. Returns the specified wage measure for each occupation. Use list_common_soc_codes() to find codes. Up to 50 occupations per call.
| Name | Type | Req | Description |
|---|---|---|---|
| area_code | – | – | – |
| datatype | – | – | – |
| occ_codes | array | yes | – |
| scope | string | – | – |
| year | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
detect_latest_year ~63
Report the OEWS data year this server answers from. OEWS releases annually in spring, and this server bundles the current release. Every tool defaults to that year. When BLS publishes a newer release, a new package version bundles it.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_data_status ~67
Report which OEWS release this server answers from and where it came from. Returns the bundled data year and release, the BLS source files with their SHA-256 and publication dates, the retrieval date, and row counts. No API key is used or needed.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_wage_data ~630
Get wage data for an occupation by SOC code. This is the primary tool for querying BLS OEWS wage statistics. occ_code: 6-digit SOC code without dash (e.g., '151252' for Software Developers, '131082' for Project Management Specialists). See list_common_soc_codes() for common mappings. scope + area_code: - 'national': no area_code needed (all US) - 'state': area_code = 2-digit state FIPS (e.g., '51' for VA, '11' for DC) - 'metro': area_code = 5-digit MSA code (e.g., '47900' for DC metro, '42660' for Seattle). See list_common_metros() for codes. industry: 6-digit industry code for national-only breakdowns. '000000' = all industries (default). Common: '541000' (Professional, Scientific, and Technical Services), '541500' (Computer Systems Design and Related Services), '999100' (Federal Executive Branch (OEWS Designation)). Industry breakdowns only work with scope='national'. Federal IT staff mostly fall under 15-1299 (Computer Occupations, All Other), so 999100 with 15-1252 rests on few employees. datatypes: list of 2-digit codes. Default uses IGCE set: - '04' = Annual Mean Wage - '13' = Annual Median - '11' = Annual 10th Percentile - '15' = Annual 90th Percentile Hourly percentiles: '03' (Mean), '06' (10th), '07' (25th), '08' (Median), '09' (75th), '10' (90th). Annual percentiles: '11' (10th), '12' (25th), '13' (Median), '14' (75th), '15' (90th). Other: '01' (Employment); '16' (Employment per 1,000 Jobs) and '17' (Location Quotient) exist at state/metro scope only. '02' (Employment RSE) and '05' (Mean Wage RSE) are relative standard errors in percent, a measure of each estimate's reliability. Data year defaults to the OEWS release bundled with this server (get_data_status reports it). Do NOT pass the current calendar year: OEWS publishes about a year in arrears. Other years are rejected. Special values ('-', '*', '#') mean BLS did no…
| Name | Type | Req | Description |
|---|---|---|---|
| area_code | – | – | – |
| datatypes | – | – | – |
| industry | – | – | – |
| occ_code | – | yes | – |
| scope | string | – | – |
| year | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
igce_wage_benchmark ~414
Get wage benchmarks formatted for IGCE development. Returns annual and hourly wages at the mean and the 10th, 25th, median, 75th, and 90th percentiles (25th/75th are the usual junior/senior anchors), plus estimated burdened hourly rates using the specified burden multiplier range. Hourly figures are BLS's published hourly wages (annual / 2080 only where BLS publishes no hourly wage). Also returns the cell's employment and relative standard errors (reliability) and flags thin estimates. Wages are point-in-time estimates for the OEWS reference month (wage_period in the response), not current rates: escalate them to the period of performance before pricing. BLS wages are BASE wages (no fringe, overhead, G&A, or profit). Multiply by a burden factor to estimate fully-loaded rates: - 1.5x-1.7x: lean contractor - 1.8x-2.2x: mid-range professional services (default) - 2.0x-2.5x: large contractor with clearance overhead - 2.5x-3.0x: high-overhead (SCIF, deployed) The burdened range should roughly align with GSA CALC+ ceiling rates for comparable labor categories. If CALC+ >> burdened BLS, the role may require specialized skills or clearance overhead. Document the gap. Burden multipliers must be positive and burden_low <= burden_high. Reasonable range: 1.3 (lean) to 4.0 (high-overhead/clearance).
| Name | Type | Req | Description |
|---|---|---|---|
| area_code | – | – | – |
| burden_high | number | – | – |
| burden_low | number | – | – |
| occ_code | – | yes | – |
| scope | string | – | – |
| year | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_common_metros ~83
List common metro area MSA codes for wage lookups. Use these codes with get_wage_data(scope='metro', area_code=...). Pass the 5-digit MSA code (the tool auto-pads to 7 characters). For the full MSA list: https://www.bls.gov/oes/current/msa_def.htm
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_common_soc_codes ~86
List common SOC code mappings for federal IT and professional services. Use these codes with get_wage_data() and other tools. SOC codes are 6 digits without a dash (e.g., '151252' not '15-1252'). For the full SOC list: https://www.bls.gov/oes/current/oes_stru.htm
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the BLS OEWS MCP server?
BLS OEWS is a hosted endpoint at https://bls-oews.1102tools.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 · bls-oews.1102tools.com
claude mcp add --transport http com-1102tools-bls-oews-mcp 'https://bls-oews.1102tools.com/mcp'
What is the BLS OEWS MCP server?
BLS OEWS is an MCP server listed in the public MCP registry as com.1102tools/bls-oews-mcp. BLS Occupational Employment and Wage Statistics market wages, bundled; no API key. 8 tools. This page covers its hosted endpoint (https://bls-oews.1102tools.com/mcp).
Is the BLS OEWS MCP server safe to use?
BLS OEWS scores 69 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 BLS OEWS MCP server expose?
BLS OEWS exposes 8 tools: compare_metros, compare_occupations, detect_latest_year, get_data_status, get_wage_data, and 3 more. Their descriptions and schemas cost roughly 1,569 tokens of context every time the server is loaded.
Does the BLS OEWS MCP server require authentication?
No. We connected to BLS OEWS without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BLS OEWS MCP server still maintained?
BLS OEWS is still listed as active in the MCP registry. We last reached this channel on 5 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 BLS OEWS MCP server?
VerifyMCP ran 12 checks on BLS OEWS, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about BLS OEWS: HTTPS. 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.