GSA Per Diem runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 15 Oct 2026.
GSA Per Diem access readiness, lodging, and meals and incidental expense rates. 7 tools.
What the code does
We read the source, 15 h ago · rules ccca72095570
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
- name: Open or update the failure issue
if: failure()
env:
PUSHED: ${{ steps.push.outcome }}
execFileSync(PYTHON, [join(ROOT, "deploy/gsa-perdiem/parity/build_corpus.py")], {cwd: PACKAGE, env: pythonEnv, stdio: ["ignore", "ignore", "inherit"]});
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Nothing serious here today
Today is the operative word: we check GSA Per Diem every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Alternatives to GSA Per Diem
same job, measured the same wayRead-only GCP tools for debugging incidents and finding cost savings
VMware incident timeline, root-cause routing, local case ledger; no vSphere access. 14 MCP tools.
Forward Deployed Engineering rules traced to real incidents. Agent pays per query, no account.
Read-only access to your Infrly services, deploys, logs, metrics and billing.
Connect AI coding tools to LogClaw incidents, logs, and anomaly detections.
Status pages and uptime monitoring: read status, monitors and incidents; open incidents.
AI bookkeeping for small business. Create invoices, log expenses, and check P&L by voice or text.
Measured readings on open-source dependencies: health, end-of-life, model prices, incidents.
GSA Per Diem — questions
Answers built from our own checks of this server.