Gsa Calc
NPM · @PIPEWORX/MCP-GSA-CALC · 2 COMPONENTS
GSA CALC+ ceiling labor rates — what vendors may charge per hour under GSA schedule contracts, for…
Available components
Last scanned (15 hours ago)
Scores higher than 83% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-gsa-calc). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 20 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1355 tokens (~451/item across 3 items; 3 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 Management80
- Stability observed for 24 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 22 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 18 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.
- 16 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.
- 14 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.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +6
- Source repository: unverified → pass ▲ security
- 9 Nov 26 −5
- Provenance: pass → unverified ▼ security
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 22 Nov 2026 · Analysed npm/@pipeworx/mcp-gsa-calc@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-gsa-calc |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-gsa-calc/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637386016 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7857093cdaa15dd347c3619d3a05541c1edd9fd6f6e87a508baacb151a1afa08e3e631306dc89c5a856000e4a464a3cf352d49b16f3fc8dd17eb2591d |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
gsa_labor_rates ~500
GSA schedule hourly labor rates for a job title — the ceiling rate vendors may charge the government under a GSA MAS contract. Use this to benchmark what a labor category costs: "typical GSA hourly rate for a project manager", "what do senior software engineers bill under MAS", "GSA schedule rate for a data scientist with 10 years experience". Returns individual rates with vendor name, contract number, SIN, education and experience requirements, plus a price summary (min, p25, median, p75, max) computed across EVERY matching rate, not just the ones returned. Filter by experience, education, worksite, business size, security clearance and price band. Example: gsa_labor_rates({ labor_category: "software engineer", min_experience: 5 })
| Name | Type | Req | Description |
|---|---|---|---|
| business_size | string | – | "S" for small business or "O" for other than small. "small" and "large" also work. |
| education | string | – | Minimum education: HS, AA, BA or MA. Plain spellings work too ("bachelors", "high school"). Combine with | for several, e.g. "BA|MA". |
| labor_category | string | yes | Job title to benchmark, e.g. "software engineer", "project manager". Partial match against contract labor categories, which are free text — prefer a short phrase over a long one. |
| limit | number | – | How many individual rates to return, 1-200 (default 25). The summary always covers every matching rate regardless of this. |
| max_experience | number | – | Maximum years of experience required, inclusive. |
| max_rate | number | – | Only rates at or below this hourly price, USD. |
| min_experience | number | – | Minimum years of experience required, inclusive. Means "this many OR MORE" — mapped to the upstream range filter, because the upstream field of the same name is an exact match. |
| min_rate | number | – | Only rates at or above this hourly price, USD. |
| security_clearance | string | – | "yes" to only rates requiring a clearance, "no" to exclude them. |
| sort_by | string | – | Sort field (default current_price). |
| sort_dir | string | – | Sort direction (default asc). |
| worksite | string | – | Where the work is performed: "contractor" (vendor site) or "customer" (government site). |
No output schema declared.
No examples provided.
gsa_rate_stats ~394
Price statistics only for a GSA schedule labor category — min, 25th percentile, median, 75th percentile and max hourly ceiling rate across every matching contract rate, with no individual rows. Use when you want the benchmark number rather than the listings: "what is the median GSA rate for a business analyst", "p75 hourly rate for cybersecurity engineers with a clearance". Same filters as gsa_labor_rates. Example: gsa_rate_stats({ labor_category: "project manager", education: "BA", min_experience: 10 })
| Name | Type | Req | Description |
|---|---|---|---|
| business_size | string | – | "S" for small business or "O" for other than small. "small" and "large" also work. |
| education | string | – | Minimum education: HS, AA, BA or MA. Plain spellings work too ("bachelors", "high school"). Combine with | for several, e.g. "BA|MA". |
| labor_category | string | yes | Job title to benchmark, e.g. "project manager". |
| max_experience | number | – | Maximum years of experience required, inclusive. |
| max_rate | number | – | Only rates at or below this hourly price, USD. |
| min_experience | number | – | Minimum years of experience required, inclusive. Means "this many OR MORE" — mapped to the upstream range filter, because the upstream field of the same name is an exact match. |
| min_rate | number | – | Only rates at or above this hourly price, USD. |
| security_clearance | string | – | "yes" to only rates requiring a clearance, "no" to exclude them. |
| sort_by | string | – | Sort field (default current_price). |
| sort_dir | string | – | Sort direction (default asc). |
| worksite | string | – | Where the work is performed: "contractor" (vendor site) or "customer" (government site). |
No output schema declared.
No examples provided.
gsa_vendor_rates ~405
Every GSA schedule labor rate published by one contractor — what this specific company charges the government per hour, across its labor categories, with contract numbers and SINs. Use for "what rates does Booz Allen have on its GSA schedule" or to compare one vendor against the market median. Example: gsa_vendor_rates({ vendor: "DIGNITAS TECHNOLOGIES" })
| Name | Type | Req | Description |
|---|---|---|---|
| business_size | string | – | "S" for small business or "O" for other than small. "small" and "large" also work. |
| education | string | – | Minimum education: HS, AA, BA or MA. Plain spellings work too ("bachelors", "high school"). Combine with | for several, e.g. "BA|MA". |
| limit | number | – | How many rates to return, 1-200 (default 25). |
| max_experience | number | – | Maximum years of experience required, inclusive. |
| max_rate | number | – | Only rates at or below this hourly price, USD. |
| min_experience | number | – | Minimum years of experience required, inclusive. Means "this many OR MORE" — mapped to the upstream range filter, because the upstream field of the same name is an exact match. |
| min_rate | number | – | Only rates at or above this hourly price, USD. |
| security_clearance | string | – | "yes" to only rates requiring a clearance, "no" to exclude them. |
| sort_by | string | – | Sort field (default current_price). |
| sort_dir | string | – | Sort direction (default asc). |
| vendor | string | yes | Company name or a distinctive fragment of it, e.g. "DIGNITAS" or "Booz Allen". Vendor names are recorded in full legal form on the contract. |
| worksite | string | – | Where the work is performed: "contractor" (vendor site) or "customer" (government site). |
No output schema declared.
No examples provided.
How do I install the Gsa Calc MCP server?
Gsa Calc runs locally as an npm package, launched with npx -y @pipeworx/mcp-gsa-calc. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-gsa-calc
claude mcp add pipeworx-io-gsa-calc -- npx -y @pipeworx/mcp-gsa-calc
What is the Gsa Calc MCP server?
Gsa Calc is an MCP server listed in the public MCP registry as io.github.pipeworx-io/gsa-calc. GSA CALC+ ceiling labor rates, what vendors may charge per hour under GSA schedule contracts, for… This page covers its npm package (@pipeworx/mcp-gsa-calc).
Is the Gsa Calc MCP server safe to use?
Gsa Calc scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Gsa Calc MCP server expose?
Gsa Calc exposes 3 tools: gsa_labor_rates, gsa_rate_stats, gsa_vendor_rates. Their descriptions and schemas cost roughly 1,299 tokens of context every time the server is loaded.
Is the Gsa Calc MCP server still maintained?
Gsa Calc is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Gsa Calc MCP server under?
Gsa Calc declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Gsa Calc MCP server?
VerifyMCP ran 16 checks on Gsa Calc, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.