Bring Federal Procurement
to Claude Desktop
Learn how to connect DOD Contracts (FPDS) to Claude Desktop and start using 1 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
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 Claude Desktop?
Claude Desktop is the definitive way to connect DOD Contracts (FPDS) to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 1 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
DOD Contracts (FPDS) in Claude Desktop
DOD Contracts (FPDS) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect DOD Contracts (FPDS) to Claude Desktop 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 Claude Desktop
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 Claude Desktop 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 Claude Desktop
Every tool call from Claude Desktop 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 Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
Ragas
7 toolsEquip your AI with Ragas to create datasets, run RAG evaluations, and track experiment metrics directly from your workflow.
FNS SNAP Retailer Locator (USDA)
2 toolsLocate SNAP-authorized retailers across the US using USDA public data. Filter by location, store name, or coordinates.
Nango (Unified API & Integration Platform)
7 toolsManage product integrations via Nango — audit OAuth connections, track data syncs, and explore unified records.
AfterShip Tracking
5 toolsShipment tracking and logistics — track packages, manage couriers, and monitor deliveries via AI.