usaspending-mcp

Created By
flothjla year ago
mcp server to interact with usaspending.gov api
Overview

what is usaspending-mcp?

usaspending-mcp is a Modular Computing Platform (MCP) server designed to facilitate AI agents in accessing and interacting with the USAspending.gov API, providing tools and utilities for retrieving and analyzing U.S. government spending data.

how to use usaspending-mcp?

To use usaspending-mcp, configure the server with the necessary parameters and utilize the provided endpoints to query spending data based on agency IDs, award IDs, or keywords.

key features of usaspending-mcp?

  • Access to USAspending.gov API for government spending data
  • Multiple endpoints for specific queries (e.g., by agency, award ID, keywords)
  • Streamlined data retrieval and analysis tools

use cases of usaspending-mcp?

  1. Analyzing government spending trends by agency.
  2. Retrieving detailed information about specific awards.
  3. Conducting keyword-based searches for spending data.

FAQ from usaspending-mcp?

  • What is the purpose of usaspending-mcp?

It serves as a server to interact with the USAspending.gov API, making it easier to access and analyze government spending data.

  • How do I configure usaspending-mcp?

Configuration involves setting up the server with the appropriate parameters and using the provided YAML configuration format.

  • Is usaspending-mcp open source?

Yes! The project is available on GitHub for public use and contributions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
flothjl
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago