# FedTally — US Federal Contract Intelligence (remote · fedtally.com)

US federal contract recompetes with the incumbent named, awards by company, agency spend.

- Trust score: 79/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `fedtally.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/woodydaniel-fedtally/api-mcp.md), [page](https://verifymcp.io/servers/woodydaniel-fedtally/api-mcp)

## Channel facts

- Endpoint: `https://fedtally.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 947 tokens (~315/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the FedTally — US Federal Contract Intelligence MCP server?

FedTally — US Federal Contract Intelligence is a hosted endpoint at https://fedtally.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http woodydaniel-fedtally 'https://fedtally.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "woodydaniel-fedtally": {
      "url": "https://fedtally.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "woodydaniel-fedtally": {
      "type": "http",
      "url": "https://fedtally.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.woodydaniel-fedtally]
url = "https://fedtally.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "woodydaniel-fedtally": {
      "type": "remote",
      "url": "https://fedtally.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add woodydaniel-fedtally --url 'https://fedtally.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  woodydaniel-fedtally:
    url: "https://fedtally.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "woodydaniel-fedtally": {
      "Transport": "http",
      "Url": "https://fedtally.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add woodydaniel-fedtally -t streamable-http -u 'https://fedtally.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "woodydaniel-fedtally": {
      "type": "http",
      "url": "https://fedtally.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-10 (score 79, 0)

- [security] Stability: 0.97 → pass

### 2026-09-09 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-02 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-31 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-29 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-27 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `search_awards_by_company` (~241 tokens)

Search federal awards by company

Top US federal prime contract awards won by a company, largest award amount first. Use it to size a contractor's federal business, see which agencies buy from it, or pull its biggest named contracts. Matching is full-text on the recipient name, so pass the company's common or legal name ("Booz Allen", "Lockheed Martin") rather than a ticker or internal abbreviation; a name that is too specific returns nothing. Returns up to 25 awards per page with award ID, recipient, awarding agency, amount, period of performance, NAICS code, and description; page through with the page argument while hasNext is true. Source: USAspending.gov prime contract awards (public domain, no login). Civilian agency awards are roughly 4 days fresh; Department of Defense awards are withheld about 90 days, so recent defense activity looks sparser than it is. Amounts are obligated dollars in USD.

Input parameters:

- `page` (integer): Page of 25 awards, sorted by amount descending. Defaults to 1.
- `query` (string, required): Company name to match against federal award recipients, e.g. "Booz Allen".

### `get_agency_spend` (~250 tokens)

Get agency contract spend

Where one federal agency's contract dollars went in a fiscal year: its top vendors and its top NAICS industries, both ranked by obligated amount. Use it to answer who sells to an agency and what that agency buys. The agency argument must resolve to a single toptier agency — use the full name ("Department of Veterans Affairs") or the official abbreviation ("VA"); an ambiguous fragment matching several agencies returns no match rather than a guess. Fiscal years run 1 October to 30 September and are named for the ending calendar year, so FY2026 starts 2025-10-01; omit fiscalYear for the current one. Source: USAspending.gov prime contract awards (public domain, no login). Civilian agency awards are roughly 4 days fresh; Department of Defense awards are withheld about 90 days, so recent defense activity looks sparser than it is. Amounts are obligated dollars in USD.

Input parameters:

- `agency` (string, required): Toptier agency name or abbreviation, e.g. "Department of Homeland Security" or "GSA".
- `fiscalYear` (integer): US federal fiscal year, e.g. 2026. Defaults to the current fiscal year.

### `get_expiring_contracts` (~370 tokens)

Get expiring contracts

Federal contracts whose period of performance ends inside a chosen window for one NAICS industry — the recompete pipeline, useful for finding work about to be rebid and identifying the incumbent to displace. Rows come back soonest expiry first with the end date, days remaining, contract PIID and parent IDV, incumbent vendor name and UEI, contracting department, obligated dollars, total contract value including options, place of performance, and description. Two fields matter most to small contractors: setAside, the socioeconomic set-aside the work was competed under (SDVOSBC service-disabled veteran-owned, WOSB women-owned, 8AN 8(a) sole source, SBA total small business, HZC HUBZone), which is null when the work was competed full and open; and isSmallBusiness, the contracting officer's size determination for the incumbent — together they show whether a small firm is eligible to bid and whether the incumbent is a small business or a large one. Rows are served from nightly SAM.gov snapshots. Coverage is partial and rotating: the sync refreshes the stalest few of the 20 seeded industries each night, so only some are readable at any moment and the set grows over a few nights. The syncedAt field gives the timestamp of the sync that produced the rows, and an industry with no snapshot yet returns a short notice naming the codes that are currently synced, instead of data. Source: SAM.gov Contract Awards v1, public domain US Government data. Vendor street addresses are never returned.

Input parameters:

- `days` (integer): Days ahead to look for expiring periods of performance. Defaults to 180.
- `naics` (string, required): NAICS industry code, 2 to 6 digits, e.g. "541511" for custom computer programming.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/woodydaniel-fedtally/api-mcp#diagnostics

## Score history

- 2026-09-24: 79
- 2026-09-23: 79
- 2026-09-22: 79
- 2026-09-21: 79
- 2026-09-20: 79
- 2026-09-19: 79
- 2026-09-18: 79
- 2026-09-17: 79
- 2026-09-16: 79
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 79
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 79
- 2026-09-09: 79
- 2026-09-08: 78
- 2026-09-07: 78
- 2026-09-06: 78
- 2026-09-05: 77
- 2026-09-04: 77
- 2026-09-03: 76
- 2026-09-02: 76
- 2026-09-01: 75
- 2026-08-31: 75
- 2026-08-30: 74
- 2026-08-29: 74
- 2026-08-28: 73
- 2026-08-27: 73
- 2026-08-26: 72

## Common questions

### What is the FedTally — US Federal Contract Intelligence MCP server?

FedTally — US Federal Contract Intelligence is an MCP server listed in the public MCP registry as io.github.woodydaniel/fedtally. US federal contract recompetes with the incumbent named, awards by company, agency spend. This page covers its hosted endpoint (https://fedtally.com/api/mcp).

### Is the FedTally — US Federal Contract Intelligence MCP server safe to use?

FedTally — US Federal Contract Intelligence scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the FedTally — US Federal Contract Intelligence MCP server expose?

FedTally — US Federal Contract Intelligence exposes 3 tools: search_awards_by_company, get_agency_spend, get_expiring_contracts. Their descriptions and schemas cost roughly 861 tokens of context every time the server is loaded.

### Does the FedTally — US Federal Contract Intelligence MCP server require authentication?

No. We connected to FedTally — US Federal Contract Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the FedTally — US Federal Contract Intelligence MCP server still maintained?

FedTally — US Federal Contract Intelligence is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://fedtally.com/api/mcp
- Website: https://fedtally.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/woodydaniel-fedtally/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/woodydaniel-fedtally/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/woodydaniel-fedtally/api-mcp