Compatible with every major AI agent and IDE
What is the DOD Contracts (FPDS) MCP Server?
Connect your AI agent to the Federal Procurement Data System (FPDS) to monitor government spending and analyze contract awards in real-time.
What you can do
- Contract Search — Query the massive database of federal procurement actions using standard FPDS search syntax.
- DOD Targeting — Specifically isolate Department of Defense data by filtering for Department ID '9700' or Agency Code '9700'.
- Market Intelligence — Track vendor performance, identify upcoming procurement trends, and analyze historical spending patterns.
- Pagination Support — Navigate through large result sets using the start parameter to fetch data in batches of 10.
How it works
- Subscribe to this server
- Configure your access identifier
- Start querying federal contracts from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Government Contractors — monitor competitors and find new opportunities within the DOD.
- Data Analysts — extract raw XML contract data for spending analysis and reporting.
- Journalists & Researchers — track government transparency and public spending across federal agencies.
Built-in capabilities (1)
To target DOD contracts, include DEPARTMENT_ID:"9700" or AGENCY_CODE:"9700" in the sQuery parameter. Returns XML data containing contract entries. Search federal contracts via FPDS Atom Feed
Why LlamaIndex?
LlamaIndex agents combine DOD Contracts (FPDS) tool responses with indexed documents for comprehensive, grounded answers. Connect 1 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine DOD Contracts (FPDS) tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain DOD Contracts (FPDS) tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query DOD Contracts (FPDS), a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what DOD Contracts (FPDS) tools were called, what data was returned, and how it influenced the final answer
DOD Contracts (FPDS) in LlamaIndex
DOD Contracts (FPDS) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect DOD Contracts (FPDS) to LlamaIndex through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for DOD Contracts (FPDS) in LlamaIndex
The DOD Contracts (FPDS) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 1 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LlamaIndex only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
DOD Contracts (FPDS) for LlamaIndex
Every tool call from LlamaIndex to the DOD Contracts (FPDS) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I specifically target Department of Defense (DOD) contracts?
To target DOD contracts, include DEPARTMENT_ID:"9700" or AGENCY_CODE:"9700" in your sQuery parameter when using the search_contracts tool.
Can I paginate through large sets of contract results?
Yes. The search_contracts tool supports a start parameter. Results are returned in batches of 10, so you can increment the start number (e.g., 10, 20, 30) to see more records.
What search syntax should I use for the sQuery parameter?
The search_contracts tool uses the standard FPDS Atom Feed search syntax. You can search by keywords, or use specific fields like VENDOR_NAME:"Example Corp" or PIID:"ContractID".
How does LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query DOD Contracts (FPDS) tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp
Explore More MCP Servers
View all →
lemon.markets
8 toolsTrade European stocks and ETFs and access real-time market data via lemon.markets.

UKG Pro
4 toolsManage HR data, employee profiles, and payroll via UKG Pro.

Teambition
10 toolsCollaborative project management platform by Alibaba — manage tasks, projects, and team workflows via AI.

Change Case Engine
1 toolsTransform text between 12 naming conventions (camelCase, snake_case, PascalCase, kebab-case, CONSTANT_CASE, and more) with zero errors.
