Is Federal Compass MCP safe to use?

Federal Compass MCP has an HVTrust score of 47.7/100 (Grade D), ranked #487 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Federal Compass MCP?

Federal Compass MCP scores 47.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 12 GitHub stars and is categorized under MCP Servers.

Federal Compass MCP

skivuha/federal-compass-mcp

Your AI compass from private sector to federal career — MCP server for USAJobs API

MCP Servers TypeScript Grade D Listed MIT

47.7/100

Rank #487 of 1283

Compare Federal Compass MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-05 · 7d ago

Recent change

Rank +1

Is Federal Compass MCP safe? Federal Compass MCP scores 47.7/100 (Grade D), ranked #487 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.8/10; 91% of recent commits are signed; last pushed 2026-08-05. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#164 Coolify MCP — 48.0 (D) → #165 GitMCP — 47.7 (D) → #167 Enquire MCP — 47.7 (D) → #168 BLS OEWS — 47.6 (D) →

Quick Trust Read

What Would Improve It

Expose more independent signals, such as package metadata, provenance, or public usage evidence.

Recent Changes

2026-08-10

Rank Moved

Rank dropped 18 spots (#470 → #488)

2026-08-08

Newly Listed

First tracked at rank #467

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.8/10. Tighten the weakest checks to improve public safety evidence.

Compare with another agent Get email alerts for Federal Compass MCP View MCP Servers Report missing data

39.8

Activity sub-score · out of 100

#166

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars

Forks

Last Push

2026-08-05

7 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #488

Analysis

HVTrust Dimensions vs MCP Servers

47.7 / 100 · 67.0% confidence

Federal Compass MCP MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

18.0 / 25

13.0 above avg 5.0

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.7 above avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

12.6 / 17

3.8 above avg 8.8

Maintenance60% last-push freshness · 40% commit activity

12.7 / 20

in line with avg 12.4

AdoptionLog-scaled stars · package downloads

2.7 / 20

3.1 below avg 5.8

Activity Inputs

39.8 / 100

StarsRepository reach

6.7 / 30

FreshnessLast push recency

24.0 / 25

ActivityRecent commits

7.5 / 25

CommunityFork signal

1.4 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

4.8 / 10

OpenSSF Scorecard · scanned Aug 8, 2026

Signed Commits

91%

of last 100 commits verified

Token-Permissions 0

Code-Review 0

Maintained 10

Binary-Artifacts 10

Dependency-Update-Tool 10

Dangerous-Workflow 10

Pinned-Dependencies 6

CII-Best-Practices 0

Packaging -1

Vulnerabilities 0

License 10

Signed-Releases -1

SAST 0

Branch-Protection -1

Fuzzing 0

Security-Policy 0

Contributors 3

CI-Tests 7

Is Federal Compass MCP safe?

Public trust evidence for Federal Compass MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Federal Compass MCP publish package provenance?

Yes. Federal Compass MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Federal Compass MCP have an OpenSSF Scorecard?

Federal Compass MCP has an OpenSSF Scorecard score of 4.8/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Federal Compass MCP actively maintained?

Actively maintained. The repository was pushed to within the last 7 day(s).

What license does Federal Compass MCP use?

Federal Compass MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Federal Compass MCP's commits signed?

90% of the last 100 commits to Federal Compass MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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

Scored in HVTrust

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 Server Support

high confidence

Implemented

Federal Compass MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-10

Rank Moved

Rank dropped 18 spots (#470 → #488)

2026-08-08

Newly Listed

First tracked at rank #467

GitHub → npm: federal-compass-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/federal-compass-mcp.svg)](https://hvtracker.net/agents/federal-compass-mcp)
            
HTML:
            <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

Data sources
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.3 · Raw JSON