A remote MCP server that gives an assistant federal contractor acquisition signals, a daily rising-contractor feed, and live US federal award search.
What you can do
Look up a named federal contractor's acquisition-likelihood signal profile, including a 0-100 score with reasoning, award velocity, multi-year trajectory, agency and NAICS mix, biggest win, set-aside footprint, and public SEC EDGAR ticker details where available. Retrieve the daily refreshed ranked feed of rising small and mid-size contractors flagged as likely M&A targets. Search live US federal awards by NAICS, agency, recipient, keyword, date and dollar range.
When to use it
Useful for market research, competitive intelligence, or M&A sourcing around US federal contractors, and for checking a specific contractor's growth momentum or searching awards by agency, NAICS or recipient.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables or headers are declared. The manifest declares no authentication, though the provider may still require access. Network access to the endpoint is needed.
Before you install
The acquisition-likelihood score is pattern-based and should be treated as a signal, not a prediction. Results draw on public sources such as USAspending.gov and SEC EDGAR and may be incomplete or lag behind. The tools are read-only lookups and searches.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.dropwatchhq%2Fgovcon-contractor-signals/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Given a federal contractor NAME, return its acquisition-likelihood / rising-contractor signal profile: a 0-100 pattern-based score with full reasoning, plus award-velocity, multi-year trajectory, agency/NAICS mix, biggest win, set-aside footprint, and (if public) SEC EDGAR ticker + recent corporate-event filings. Built on PUBLIC USAspending.gov + EDGAR data. Probabilistic leading-signal estimate — NOT certainty, NOT insider/MNPI, NOT investment advice.
Parametersnamerequired
rising_contractors
Return the current ranked 'Rising Contractors / Likely M&A Targets' feed — small/mid federal contractors showing the strongest leading acquisition signals, refreshed daily.
Parameterslimit
search_awards
Direct live search of US federal awards (USAspending.gov) by NAICS, agency, recipient, keyword, date and $ range.
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.