FedTally — US Federal Contract Intelligence
REMOTE · FEDTALLY.COM · SCANNED SEP 24
US federal contract recompetes with the incumbent named, awards by company, agency spend.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · fedtally.com
claude mcp add --transport http woodydaniel-fedtally 'https://fedtally.com/api/mcp'
{
"mcpServers": {
"woodydaniel-fedtally": {
"url": "https://fedtally.com/api/mcp"
}
}
} {
"servers": {
"woodydaniel-fedtally": {
"type": "http",
"url": "https://fedtally.com/api/mcp"
}
}
} [mcp_servers.woodydaniel-fedtally] url = "https://fedtally.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"woodydaniel-fedtally": {
"type": "remote",
"url": "https://fedtally.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add woodydaniel-fedtally --url 'https://fedtally.com/api/mcp' --transport streamable-http
mcp_servers:
woodydaniel-fedtally:
url: "https://fedtally.com/api/mcp" {
"McpServers": {
"woodydaniel-fedtally": {
"Transport": "http",
"Url": "https://fedtally.com/api/mcp"
}
}
} assistant mcp add woodydaniel-fedtally -t streamable-http -u 'https://fedtally.com/api/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 10 Sept 26 0
- Stability: 0.97 → pass security
- 9 Sept 26 +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.
- 6 Sept 26 +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.
- 4 Sept 26 +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.
- 2 Sept 26 +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.
- 31 Aug 26 +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.
- 29 Aug 26 +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.
- 27 Aug 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://fedtally.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fedtally.com | CN=YR2,O=Let's Encrypt,C=US | 11 Aug 2026 | 9 Nov 2026 | RSA 2048 | SHA256-RSA | 5b076dc2fa1a9146662305baeed71beaae9 |
| SANs: fedtally.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fedtally.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| fedtally.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fedtally.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://fedtally.com/api/mcp | HTTPS enforced | 308 | https://fedtally.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_agency_spend Get agency contract spend ~250
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | yes | 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. |
No output schema declared.
No examples provided.
get_expiring_contracts Get expiring contracts ~370
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days ahead to look for expiring periods of performance. Defaults to 180. |
| naics | string | yes | NAICS industry code, 2 to 6 digits, e.g. "541511" for custom computer programming. |
No output schema declared.
No examples provided.
search_awards_by_company Search federal awards by company ~241
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page of 25 awards, sorted by amount descending. Defaults to 1. |
| query | string | yes | Company name to match against federal award recipients, e.g. "Booz Allen". |
No output schema declared.
No examples provided.
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.