
Gsa Calc MCP server
online · 100% uptimeGSA CALC+ ceiling labor rates — what vendors may charge per hour under GSA schedule contracts, for…
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Gsa Calc yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Gsa Calc tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Gsa Calc compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 73/100
- higher than 39% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 37 ms
- faster than 94% of 30,031 servers
Release history: 6 versions in the registry since 2026-09-14, latest 2026-11-02, typically one every 4 days.
Install Gsa Calc in Claude Code, Cursor or VS Code
claude mcp add --transport http gsa-calc https://gateway.pipeworx.io/gsa-calc/mcp
What the publisher says
From the Gsa Calc repository's README, as published. We do not edit it. Read it on GitHub
gsa-calc
GSA CALC+ ceiling labor rates — the maximum hourly price a vendor may charge the US government for a labor category under a GSA schedule contract. Used to benchmark rates before negotiating.
Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.
Tools
Filters on all three: minexperience / maxexperience, education, worksite, businesssize, securityclearance, minrate / maxrate, sortby / sortdir.
Auth
None. api.gsa.gov/acquisition/calc/v3 is keyless — no api.data.gov key is needed, unlike gsa-auctions and gsaperdiem which do use PLATFORMDATAGOV_KEY.
Data sources
current contract year, not a negotiated or paid price.
- CALC+ Quick Rate API —
- Endpoint: https://api.gsa.gov/acquisition/calc/v3/api/ceilingrates/
- Rates come from GSA MAS contracts; the figure is the ceiling rate for the
The older calc.gsa.gov/api/rates/ path found in pre-2026 write-ups is dead (404). calc.gsa.gov now redirects to a landing page on buy.gsa.gov.
Upstream behaviour worth knowing
All measured live on 2026-08-28. The running API differs from its documentation in ways that change answers, so they are listed rather than assumed.
An unrecognised filter value is silently ignored. filter=worksite:Contractor (capital C) and filter=nonsensefield:zzz each return the complete unfiltered result set with HTTP 200 — the same total as sending no filter at all. A caller who asks for contractor-site rates and gets a confident answer may be reading every rate in the schedule. This pack validates every enum and refuses an unknown value** rather than forwarding it; the error names the accepted set. A refused call is recoverable, a silently unfiltered benchmark is not.
The vocabularies are case-sensitive in opposite directions, and there are three of them. worksite matches lowercase only (contractor); Contractor is ignored. business_size matches uppercase only (S); s returns zero rows. And the same field is spelled differently depending on where you read it — filter BA, JSON response Bachelors, CSV export small business for filter S. The pack accepts human spellings ("bachelors", "small business", "contractor facility") and maps them.
minyearsexperience is an equality filter, not a minimum. Upstream, minyearsexperience:5 returns only rows requiring exactly 5 years (667 of 4,396 for "software engineer"). Our minexperience means what a caller means by it — 5 or more — and maps to experiencerange:5,99 (2,561 rows, with requirements from 5 to 15+ years).
page and pagesize are both ignored. The JSON endpoint returns exactly 20 rows for every query; page=1, page=2 and page=3 return byte-identical rows, and pagesize=300 returns 20. export=y returns the complete matching set as CSV instead, so this pack computes percentiles from the export — basedon in every ratesummary states how many rows the numbers came from. The JSON endpoint's own total caps at 10,000 with relation: "gte"; the export count is exact.
Accept: text/csv returns 406. The export responds Content-Type: text/csv, but asking for that type is the one request it refuses. Send /.
Reading the result
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-10-03downgradeA → Bscore 73
- 2026-09-19restoreB → Ascore 87
Gsa Calc: common questions
- Is Gsa Calc MCP server safe?
- Mostly: it is graded B (73/100). Read the Gsa Calc safety report
- How do I install Gsa Calc?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Gsa Calc need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Gsa Calc maintained?
- The last commit was 39 days ago (2026-09-26). The latest release is v0.2.1.
- Is Gsa Calc up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Gsa Calc compare with other MCP servers?
- safety score 73/100 (higher than 39% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 37 ms (faster than 94% of 30,031 servers). Full comparison.