Is the Awardtape MCP server down?

mcp-registry/com.awardtape/mcp · v1.0.0

healthy
Last checked 2026-10-27 04:12 UTC · handshake 190ms

As of 2026-10-27 04:12 UTC, the Awardtape MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
567
outages (90d)
0
tools
18

Search DoD and DHS prime contract awards since FY2024, company profiles and daily contract releases.

Point your MCP client at this streamable-http endpoint: https://awardtape.com/api/agent/mcp

Agent-readiness: C (73/100)

C (73/100): 0 error(s), 3 warning(s) across 18 tool(s); ~2,396 tokens of tool definitions.
Scores higher than 8% of 15,786 MCP servers Glimind has audited.
Its tool list costs an agent ~2,396 tokens per session — more than 50% of servers.
70 → 73 since 2026-10-25
no tool-poisoning patterns
Schemas100
Descriptions51
Safety hints16
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

18 of 18 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: check_demand_for_xyz, check_owner_payment, find_expiring_recompetes, find_sell_now_opportunities, get_company and 13 more

26 parameter(s) across 10 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: check_owner_payment, get_company, get_global_trends, list_allied_and_fms, list_recompetes and 5 more

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: request_owner_payment

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 14 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 10 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.awardtape%2Fmcp/fixes

check_demand_for_xyz 1 change
{
  "name": "check_demand_for_xyz",
  "description": "Free (0 credits). Demand for XYZ velocity & market-structure analyzer: pass any capability, commodity, PSC/FSC code, MIL-STD, or weapon system (e.g. \"radar\", \"counter-UAS\", \"fuel\", \"4470\", \"MIL-STD-810H\") to get 7d/30d DoD spend velocity, velocity multiple vs baseline, top buying commands, market concentration (Consolidated -> Subcontract Play vs Open -> Direct Bid Play), and counts of open Sell-Now subcontract windows and Sell-Next expiring recompetes.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "q": {
        "type": "string",
        "description": "Capability, commodity, PSC/FSC code, standard, or weapon system query (e.g. radar, counter-UAS, fuel, 4470, MIL-STD-810H)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
check_owner_payment 1 change
{
  "name": "check_owner_payment",
  "description": "Free. Status of an owner checkout: pending, paid (returns the key once), claimed or expired.",
  "inputSchema": {
    "type": "object",
    "required": [
      "claim_token"
    ],
    "properties": {
      "claim_token": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
find_expiring_recompetes 1 change
{
  "name": "find_expiring_recompetes",
  "description": "Paid ($0.05/call or 1 call from API key). Sell-Next recompete radar: returns expiring DoD and DHS incumbent contracts (next 6-18 months) from the $126.8B recompete pipeline with days_to_expiry, burn_pct, incumbent_vulnerability (sole-source vs single-bid vs competed), monetize_action, and 1-click FOIA (Beta) URL.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "q": {
        "type": "string",
        "description": "Keyword, capability, PSC, PIID, or office filter"
      },
      "agency": {
        "type": "string",
        "description": "Agency or sub-agency filter"
      },
      "company": {
        "type": "string",
        "description": "Incumbent contractor name or slug filter"
      },
      "max_days": {
        "type": "integer",
        "description": "Maximum days until contract expiration (default 540)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.awardtape/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.awardtape/mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.awardtape%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fcom.awardtape%2Fmcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.awardtape%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.awardtape%2Fmcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.awardtape%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.awardtape%2Fmcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:6abf2d3d6541e84d…, first seen 2026-10-26, included at leaf 76099 of 77,297. Version history · verify what your client received.

Tools (18)

Compare: most reliable search servers · most reliable payments servers · most reliable knowledge servers · most reliable communication servers · most reliable compliance servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Awardtape MCP server down right now?

As of 2026-10-27 04:12 UTC, the Awardtape MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Awardtape MCP server provide?

Awardtape MCP server advertises 18 tools, including check_demand_for_xyz, check_owner_payment, find_expiring_recompetes, find_sell_now_opportunities, get_company.

How do I install Awardtape MCP server?

Point your MCP client at this streamable-http endpoint: https://awardtape.com/api/agent/mcp

Is the Awardtape MCP server safe to connect to an AI agent?

Glimind scanned all 18 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Awardtape MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve