NDAA.AI FY2027 Tracker
REMOTE · MCP.NDAA.AI · 2 COMPONENTS
Public FY2027 NDAA tracker: bill status, section text, House vs Senate diffs, and news from ndaa.ai
Available components
Last scanned (5 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 5 Nov 2026.
Category News and Social
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 8 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 Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 658 tokens (~82/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 65
First indexed and scored.
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 5 Nov 2026 · Probed https://mcp.ndaa.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.ndaa.ai | CN=YR2,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | RSA 2048 | SHA256-RSA | 6f95077a5afa7aed3f3bb5d8fd589dd8832 |
| SANs: mcp.ndaa.ai | ||||||
| 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 mcp.ndaa.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| ndaa.ai. | 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://mcp.ndaa.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.ndaa.ai/mcp | HTTPS enforced | 308 | https://mcp.ndaa.ai/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 →
compare_house_senate ~120
Compare House (H.R. 8800) vs Senate (S. 4784) text for a section number or a topic. Returns which chamber has the section, whether the text differs, and the diff URL.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max sections when comparing a topic (default 12, max 25). |
| section | string | – | Section number to compare (e.g. "601"). |
| topic | string | – | Topic slug or keyword to compare across chambers (e.g. "pay raise", "foci"). |
No output schema declared.
No examples provided.
get_section ~60
Get one FY2027 NDAA section: plain-language summary, statutory text, House and Senate variants when both exist, and the ndaa.ai URL to cite.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | yes | Section number, e.g. "601" or "847". |
No output schema declared.
No examples provided.
get_status ~53
Current FY2027 NDAA bill status (H.R. 8800 / S. 4784): headline, summary, next steps, stage tracker, and as-of date. Cite the returned ndaa.ai URL.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_update ~74
Get one dated NDAA update post (the newest if no date): intro, every story (headline, outlet, summary, source URL), status note, and the canonical URL.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Post date YYYY-MM-DD (e.g. "2026-10-14"). Omit for the latest post. |
No output schema declared.
No examples provided.
latest_news ~54
Latest NDAA news items tracked on ndaa.ai (outlet, date, summary, source URL, and the /news page to cite).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max items (default 10, max 25). |
No output schema declared.
No examples provided.
list_guides ~40
List NDAA.AI explainer guides (status, House vs Senate, FY2027 vs FY2026, military pay raise) with canonical URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_updates ~60
List ndaa.ai's dated NDAA update posts, newest first: date, title, story count, status note, and the /updates/YYYY-MM-DD URL to cite.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max posts (default 10, max 50). |
No output schema declared.
No examples provided.
search_sections ~112
Search FY2027 NDAA sections by keyword or topic (pay raise, FOCI, OTA, shipbuilding, etc.). Returns matching sections with snippets and canonical ndaa.ai URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 12, max 25). |
| query | string | – | Keyword, topic slug, or phrase to search in titles, topics, and statutory text. |
| topic | string | – | Optional topic slug (e.g. foci, ota, space-force, right-to-repair). |
No output schema declared.
No examples provided.
How do I install the NDAA.AI FY2027 Tracker MCP server?
NDAA.AI FY2027 Tracker is a hosted endpoint at https://mcp.ndaa.ai/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 · mcp.ndaa.ai
claude mcp add --transport http tera-sarah-ndaa-ai 'https://mcp.ndaa.ai/mcp'
What is the NDAA.AI FY2027 Tracker MCP server?
NDAA.AI FY2027 Tracker is an MCP server listed in the public MCP registry as io.github.tera-sarah/ndaa-ai. Public FY2027 NDAA tracker: bill status, section text, House vs Senate diffs, and news from ndaa.ai. This page covers its hosted endpoint (https://mcp.ndaa.ai/mcp).
Is the NDAA.AI FY2027 Tracker MCP server safe to use?
NDAA.AI FY2027 Tracker scores 66 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 NDAA.AI FY2027 Tracker MCP server expose?
NDAA.AI FY2027 Tracker exposes 8 tools: get_status, search_sections, get_section, compare_house_senate, latest_news, and 3 more. Their descriptions and schemas cost roughly 573 tokens of context every time the server is loaded.
Does the NDAA.AI FY2027 Tracker MCP server require authentication?
No. We connected to NDAA.AI FY2027 Tracker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the NDAA.AI FY2027 Tracker MCP server still maintained?
NDAA.AI FY2027 Tracker is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.