FedFinder MCP server
Federal contracting data as tools your agent can call: open solicitations, 21M award records, 885k registered entities, 1M contracting people, and grants.
Why not just call SAM.gov
You can, and it is free. The reason people stop is that the raw feeds do not answer the question you actually asked.
SAM.gov's active flag does not mean "open for bid". A notice with no response
deadline stays active forever, because the retirement sweeps key on the
deadline. Measured on FedFinder's production corpus, one row in five that the
raw feed calls open is a notice SAM already archived, including one posted in
2008 and archived twelve days later. Grants have the same shape: SAM assistance
listings describe standing programmes with no application and no deadline, and
they outnumber the real opportunities.
Every tool here filters that out before it answers. That is the product.
Setup
pip install fedfinder-mcp
export FEDFINDER_API_KEY=fedf_live_...
Get a key at https://app.fedfinder.net. Standalone API access is $49/month: 30 requests per minute, 50,000 calls per month.
Claude Desktop
{
"mcpServers": {
"fedfinder": {
"command": "fedfinder-mcp",
"env": { "FEDFINDER_API_KEY": "fedf_live_..." }
}
}
}
Tools
| tool | scope required |
|---|---|
search_opportunities |
opportunities:read |
get_opportunity |
opportunities:read |
search_state_opportunities |
state-opportunities:read |
search_contracts |
contracts:read |
search_vendors |
vendors:read |
search_people |
people:read (Intel) |
search_grants |
grants:read |
search_pre_rfp_signals |
pre-rfp-signals:read (Intel) |
list_captures |
captures:read |
list_win_loss |
winloss:read |
api_info |
any |
Keys are scoped. A tool whose scope your key lacks returns a message naming the
missing scope rather than an opaque 403. Omit scopes when minting a key to
grant all read scopes.
Things worth knowing
State filtering is asymmetric on purpose. SAM omits place of performance on about half of all notices, so a bare equality test hides most of the market. A row with no stated performance location falls back to the contracting office's state; a row that states a different location is never rescued by its office, because a DC office buys work performed in Guam and treating those as the same fact would swap a silent miss for a confident error.
Names are stored inverted at the source. "Smith, John", not "John Smith".
search_people handles it; if you are joining against another system, do not
assume the ordering matches.
Grant close dates are free text. Several formats arrive, some as vague as a bare year. Treat anything you cannot parse as "rolling or unknown" rather than inventing a date, which would close a grant that is still live.
Municipal money is not here. City and county programmes are not tracked by any platform, FedFinder included. If that is what you need, a human has to call the city.
Rate limits
30 requests per minute on the standalone plan, higher on Pro and Intel. A 429
means wait, not retry immediately. api_info reports what your key carries.
Metadata
Release files for fedfinder-mcp 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| fedfinder_mcp-1.0.0.tar.gz | 7.2 kB | Without provenance | Details for fedfinder_mcp-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fedfinder_mcp-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for fedfinder_mcp-1.0.0-py3-none-any.whl |
Total release size: 14.1 kB
Release files / fedfinder_mcp-1.0.0.tar.gz
| Download URL | fedfinder_mcp-1.0.0.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
38461b1d9675d50fb1948a34e44e24264d7a386adeb1d29c71817d50f0c92b23
|
|
BLAKE2b-256 checksum How to use checksums |
fe88767e6438ca2ab2d95c977417347a76fe01098feaeffcb0643a3c49686480
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.15
|
Release files / fedfinder_mcp-1.0.0-py3-none-any.whl
| Download URL | fedfinder_mcp-1.0.0-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
82a1f00853098c98ca782d4bbbd01f32a0f8ef968349111e91915143a7bebb9e
|
|
BLAKE2b-256 checksum How to use checksums |
4eb2986e0368fecb3ec527874c60eb91f5c8ecab25dc2429ac555ece2fc7c9d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.15
|
Security for fedfinder-mcp 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.