# Koot by Datakoot (remote · koot.datakoot.com)

One-call briefings for AI agents: dependency risk (KEV/EPSS), SEC companies, domains, US places.

- Trust score: 63/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `koot.datakoot.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-datakoot-koot-briefings/koot.md), [page](https://verifymcp.io/servers/com-datakoot-koot-briefings/koot)

## Channel facts

- Endpoint: `https://koot.datakoot.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.2`

## 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-10-18.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (koot_unwatch).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 828 tokens (~103/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-datakoot-koot-briefings 'https://koot.datakoot.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-datakoot-koot-briefings": {
      "url": "https://koot.datakoot.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-datakoot-koot-briefings": {
      "type": "http",
      "url": "https://koot.datakoot.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-datakoot-koot-briefings]
url = "https://koot.datakoot.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-datakoot-koot-briefings": {
      "type": "remote",
      "url": "https://koot.datakoot.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-datakoot-koot-briefings --url 'https://koot.datakoot.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-datakoot-koot-briefings:
    url: "https://koot.datakoot.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-datakoot-koot-briefings": {
      "Transport": "http",
      "Url": "https://koot.datakoot.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-datakoot-koot-briefings -t streamable-http -u 'https://koot.datakoot.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-datakoot-koot-briefings": {
      "type": "http",
      "url": "https://koot.datakoot.com/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-10-17 (score 63, +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.

### 2026-10-15 (score 62, +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.

### 2026-10-13 (score 61, +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.

### 2026-10-12 (score 60, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-10 (score 59)

First indexed and scored.

## MCP tools (8)

### `brief_stack` (~157 tokens)

Ask Koot: Is My Stack Safe?

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.

Input parameters:

- `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"].

Output parameters:

- `koot` (string): Koot's one-line answer.

### `brief_company` (~67 tokens)

Ask Koot: Brief Me on a Company

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.

Input parameters:

- `company` (string, required): Ticker (TSLA), company name (Tesla) or CIK.

Output parameters:

- `koot` (string): Koot's one-line answer.

### `brief_domain` (~54 tokens)

Ask Koot: Check a Domain

One call checks a domain: registration and DNS, email security (SPF/DKIM/DMARC), tech stack, and subdomains from certificate logs.

Input parameters:

- `domain` (string, required): Domain, e.g. stripe.com.

Output parameters:

- `koot` (string): Koot's one-line answer.

### `brief_place` (~55 tokens)

Ask Koot: What's Happening at a Place?

One call briefs you on a US place: current conditions, forecast, active weather alerts for the state, nearby earthquakes and elevation.

Input parameters:

- `place` (string, required): US city or address, e.g. 'Harrisburg, PA'.

Output parameters:

- `koot` (string): Koot's one-line answer.

### `koot_watch` (~253 tokens)

Koot Watch: Watch My Stack & Companies (Pro)

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.

Input parameters:

- `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"].

Output parameters:

- `koot` (string): Koot's one-line answer.

### `koot_whats_new` (~61 tokens)

Koot Brief: Anything New for Me? (Pro)

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.

Output parameters:

- `koot` (string): Koot's one-line answer.

### `koot_watches` (~21 tokens)

Koot Watch: What Are You Watching? (Pro)

PRO. Lists what Koot is watching for you.

Output parameters:

- `koot` (string): Koot's one-line answer.

### `koot_unwatch` (~72 tokens)

Koot Watch: Stop Watching (Pro)

PRO. Stop watching some packages or companies, all: true to stop and forget everything, or stop_alerts: true to turn off Slack/Discord alerts.

Input parameters:

- `all` (boolean)
- `companies` (array)
- `packages` (array)
- `stop_alerts` (boolean)

Output parameters:

- `koot` (string): Koot's one-line answer.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-datakoot-koot-briefings/koot#diagnostics

## Score history

- 2026-10-18: 63
- 2026-10-17: 63
- 2026-10-16: 62
- 2026-10-15: 62
- 2026-10-14: 61
- 2026-10-13: 61
- 2026-10-12: 60
- 2026-10-10: 59

## Common questions

### 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.

## Links

- Remote endpoint: https://koot.datakoot.com/mcp
- Repository: https://github.com/datakoot/koot-mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-datakoot-koot-briefings/koot.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-datakoot-koot-briefings/koot.json
- HTML version of this page: https://verifymcp.io/servers/com-datakoot-koot-briefings/koot