What is the main functional difference between AwardCast Federal Contracts and Contractor License Verification (TradesAPI)?

AwardCast Federal Contracts is categorized under Legal and uses an install path we have not confirmed yet. Contractor License Verification (TradesAPI) belongs to Legal and uses a local stdio subprocess. Pick AwardCast Federal Contracts for legal work and Contractor License Verification (TradesAPI) for legal.

How do I install AwardCast Federal Contracts or Contractor License Verification (TradesAPI) in Claude Desktop, Cursor, or Windsurf?

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. AwardCast Federal Contracts has no confirmed install command yet — follow its own setup instructions.

Are AwardCast Federal Contracts and Contractor License Verification (TradesAPI) free to use, or do they require API keys?

AwardCast Federal Contracts has no declared pricing — check the project's own site. Contractor License Verification (TradesAPI) has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, AwardCast Federal Contracts has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Contractor License Verification (TradesAPI) has 49/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.

AwardCast Federal Contracts vs Contractor License Verification (TradesAPI)

Q: Can I run both AwardCast Federal Contracts and Contractor License Verification (TradesAPI) at the same time in my AI client?

Yes. MCP clients support multiple servers: add awardcast-federal-contracts and contractor-license-verification-tradesapi-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

A side-by-side look at the AwardCast Federal Contracts and Contractor License Verification (TradesAPI) MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

AwardCast Federal ContractsLegalUS federal contracting data: open solicitations, buying agencies, contractors, price history.37FairAuth: not declared

Contractor License Verification (TradesAPI)Legal · Local subprocess (stdio)Verify contractor licenses: 50 states + DC + 8 cities — status, expiration, disciplinary history.49FairAuth: not declared

Verdict: choose AwardCast Federal Contracts for legal work; choose Contractor License Verification (TradesAPI) for legal as a local process. You can also run both side by side in one mcpServers block.

Spec	A AwardCast Federal Contracts	Contractor License Verification (TradesAPI)
Category	Legal	Legal
Quality signal	37/100 · Fair	49/100 · Fair
Install command	Not confirmed yet	Confirmed
Transport	—	Local subprocess (stdio)
Auth	Not declared	Not declared
Pricing	Not declared	Not declared
Required env vars	None listed	`CLV_API_URLCLV_API_KEY`
Verified owner	Community listing	Community listing
GitHub stars	—	0
Directory activity	0 views 0 installs 0 upvotes	1 views 0 installs 0 upvotes
Tools	Not listed	1
Full listing	View AwardCast Federal Contracts	View Contractor License Verification (TradesAPI)

AwardCast Federal Contracts vs Contractor License Verification (TradesAPI)

Which MCP server should you choose?

A
Choose AwardCast Federal Contracts when

Choose Contractor License Verification (TradesAPI) when

Feature & specification comparison

Tools & capabilities

AwardCast Federal Contracts tools

Contractor License Verification (TradesAPI) tools 1

Ready-to-paste client configs