ITC Prevailing Wage & Apprenticeship Guide
REMOTE · ITC-PWA-GUIDE.SITETIME.WORKERS.DEV
IRS prevailing wage & apprenticeship (PWA) rules for the clean-energy ITC: checks, cures, rates.
Available components
Last scanned (8 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 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 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 4355 tokens (~311/item across 14 items; 14 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 Management67
- Stability observed for 20 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 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.
- 1 Nov 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.
- 30 Oct 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.
- 27 Oct 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.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 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 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 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.
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://itc-pwa-guide.sitetime.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sitetime.workers.dev | CN=WE1,O=Google Trust Services,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 58035a7f242441010ef0066ae5d05bfa |
| SANs: sitetime.workers.dev, *.sitetime.workers.dev | ||||||
| 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 itc-pwa-guide.sitetime.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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://itc-pwa-guide.sitetime.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://itc-pwa-guide.sitetime.workers.dev/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 →
check_applicability Do PWA requirements apply to this project? ~600
Says whether a project must meet the prevailing wage and apprenticeship requirements to claim the increased (5x) credit, and which ones: the credit involved, when construction began (before January 29, 2023 is exempt for 30C, 45, 45Q, 45V, 45Y, 48, 48E and 179D; 45L, 45U, 45Z and 48C have no such exception), the one-megawatt exception for 45, 45Y, 48 and 48E (maximum net output under 1 MW AC by nameplate, aggregated across the energy project or across facilities with integrated operations; for DC generation the lesser of the DC nameplate sum or the first inverter), construction versus alteration or repair after placed in service (apprenticeship applies to construction only; prevailing wages continue 5 years for the ITC, 10 for the PTC), the applicable apprentice percentage (10 / 12.5 / 15%), whether the project is under section 48 or 48E, and for solar and wind the 2025 law’s termination dates (construction after July 4, 2026 must be placed in service by December 31, 2027).
| Name | Type | Req | Description |
|---|---|---|---|
| construction_began | string | yes | When construction began (YYYY-MM-DD), under the IRS beginning-of-construction rules (physical work test or 5% safe harbor). |
| credit | string | yes | The Code section claimed: 48 (energy credit), 48E (clean electricity investment credit), 45, 45Y, 45Q, 45V, 45Z, 45U, 45L, 179D, 30C or 48C. |
| dwelling_type | string | – | For 45L only: the kind of home (prevailing wage reaches only multifamily units). |
| max_net_output_mw_ac | number | – | Maximum net output in megawatts AC by nameplate, AGGREGATED: for section 48 the sum of every energy property in the energy project (1.48-13(e)(1)); for 48E and 45Y the sum of every same-technology fa… |
| placed_in_service | string | – | Placed-in-service date (YYYY-MM-DD), if known or planned. |
| technology | string | – | What the facility is: solar or wind (the 2025 law’s termination dates apply), storage, or other. |
| work_type | string | – | construction (default) or alteration_or_repair after the facility is placed in service. |
No output schema declared.
No examples provided.
check_apprentice_hours Labor-hours test and the apprenticeship cure ~373
The apprenticeship labor-hours requirement for one facility (26 CFR 1.45-8(b)): qualified apprentices must perform the applicable percentage (10% if construction began before 2023, 12.5% in 2023, 15% from 2024) of total labor hours, counting every contractor and subcontractor, after excluding hours of foremen, superintendents, owners and executive/administrative/professional staff, and counting apprentice hours only within the daily ratio. Returns the required hours, the shortfall, and the cure the IRS accepts: $50 per shortfall hour ($500 with intentional disregard), including participation failures (an employer with 4+ individuals and no apprentice: its labor hours divided by its number of laborers and mechanics).
| Name | Type | Req | Description |
|---|---|---|---|
| construction_began | string | yes | When construction began (YYYY-MM-DD or a year): sets the percentage. |
| counted_apprentice_hours | number | yes | Hours worked by qualified (registered) apprentices that are within the daily ratio. Use check_daily_ratio to find them. |
| good_faith_hours | number | – | Apprentice hours covered by denied or unanswered good-faith requests (1.45-8(f)(1)); they count as apprentice hours. |
| intentional_disregard | boolean | – | true if the failure was knowing or willful (the IRS decides); the rate becomes $500 an hour. |
| participation_failures | array | – | Employers with four or more individuals on the facility and no qualified apprentice (each adds a participation shortfall). |
| total_labor_hours | number | yes | Total labor hours of construction, alteration or repair on the facility by all laborers and mechanics (every employer), apprentices included; hours of foremen, superintendents, owners and 541-exempt… |
No output schema declared.
No examples provided.
check_daily_ratio Daily apprentice-to-journeyworker ratio ~267
The ratio requirement (26 CFR 1.45-8(c)): on each day, for one employer and one occupation on the job site, the number of apprentices may not exceed what the registered program’s apprentice-to-journeyworker ratio allows for the journeyworkers present (or the ratio for the facility’s area). Give the program ratio and, for each day, the headcounts of journeyworkers and apprentices on site (the controlling input) with each apprentice’s hours; the tool returns the apprentice hours that count toward the percentage and the excess hours that do not (they stay in total labor hours and must be paid the full journeyworker prevailing rate: 1.45-7(b)(7)(iii), 29 CFR 5.5(a)(4)(i)). With hours only and no headcounts it prorates on hours, marked as an interpretation.
| Name | Type | Req | Description |
|---|---|---|---|
| days | array | yes | One entry per day for one employer and occupation. |
| ratio_apprentices | integer | – | Apprentices side of the program ratio (default 1). |
| ratio_journeyworkers | integer | – | Journeyworkers side of the program ratio (default 1). A 1:1 program = 1 and 1; 2 apprentices per journeyworker = 2 and 1. |
No output schema declared.
No examples provided.
check_good_faith_request Good Faith Effort Exception: does a request qualify? ~381
Judges a request for apprentices under the Good Faith Effort Exception (26 CFR 1.45-8(f)(1)): a written request (electronic or registered mail) to a registered apprenticeship program covering the facility’s area and occupation, sent at least 45 days before the apprentices are needed (14 days for a later request to the same program), with the dates, occupation, location, number, expected hours, contact and a statement of intent to employ. Denied, or unanswered for 5 business days, it stands in for the apprentices for its period, up to 365 days (366 across a leap year). Returns the lead-time check, the response status, how long the exception runs and when to request again.
| Name | Type | Req | Description |
|---|---|---|---|
| later_request_to_same_program | boolean | – | true if this is a later request to a program already asked once (14-day lead time instead of 45). |
| needed_from_date | string | – | When the apprentices were asked to start (YYYY-MM-DD): coverage runs from here. |
| needed_through_date | string | – | The last day of the employment period requested (YYYY-MM-DD), if the request named one. |
| received_date | string | – | When the program received it (YYYY-MM-DD), if different: the five business days run from receipt (1.45-8(f)(1)(i)(C)). |
| request_date | string | yes | When the request was sent (YYYY-MM-DD): the send date for email, the delivery date on the receipt for registered mail. |
| response | string | – | The program’s answer so far (default none). |
| response_date | string | – | When the program answered (YYYY-MM-DD), if it did. |
| today | string | – | The date to judge from (YYYY-MM-DD); defaults to the response date or the request date. |
No output schema declared.
No examples provided.
check_prevailing_wage Is this pay compliant, and what does a shortfall cost? ~682
Compares pay for one classification with the Davis-Bacon prevailing rate (basic hourly rate + fringe from the wage determination; look it up with lookup_wage_determination) and, if short, computes the IRS cure: the shortfall (x3 for intentional disregard), interest at the Federal short-term rate + 6 points, and the $5,000 per-worker penalty ($10,000 for intentional disregard), with the penalty waivers (corrected by the quarter deadline and either no more than 10% of pay periods short or no more than 5% short; or work under a qualifying project labor agreement). Cash plus bona fide fringe contributions together must reach base plus fringe (29 CFR 5.31).
| Name | Type | Req | Description |
|---|---|---|---|
| cash_rate_paid | number | yes | Cash wages paid ($/hour). |
| classification | string | – | The work classification (e.g. Electrician), for the record. |
| corrected_by_quarter_deadline | boolean | – | true if the back pay is made by the last day of the first month after the calendar quarter in which the failure occurred. |
| federal_short_term_rate_pct | number | – | Or give the Federal short-term rate (IRC 6621(b)) for the period yourself, in percent; the interest rate is that + 6 points. |
| fringe_paid_per_hour | number | – | Bona fide fringe benefit contributions per hour ($/hour): health, pension, insurance, vacation... not legally required benefits (29 CFR 5.29). |
| hours | number | – | Hours worked at this (short) pay: only the underpaid hours, to total the shortfall. |
| intentional_disregard | boolean | – | true if the failure was knowing or willful. |
| pay_periods_below | integer | – | Of those, how many were paid below the prevailing rate. |
| pay_periods_total | integer | – | Pay periods the worker was employed on the facility in the calendar year (for the small-failure waiver). |
| qualifying_project_labor_agreement | boolean | – | true if the work is under a pre-hire collective bargaining agreement for this project that meets 1.45-7(c)(6)(ii) and back pay is made before the credit is claimed (no penalty). |
| required_base_rate | number | yes | The determination’s basic hourly rate for the classification ($/hour). |
| required_fringe_rate | number | – | The determination’s fringe benefit amount ($/hour); 0 if none. |
| wages_due_date | string | – | When the wages were due (YYYY-MM-DD): the server looks up that quarter’s Federal short-term rate (table through 2026-10-16) to show the interest rate. |
| workers | integer | – | How many laborers or mechanics were paid this way (the penalty is per worker). |
| year_required_wages | number | – | The amount required to be paid to this worker for the calendar year (or the part of it) during which they worked on the facility: the 5% test in 1.45-7(c)(6)(i)(B) runs over the year, not over the un… |
| year_wages_paid | number | – | What the worker was actually paid for that year on the facility (defaults to the year’s required wages less the shortfall entered). |
No output schema declared.
No examples provided.
count_participation Count the four: does this employer need an apprentice? ~218
The participation requirement (26 CFR 1.45-8(d)): a taxpayer, contractor or subcontractor that employs four or more individuals to perform construction, alteration or repair work on the facility, counted over the whole construction (not at one time), must employ at least one qualified apprentice there. Give the people one employer used on this facility with their roles; the tool says who counts toward the four (laborers, mechanics and apprentices do; a supervising foreperson, an exempt 20%+ managing owner and office staff do not; a working foreperson or superintendent over 20% manual duties who is not 541-exempt, or a nonexempt owner doing trade work, does under this server’s reading), whether an apprentice is required, and whose hours are out of the labor-hours denominator either way.
| Name | Type | Req | Description |
|---|---|---|---|
| employer | string | – | The company (taxpayer, contractor or subcontractor) these people work for. |
| people | array | yes | Everyone this employer used on the facility over the whole construction, one entry each. |
No output schema declared.
No examples provided.
fetch Fetch a document from this guide (for research assistants) ~79
Returns the full text of a document found with search: overview:<topic>, records:<requirement>, form7220, law2025, tennessee, or reg:<section>[(paragraph)] such as reg:1.45-8(d), which is read live from the eCFR.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A document id from search. |
No output schema declared.
No examples provided.
find_apprenticeship_programs Find registered apprenticeship programs to request apprentices from ~185
Registered apprenticeship programs a contractor can send a good-faith request to (26 CFR 1.45-8(f)(1)): a program whose area covers the facility and that trains the occupation. For Tennessee it reads the State Apprenticeship Agency’s live list of registered programs (program, occupation, participating employers, county) and filters by occupation and county; for other states it gives the apprenticeship.gov partner finder and the State office to contact. Occupation is matched as text, so "electric" finds Electrician programs.
| Name | Type | Req | Description |
|---|---|---|---|
| counties | array | – | County names to keep (e.g. ["Warren", "Van Buren"]); leave out for the whole state. |
| occupation | string | – | The trade, e.g. electrician, laborer, operating engineer, solar. |
| state | string | yes | Two-letter state, e.g. TN. |
No output schema declared.
No examples provided.
lookup_wage_determination Look up a Davis-Bacon wage determination (live, SAM.gov) ~254
Fetches a Davis-Bacon general wage determination live from SAM.gov: by number (e.g. TN20260124, newest modification unless a revision is given) or by state, county and construction type (Building, Residential, Heavy, Highway; utility-scale solar and wind farms are Heavy). Returns the determination’s counties, modifications and every classification’s basic rate and fringe, optionally filtered to one classification, with the SAM.gov page to cite. Use the determination in force when the contract was executed (26 CFR 1.45-7(b)). A classification that is missing needs DOL’s additional classification and rate (IRAprevailingwage@dol.gov).
| Name | Type | Req | Description |
|---|---|---|---|
| classification | string | – | Show only classifications matching this (e.g. electrician, laborer, crane). |
| construction_type | string | – | Building, Residential, Heavy or Highway (for a search). |
| county | string | – | County name (for a search), e.g. Van Buren. |
| number | string | – | A determination number like TN20260124. |
| revision | integer | – | A specific modification number (default: the newest on SAM.gov). |
| state | string | – | Two-letter state (for a search). |
No output schema declared.
No examples provided.
official_sources Official sources and where to find things ~73
The primary sources behind every answer here (IRS pages and FAQs, Form 7220, the Code, the regulations on eCFR, the Treasury decision with its preamble, DOL’s IRA page, SAM.gov wage determinations, apprenticeship.gov and the Tennessee apprenticeship agency), with one line on what each is for.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pwa_overview PWA overview: the rules in one place ~156
Start here. Explains the IRS prevailing wage and apprenticeship (PWA) requirements for the increased clean-energy credit (ITC under IRC 48 / 48E and the other IRA credits): what they are, when they apply (the 1 MW and January 29, 2023 exceptions), the prevailing wage rule, the three apprenticeship tests (labor-hours percentage, daily ratio, four-or-more participation), the good-faith exception, cures and penalties, records and Form 7220, with the regulation paragraph for every figure. Ask for one topic or all of them.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | all (default), what, prevailing_wage, apprenticeship, penalties, records, changes_2025 or sources. |
No output schema declared.
No examples provided.
read_regulation Read the regulation text (live, eCFR) ~435
Returns the current text of a paragraph of the governing regulations straight from the eCFR, with its citation and URL: 26 CFR 1.45-6, 1.45-7, 1.45-8, 1.45-12, 1.48-13, 1.48E-3 and the Labor rules they rest on (29 CFR 541.101 owner exemption, 5.5 apprentices on Davis-Bacon work, 5.31 fringe, 29.5 program standards). Give a paragraph like "(d)" or "(g)(7)" to read one part; leave it out for the whole section. Sections: 1.45-6 (the 5x increased amount and when PWA applies to it); 1.45-7 (who is paid, which wage determination, corrections and penalties, definitions); 1.45-8 (labor hours (b), ratio (c), participation (d), examples (e), good faith and cure (f), definitions (g)); 1.45-12 (the records a taxpayer must keep for prevailing wage and apprenticeship); 1.48-13 (how 1.45-7/-8 apply to the energy credit, the 1 MW exception, alteration and repair); 1.48E-3 (how 1.45-7/-8 apply to section 48E facilities and energy storage); 541.101 (the 20% equity, actively-managing owner who is a bona fide exempt executive); 5.5 (apprentices: ratio, rates, registration (paragraph (a)(4))); 5.31 (cash, fringe benefits or a combination); 29.5 (what a registered program must provide: ratios, supervision, wage schedules).
| Name | Type | Req | Description |
|---|---|---|---|
| paragraph | string | – | A paragraph such as (d), (g)(7) or (f)(1); shorthand g7 works. Leave out for the whole section. |
| section | string | yes | The section number, e.g. 1.45-8. |
No output schema declared.
No examples provided.
records_checklist Records to keep (and who keeps them) ~126
The records the regulations expect for the prevailing wage and apprenticeship requirements (26 CFR 1.45-12), as a checklist for a taxpayer, a prime contractor or a subcontractor, with how they may be kept (each company keeps its own unredacted records, or hands PII-redacted copies to the taxpayer or a vendor; unredacted records go to the IRS on request) and how they feed Form 7220.
| Name | Type | Req | Description |
|---|---|---|---|
| requirement | string | – | Which records (default both). |
| role | string | – | Whose checklist (default taxpayer: the credit claimant). |
No output schema declared.
No examples provided.
search Search this guide (for research assistants) ~160
Full-text search over this guide’s documents: the PWA overview sections, the records checklists, Form 7220, the 2025 law changes, the Tennessee agency, and the governing regulation sections (26 CFR 1.45-6, 1.45-7, 1.45-8, 1.45-12, 1.48-13, 1.48E-3; 29 CFR 541.101, 5.5, 5.31, 29.5). Returns ids to pass to fetch. A paragraph reference like "1.45-8(d)" finds that regulation. For calculations use the check_* tools instead.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A single query string. |
No output schema declared.
No examples provided.
How do I install the ITC Prevailing Wage & Apprenticeship Guide MCP server?
ITC Prevailing Wage & Apprenticeship Guide is a hosted endpoint at https://itc-pwa-guide.sitetime.workers.dev/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 · itc-pwa-guide.sitetime.workers.dev
claude mcp add --transport http ovanova-solar-itc-pwa-guide 'https://itc-pwa-guide.sitetime.workers.dev/mcp'
What is the ITC Prevailing Wage & Apprenticeship Guide MCP server?
ITC Prevailing Wage & Apprenticeship Guide is an MCP server listed in the public MCP registry as io.github.ovanova-solar/itc-pwa-guide. IRS prevailing wage & apprenticeship (PWA) rules for the clean-energy ITC: checks, cures, rates. This page covers its hosted endpoint (https://itc-pwa-guide.sitetime.workers.dev/mcp).
Is the ITC Prevailing Wage & Apprenticeship Guide MCP server safe to use?
ITC Prevailing Wage & Apprenticeship Guide scores 73 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 ITC Prevailing Wage & Apprenticeship Guide MCP server expose?
ITC Prevailing Wage & Apprenticeship Guide exposes 14 tools: pwa_overview, check_applicability, count_participation, check_apprentice_hours, check_daily_ratio, and 9 more. Their descriptions and schemas cost roughly 3,989 tokens of context every time the server is loaded.
Does the ITC Prevailing Wage & Apprenticeship Guide MCP server require authentication?
No. We connected to ITC Prevailing Wage & Apprenticeship Guide without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ITC Prevailing Wage & Apprenticeship Guide MCP server still maintained?
ITC Prevailing Wage & Apprenticeship Guide 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.