Federal Compass MCP
Your AI compass from private sector to federal career — MCP server for USAJobs API
Is Federal Compass MCP safe? Promising trust profile, but some evidence still deserves review.
Compare Federal Compass MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Federal Compass MCP scores 68.7/100 (Grade B), ranked #404 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.8/10; 91% of recent commits are signed; no published advisory affects its latest release (federal-compass-mcp); last pushed 2026-10-21. Every point is earned from checkable signals — never paid placement. How scoring works →
How Federal Compass MCP could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 3.8 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Fuzzing 0 +10.9 → 79.6 B · #104 of 778
Chain of custody
Scanners check what the code says. This traces who ships Federal Compass MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/skivuha/federal-compass-mcp, MIT, last pushed 2026-10-21. 91% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 3.8/10 (scanned Nov 9, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies6
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 7CII-Best-Practices 0Code-Review 0Contributors 3Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 0Packaging -1Pinned-Dependencies 6SAST 0Security-Policy 0Signed-Releases -1Token-Permissions 0Vulnerabilities 0 -
Published packages Linked and attested
- npm federal-compass-mcp Source link points back to this repo Build provenance attested
-
What you install today No known advisories
Latest release checked: federal-compass-mcp 0.1.10. No published advisory affects it (OSV, checked 2026-11-09).
Changes to this chain
- 2026-09-23 Package provenance attestation detected
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Federal Compass MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Federal Compass MCP compares in MCP Servers
- #238 MCP Accessibility Scanner 68.7 ±0
- #239 Saga MCP 68.7 ±0
- #240 Federal Compass MCP 68.7 this agent
- #241 Brave Search MCP Server 68.6 −0.1
- #242 Amazon Ads MCP 68.6 −0.1
Bars show each HVTrust score; the tick marks Federal Compass MCP’s 68.7.
Where the 68.7 comes from
HVTrust dimensions vs the MCP Servers average
68.7 / 100 · 100.0% confidenceFederal Compass MCP MCP Servers average (778 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
32.9 / 100Common questions about Federal Compass MCP
Does Federal Compass MCP publish package provenance?
Does Federal Compass MCP have an OpenSSF Scorecard?
Is Federal Compass MCP actively maintained?
What license does Federal Compass MCP use?
Are Federal Compass MCP's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Federal Compass MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Federal Compass MCP?
For maintainers
HVTrust scores Federal Compass MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/federal-compass-mcp)
<a href="https://hvtracker.net/agents/federal-compass-mcp"><img src="https://hvtracker.net/badge/federal-compass-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON