Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.smythmyke/govtoolspro-mcp-server

NPM · GOVTOOLSPRO-MCP-SERVER

Workflow tools for federal contractors: go/no-go scoring, incumbent intel, recompete, NECO.

0 this week 84 Trust /100

Last scanned (16 hours ago)

Scores higher than 75% of npm servers

Category CRM and Sales

Trust breakdown (7 categories)

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 Security98
  • 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
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 162 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1633 tokens (~163/item across 10 items; 10 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
What we tested

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 →

Changelog

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.

  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 −2
    • Stability: pass → 0.90 functional
  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 2 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 31 Oct 26 +1
    • Security disclosure: unverified → pass ▲ functional
Diagnostics

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 21 Nov 2026 · Analysed npm/govtoolspro-mcp-server@0.1.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~1,633 tokens

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 →

Tool Tokens
analyze_award_patterns ~131

Analyze how contracts in a NAICS are typically awarded: award-size distribution, competition mix (full & open / limited / sole-source), bid intensity (single-bid rate, expected bidders), contract vehicles, and pricing types. From public USAspending + FPDS data. Costs 3 credits.

NameTypeReqDescription
naicsCodestringyesNAICS code (required).
pscCodestring–Optional PSC code to narrow the analysis.
statestring–Optional 2-letter place-of-performance state filter.
yearsnumber–Lookback in years (default ~3).
NameTypeReqDescription
awardSizeDistributionarray––
bidStatisticsobject|null––
competitionobject|null––
contractVehiclesarray––
pricingTypesarray––

No examples provided.

analyze_market ~112

Full market-intelligence snapshot for a NAICS: 5-year federal spending trend, industry size (Census), top contractors with market share + HHI concentration, set-aside distribution, geographic distribution, and contract-vehicle usage. From public USAspending + Census data. Costs 5 credits.

NameTypeReqDescription
naicsCodestringyesNAICS code (required).
pscCodestring–Optional PSC code for sharper competitor filtering.
setAsidestring–Optional set-aside context.
NameTypeReqDescription
concentrationobject|null––
contractVehiclesarray––
federalSharePctnumber|null––
geographicDistributionarray––
industryContextobject|null––
recentLargeAwardsarray––
setAsideDistributionarray––
spendingTrendarray––
topContractorsarray––

No examples provided.

balance ~44

Return the current GovToolsPro credit balance and subscription status for the authenticated account. Free — exercises auth end-to-end. The extension and the API draw from the same shared credit pool.

Input schema present but exposes no named parameters.

NameTypeReqDescription
balancenumberyesCurrent total credit balance.
subscriptionobject|null–Active subscription, or null if none.
subscriptionCreditsnumber–Credits from the active subscription.
topupCreditsnumber–Credits purchased as one-off top-ups.
totalPurchasednumber–Lifetime credits purchased.
totalUsednumber–Lifetime credits consumed.

No examples provided.

find_incumbents ~211

Identify the likely current incumbent(s) for a solicitation using public USAspending + FPDS award data. Returns the primary incumbent (name, award value, period of performance), FPDS competition signals (offers received, set-aside, sole-source flags), and an anticipated next-award start date. Deterministic, free. FPDS failures degrade gracefully (USAspending half stays intact).

NameTypeReqDescription
anticipatedStartDatestring–ISO date overriding the responseDeadline-based anticipated-start calculation.
fpdsMaxResultsnumber–Max FPDS contracts (default 50, max 100).
limitnumber–Max USAspending contracts (default 50, max 100).
solicitationobjectyesSolicitation context. naicsCode is REQUIRED. Optional: pscCode, agency, subAgency, office, placeOfPerformance, title, responseDeadline.
yearsnumber–USAspending lookback in fiscal years (default 5, max 10).
NameTypeReqDescription
anticipatedStartDatestring––
fpdsErrorstring|null––
fpdsResultsnumber––
otherIncumbentsarray––
primaryIncumbentobject|null––
usaspendingResultsnumber––

No examples provided.

find_partners_near ~155

Find potential teaming partners / subcontractors near a solicitation's place of performance via Google Places. Given a capability keyword and a geocodable address, returns nearby businesses ranked by proximity, enriched (top results) with phone and website. Deterministic, free. Verify capabilities, certifications, and eligibility independently before relying on results.

NameTypeReqDescription
addressstringyesPlace of performance — any geocodable string, e.g. 'Arlington, VA' or a full street address.
keywordstringyesIndustry/capability term, e.g. 'IT support', 'electrical contractor', 'janitorial services'.
radiusnumber–Search radius in miles (default 25, max 100).
NameTypeReqDescription
businessesarrayyes–
placeOfPerformanceobject––
totalResultsnumberyes–

No examples provided.

get_solicitation ~218

Retrieve a single SAM.gov solicitation's structured fields by notice ID (or, best-effort, by solicitation number). Returns title, solicitation number, type, NAICS, PSC, set-aside, place of performance, response deadline (with timezone), points of contact, description, and attachment download links. Deterministic, free — pulls from SAM.gov's public opportunity records. This is the entry point for a workflow: feed the returned fields into score_go_no_go, find_incumbents, or find_partners_near.

NameTypeReqDescription
includeAttachmentsboolean–Include attachment download links (default true). Set false to skip the extra lookup.
noticeIdstring–32-character hex SAM.gov notice ID (the ID in a sam.gov/opp/<id>/view URL). Primary, most reliable input.
solicitationNumberstring–Solicitation number (e.g. '140P6026Q0003'). Best-effort fallback — resolved via SAM.gov search; provide noticeId when you have it.
NameTypeReqDescription
archiveDatestring––
archivedboolean––
attachmentsarray––
cancelledboolean––
descriptionstring––
linkstring––
modifiedDatestring––
naicsCodestring––
naicsCodesarray––
noticeIdstringyes–
placeOfPerformanceobject|null––
pointOfContactarray––
postedDatestring––
pscCodestring––
responseDeadlinestring––
responseTimeZonestring––
setAsidestring––
solicitationNumberstring––
titlestringyes–
typestring––
typeLabelstring––

No examples provided.

lookup_labor_rates ~132

Benchmark federal labor rates for a NAICS code and/or a specific labor category. Returns GSA CALC awarded ceiling rates (min/median/max by category) plus BLS OEWS wage data with a +55% government wrap (loaded hourly) estimate. Free. Public GSA + BLS data — verify allowable rates against the RFP.

NameTypeReqDescription
laborCategorystring–Specific labor category for a direct GSA search, e.g. 'program manager', 'software engineer'.
naicsCodestring–NAICS code — maps to GSA labor categories + BLS SOC occupations.
NameTypeReqDescription
blsWagesarrayyes–
gsaRatesarrayyes–
summaryobject––

No examples provided.

lookup_neco_data ~181

Fetch and parse a Navy NECO (Navy Electronic Commerce Online) solicitation page into structured data — solicitation number, title, response deadline, NSN/line items, buyer contact, set-aside, and document links. Deterministic scrape of the public neco.navy.mil site, free. No other govcon MCP exposes NECO data. Pass the full NECO URL when you have it (most reliable); solicitationNumber alone is best-effort.

NameTypeReqDescription
hkeystring–Optional NECO hkey — improves solicitationNumber resolution.
necoUrlstring–Full NECO solicitation URL (https://www.neco.navy.mil/...). Primary, most robust input.
solicitationNumberstring–Navy solicitation number. Best-effort — the main NECO page may require an hkey to resolve.
NameTypeReqDescription
dataobject––
requestedUrlstringyes–
summaryobjectyes–

No examples provided.

predict_recompete ~196

Discover federal contracts expiring within a window (recompete opportunities) via public USAspending data, optionally enriched with procurement-history signals (all-options-exercised, offers received, set-aside, competition type). Filter by NAICS, PSC, state, value, and keywords. Returns contracts with days-until-expiration and urgency. Deterministic, free. Expiration/option signals reflect reported data and may lag.

NameTypeReqDescription
enrichboolean–Enrich top results with procurement history (default true).
enrichCountnumber–How many to enrich (default 10, max 25).
filtersobject–All optional. Narrow the recompete search.
limitnumber–Results per page (default 25, max 100).
pagenumber–Page number (default 1).
sortOrderstring–Sort by End Date (default 'desc').
NameTypeReqDescription
contractsarrayyes–
hasMoreboolean––
totalCountnumberyes–

No examples provided.

score_go_no_go ~253

Score a federal solicitation as GO / NO-GO (0-100) against a company profile. Detects hard blockers (CMMC certification gaps, geographic/OEM constraints, set-aside ineligibility), scores NAICS match, past performance, and capability fit, and returns a recommendation with red flags and reasons. Deterministic decision-support — no AI, free. Pass the analyzed solicitation documents (from your extension or an analyze-solicitation step) plus your company profile.

NameTypeReqDescription
documentAnalysesarrayyesAnalyzed solicitation documents (required, at least one). Each item is the structured analysis of a solicitation document (summary, classification with naicsCode/setAside, valueAndScope with placeOfP…
incumbentDataobject–Optional incumbent context, e.g. { primaryIncumbent } from find_incumbents.
profileobject–Company profile to score against: company (legalName, address.state), industryCodes.primaryNaics, businessTypes (smallBusiness, sdvosb, ...), capabilities (coreCompetencies, cmmcStatus.level).
solicitationDataobject–Optional extra solicitation context, e.g. { responseDeadline }.
NameTypeReqDescription
blockersarray––
categoryScoresobject––
reasonsarray––
recommendationstringyesGO / NO-GO / REVIEW.
scorenumberyes0-100 fit score.

No examples provided.

Install

How do I install the io.github.smythmyke/govtoolspro-mcp-server server?

io.github.smythmyke/govtoolspro-mcp-server runs locally as an npm package, launched with npx -y govtoolspro-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · govtoolspro-mcp-server

# add to Claude Code
claude mcp add smythmyke-govtoolspro-mcp-server -- npx -y govtoolspro-mcp-server
Common questions

What is the io.github.smythmyke/govtoolspro-mcp-server server?

io.github.smythmyke/govtoolspro-mcp-server is listed in the public MCP registry as io.github.smythmyke/govtoolspro-mcp-server. Workflow tools for federal contractors: go/no-go scoring, incumbent intel, recompete, NECO. This page covers its npm package (govtoolspro-mcp-server).

Is the io.github.smythmyke/govtoolspro-mcp-server server safe to use?

io.github.smythmyke/govtoolspro-mcp-server scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.smythmyke/govtoolspro-mcp-server server expose?

io.github.smythmyke/govtoolspro-mcp-server exposes 10 tools: balance, get_solicitation, score_go_no_go, find_incumbents, find_partners_near, and 5 more. Their descriptions and schemas cost roughly 1,633 tokens of context every time the server is loaded.

Is the io.github.smythmyke/govtoolspro-mcp-server server still maintained?

io.github.smythmyke/govtoolspro-mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.smythmyke/govtoolspro-mcp-server server under?

io.github.smythmyke/govtoolspro-mcp-server 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 io.github.smythmyke/govtoolspro-mcp-server server?

VerifyMCP ran 16 checks on io.github.smythmyke/govtoolspro-mcp-server, 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.