Koot by Datakoot
REMOTE · KOOT.DATAKOOT.COM
One-call briefings for AI agents: dependency risk (KEV/EPSS), SEC companies, domains, US places.
Available components
Last scanned (19 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Security
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 Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (koot_unwatch). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 828 tokens (~103/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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 10 Oct 26 59
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 18 Oct 2026 · Probed https://koot.datakoot.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=datakoot.com | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 52dfd27aedf5d35513f7bb83cffed366 |
| SANs: datakoot.com, koot.datakoot.com, *.koot.datakoot.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of koot.datakoot.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| datakoot.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=31536000; includeSubDomains; preload |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://koot.datakoot.com/mcp | Verified | 200 | |
| http (plaintext) | http://koot.datakoot.com/mcp | Inconclusive | 405 |
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 →
brief_company Ask Koot: Brief Me on a Company ~67
One call briefs you on a US public company: SEC profile, recent filings (8-K material events flagged), insider trades and reported financials. Give a ticker, name or CIK.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Ticker (TSLA), company name (Tesla) or CIK. |
| Name | Type | Req | Description |
|---|---|---|---|
| koot | string | yes | Koot's one-line answer. |
No examples provided.
brief_domain Ask Koot: Check a Domain ~54
One call checks a domain: registration and DNS, email security (SPF/DKIM/DMARC), tech stack, and subdomains from certificate logs.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain, e.g. stripe.com. |
| Name | Type | Req | Description |
|---|---|---|---|
| koot | string | yes | Koot's one-line answer. |
No examples provided.
brief_place Ask Koot: What's Happening at a Place? ~55
One call briefs you on a US place: current conditions, forecast, active weather alerts for the state, nearby earthquakes and elevation.
| Name | Type | Req | Description |
|---|---|---|---|
| place | string | yes | US city or address, e.g. 'Harrisburg, PA'. |
| Name | Type | Req | Description |
|---|---|---|---|
| koot | string | yes | Koot's one-line answer. |
No examples provided.
brief_stack Ask Koot: Is My Stack Safe? ~157
One call answers 'is my project safe?'. Checks every package for known vulnerabilities, tells you which are being EXPLOITED IN THE WILD right now (CISA KEV) or likely to be (EPSS), flags abandoned/deprecated packages, and returns a ranked fix-first list. Accepts a package list or a pasted package.json / requirements.txt.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Registry for string packages (default npm). |
| manifest | string | – | Or paste a whole package.json or requirements.txt here. |
| packages | array | – | Packages as 'name' or 'name@version' strings (or {name, version, ecosystem} objects), e.g. ["lodash@4.17.15", "express"]. |
| Name | Type | Req | Description |
|---|---|---|---|
| koot | string | yes | Koot's one-line answer. |
No examples provided.
koot_unwatch Koot Watch: Stop Watching (Pro) ~72
PRO. Stop watching some packages or companies, all: true to stop and forget everything, or stop_alerts: true to turn off Slack/Discord alerts.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | – |
| companies | array | – | – |
| packages | array | – | – |
| stop_alerts | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| koot | string | yes | Koot's one-line answer. |
No examples provided.
koot_watch Koot Watch: Watch My Stack & Companies (Pro) ~253
PRO. Tell Koot what to watch once: packages (or a pasted package.json) and/or companies (tickers). Koot remembers them and only reports what is NEW: newly exploited or likely-exploited vulnerabilities in your packages, and new SEC filings (8-K material events flagged) from your companies. Add notify_url (Slack or Discord webhook) and Koot posts new items there by itself, daily. Calling again adds to the list.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | – | US public companies to watch for NEW SEC filings: tickers, names or CIKs, e.g. ["TSLA", "AAPL"]. Up to 25. |
| ecosystem | string | – | Registry for string packages (default npm). |
| manifest | string | – | Or paste a whole package.json or requirements.txt here. |
| notify_url | string | – | Optional. A Slack or Discord incoming-webhook URL. Koot checks daily and posts there only when something NEW is exploited or likely to be. |
| packages | array | – | Packages as 'name' or 'name@version' strings (or {name, version, ecosystem} objects), e.g. ["lodash@4.17.15", "express"]. |
| Name | Type | Req | Description |
|---|---|---|---|
| koot | string | yes | Koot's one-line answer. |
No examples provided.
koot_watches Koot Watch: What Are You Watching? (Pro) ~21
PRO. Lists what Koot is watching for you.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| koot | string | yes | Koot's one-line answer. |
No examples provided.
koot_whats_new Koot Brief: Anything New for Me? (Pro) ~61
PRO. Ask 'anything new?' and Koot reports only what changed since the last check: new exploited or likely-exploited issues in your watched packages and new SEC filings from your watched companies. Great to call at the start of every session.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| koot | string | yes | Koot's one-line answer. |
No examples provided.
How do I install the Koot by Datakoot MCP server?
Koot by Datakoot is a hosted endpoint at https://koot.datakoot.com/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 · koot.datakoot.com
claude mcp add --transport http com-datakoot-koot-briefings 'https://koot.datakoot.com/mcp'
What is the Koot by Datakoot MCP server?
Koot by Datakoot is an MCP server listed in the public MCP registry as com.datakoot/koot-briefings. One-call briefings for AI agents: dependency risk (KEV/EPSS), SEC companies, domains, US places. This page covers its hosted endpoint (https://koot.datakoot.com/mcp).
Is the Koot by Datakoot MCP server safe to use?
Koot by Datakoot scores 63 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 Koot by Datakoot MCP server expose?
Koot by Datakoot exposes 8 tools: brief_stack, brief_company, brief_domain, brief_place, koot_watch, and 3 more. Their descriptions and schemas cost roughly 740 tokens of context every time the server is loaded.
Does the Koot by Datakoot MCP server require authentication?
No. We connected to Koot by Datakoot without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Koot by Datakoot MCP server still maintained?
Koot by Datakoot is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.