USASpending.gov
REMOTE · USASPENDING.1102TOOLS.COM · 2 COMPONENTS
USAspending.gov contracts, grants, loans, subawards, recipients, agencies, and federal accounts.
Available components
Last scanned (11 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 9933 tokens (~180/item across 55 items; 55 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 Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 55 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 55 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Server version: 1.0.28 → 1.0.29 functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 0
- Server version: 1.0.27 → 1.0.28 functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://usaspending.1102tools.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=1102tools.com | CN=WE1,O=Google Trust Services,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e31214ef89e3a47f0e81992d1f0aa6cb |
| SANs: 1102tools.com, usaspending.1102tools.com, *.usaspending.1102tools.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of usaspending.1102tools.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| 1102tools.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://usaspending.1102tools.com/mcp | Verified | 200 | |
| http (plaintext) | http://usaspending.1102tools.com/mcp | Inconclusive | 405 |
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 →
spending_by_category ~535
Aggregate spending by a dimension (top vendors, top agencies, top NAICS, etc.). The 'category' parameter controls the grouping dimension. Common uses: - category='recipient': top vendors for a filter set (vendor landscape analysis) - category='awarding_subagency': which contracting offices within an agency - category='naics': which work categories got the most spending - category='psc': which product/service codes got the most spending - category='state_territory': geographic distribution - category='cfda': grant assistance listings Note: recipient category returns vendor names in ALL CAPS and may contain duplicates (subsidiaries, rebrands, re-registrations). For precise market share, apply name normalization to the returned 'name' field. At least one filter is required. An unfiltered call would silently aggregate the entire USASpending database (all years, all agencies), which is never what a caller wants. date_type controls the transaction date window. Omitted (the default) or 'action_date', it selects transaction actions inside the window. 'date_signed' selects the associated award's first signing date; 'last_modified_date' selects transaction update dates. 'new_awards_only' retains in-window actions associated with awards first signed in the window. These are transaction obligation totals, not new-award counts: use new_awards_over_time for counts. Award search/count tools use a different default interval-overlap rule. date_type needs time_period_start and/or time_period_end. program_numbers filters assistance awards by assistance listing (CFDA) number, e.g. ['93.778'] for Medicaid; use it with award_type='grants', 'loans', 'direct_payments', or 'other'. autocomplete_cfda() finds numbers by program name.
| Name | Type | Req | Description |
|---|---|---|---|
| award_type | – | – | – |
| awarding_agency | – | – | – |
| awarding_subagency | – | – | – |
| category | string | yes | – |
| contract_pricing_type_codes | – | – | – |
| date_type | – | – | – |
| def_codes | – | – | – |
| extent_competed_type_codes | – | – | – |
| funding_agency | – | – | – |
| keywords | – | – | – |
| limit | integer | – | – |
| naics_codes | – | – | – |
| page | integer | – | – |
| program_numbers | – | – | – |
| psc_codes | – | – | – |
| recipient_name | – | – | – |
| set_aside_type_codes | – | – | – |
| time_period_end | – | – | – |
| time_period_start | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
spending_by_geography ~229
Geographic breakdown of spending. scope: 'recipient_location' (where the recipient is) or 'place_of_performance' (where the work happens). geo_layer: 'state', 'county', or 'district'. At least one filter is required. The API returns HTTP 500 on an empty filter set, so the requirement is enforced here with a clear error. program_numbers filters assistance awards by assistance listing (CFDA) number, e.g. ['93.778'] for Medicaid; use it with award_type='grants', 'loans', 'direct_payments', or 'other'. autocomplete_cfda() finds numbers by program name.
| Name | Type | Req | Description |
|---|---|---|---|
| award_type | string | – | – |
| awarding_agency | – | – | – |
| def_codes | – | – | – |
| funding_agency | – | – | – |
| geo_layer | string | – | – |
| naics_codes | – | – | – |
| program_numbers | – | – | – |
| psc_codes | – | – | – |
| scope | string | – | – |
| time_period_end | – | – | – |
| time_period_start | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
spending_by_subaward_grouped ~410
Find matching prime awards and their cumulative FFATA report totals. Filters select prime records, but subaward_count and subaward_obligation cover all reported subawards under each prime, not just subaward actions within time_period_start/end. This ranking is not a fiscal-period subaward ranking. For dated reports, pass a returned award_generated_internal_id to search_subawards(award_id=...), read every page, and retain action_date values inside the desired period. sort accepts: award_id, subaward_count, award_generated_internal_id, subaward_obligation. (These differ from search_subawards, which sorts by amount/action_date/etc.) Anything else returns HTTP 400 from the API. page_metadata.hasNext is worked out here: the endpoint itself always says false, even with more pages. Rows include primes with no subawards (subaward_count 0). subaward_obligation sums FFATA reports, which can repeat cumulative amounts, so a subaward_to_award_ratio above 1 is a reporting artefact, not more subcontracting than the prime. program_numbers filters assistance awards by assistance listing (CFDA) number, e.g. ['93.778'] for Medicaid; use it with award_type='grants', 'loans', 'direct_payments', or 'other'. autocomplete_cfda() finds numbers by program name.
| Name | Type | Req | Description |
|---|---|---|---|
| award_type_codes | – | – | – |
| awarding_agency | – | – | – |
| def_codes | – | – | – |
| funding_agency | – | – | – |
| limit | integer | – | – |
| naics_codes | – | – | – |
| order | string | – | – |
| page | integer | – | – |
| program_numbers | – | – | – |
| psc_codes | – | – | – |
| set_aside_type_codes | – | – | – |
| sort | – | – | – |
| time_period_end | – | – | – |
| time_period_start | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
spending_by_transaction ~314
Search at the transaction (modification) level. Unlike search_awards which returns one row per award, this returns one row per transaction (initial action plus every modification). Useful for tracking obligation events over time, ceiling adjustments, deobligations, and admin mods. recipient_uei is matched through the API's recipient text search (which covers name, UEI, and DUNS), so pass the plain 12-character UEI. Returns standard transaction fields: Action Date, Mod, Award ID, Action Type, Awarding Agency, Recipient Name. program_numbers filters assistance awards by assistance listing (CFDA) number, e.g. ['93.778'] for Medicaid; use it with award_type='grants', 'loans', 'direct_payments', or 'other'. autocomplete_cfda() finds numbers by program name.
| Name | Type | Req | Description |
|---|---|---|---|
| award_amount_max | – | – | – |
| award_amount_min | – | – | – |
| award_type | string | – | – |
| awarding_agency | – | – | – |
| funding_agency | – | – | – |
| keywords | – | – | – |
| limit | integer | – | – |
| naics_codes | – | – | – |
| order | string | – | – |
| page | integer | – | – |
| program_numbers | – | – | – |
| psc_codes | – | – | – |
| recipient_uei | – | – | – |
| set_aside_type_codes | – | – | – |
| sort | string | – | – |
| time_period_end | – | – | – |
| time_period_start | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
spending_over_time ~601
Aggregate spending amounts over time, grouped by fiscal year, quarter, or month. Use this to visualize spending trends, identify fiscal-year-end spikes, or compare spending patterns across years. Note: The API returns fiscal_year as a STRING. Cast to int for numeric comparisons. quarter and month are FISCAL periods (month 1 = October, quarter 1 = October-December). Buckets are clipped to the window, so a calendar-2025 window returns a partial fiscal_year '2025' (January- September only) and a partial '2026' (October-December); neither is that whole fiscal year. DoD contract actions are published 90 days late, so when the window reaches into the last 90 days and DoD is in scope the answer carries a data_note: those months are understated, so don't read them as a drop. awarding_agency must be a TOPTIER agency name ('Department of Defense'). Military departments are subtiers: pass awarding_subagency='Department of the Navy'. A non-toptier name in awarding_agency (or a subagency that does not belong to the given toptier) silently returns all-zero aggregates. At least one filter is required (the API rejects empty filter sets with HTTP 400). Typical usage: pass time_period_start + time_period_end. date_type controls the transaction date window. Omitted (the default) or 'action_date', it selects transaction actions inside the window. 'date_signed' selects the associated award's first signing date; 'last_modified_date' selects transaction update dates. 'new_awards_only' retains in-window actions associated with awards first signed in the window. These are transaction obligation totals, not new-award counts: use new_awards_over_time for counts. Award search/count tools use a different default interval-overlap rule. date_type needs time_period_start and/or time_period_end. program_numbers filters assistance awards by assistance listing (CFDA) number, e.g…
| Name | Type | Req | Description |
|---|---|---|---|
| award_type | – | – | – |
| awarding_agency | – | – | – |
| awarding_subagency | – | – | – |
| contract_pricing_type_codes | – | – | – |
| date_type | – | – | – |
| def_codes | – | – | – |
| extent_competed_type_codes | – | – | – |
| funding_agency | – | – | – |
| group | string | – | – |
| keywords | – | – | – |
| naics_codes | – | – | – |
| program_numbers | – | – | – |
| psc_codes | – | – | – |
| recipient_name | – | – | – |
| time_period_end | – | – | – |
| time_period_start | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the USASpending.gov MCP server?
USASpending.gov is a hosted endpoint at https://usaspending.1102tools.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · usaspending.1102tools.com
claude mcp add --transport http com-1102tools-usaspending-gov-mcp 'https://usaspending.1102tools.com/mcp'
What is the USASpending.gov MCP server?
USASpending.gov is an MCP server listed in the public MCP registry as com.1102tools/usaspending-gov-mcp. USAspending.gov contracts, grants, loans, subawards, recipients, agencies, and federal accounts. This page covers its hosted endpoint (https://usaspending.1102tools.com/mcp).
Is the USASpending.gov MCP server safe to use?
USASpending.gov scores 68 out of 100 on VerifyMCP. 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 USASpending.gov MCP server expose?
USASpending.gov exposes 55 tools: search_awards, get_award_count, spending_over_time, spending_by_category, get_award_detail, and 50 more. Their descriptions and schemas cost roughly 9,933 tokens of context every time the server is loaded.
Does the USASpending.gov MCP server require authentication?
No. We connected to USASpending.gov without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the USASpending.gov MCP server still maintained?
USASpending.gov is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.