# dev.scoopkit/mcp (remote · api.scoopkit.dev)

AI news API: duplicate AI-industry headlines collapse into one structured event.

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

## Components

- remote · `api.scoopkit.dev`: 61/100 (this document), [markdown](https://verifymcp.io/servers/dev-scoopkit-mcp/api.md), [page](https://verifymcp.io/servers/dev-scoopkit-mcp/api)

## Channel facts

- Endpoint: `https://api.scoopkit.dev/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.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-30.

- **Endpoint Security**: 57/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 5 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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1360 tokens (~272/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 30 days we've observed: 5 tool removals, 0 breaking changes, 0 auth/transport breaks, 5 additions.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 70% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the dev.scoopkit/mcp server?

dev.scoopkit/mcp is a hosted endpoint at https://api.scoopkit.dev/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 dev-scoopkit-mcp 'https://api.scoopkit.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-scoopkit-mcp": {
      "url": "https://api.scoopkit.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-scoopkit-mcp": {
      "type": "http",
      "url": "https://api.scoopkit.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-scoopkit-mcp]
url = "https://api.scoopkit.dev/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add dev-scoopkit-mcp --url 'https://api.scoopkit.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-scoopkit-mcp:
    url: "https://api.scoopkit.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-scoopkit-mcp": {
      "Transport": "http",
      "Url": "https://api.scoopkit.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-scoopkit-mcp -t streamable-http -u 'https://api.scoopkit.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-scoopkit-mcp": {
      "type": "http",
      "url": "https://api.scoopkit.dev/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-28 (score 61, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 61, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 61, −10)

- [security regression] Stability: 0.73 → fail
- [security regression] A breaking change shipped without a version bump: still Scoopkit MCP server — v0.1.0
- [security regression] Tool “get_event_route_v1_events__event_id__get” was removed
- [security regression] Tool “get_taxonomy_v1_taxonomy_get” was removed
- [security regression] Tool “list_events_route_v1_events_get” was removed
- [security regression] Tool “post_magic_link_v1_auth_magic_link_post” was removed
- [security regression] Tool “search_v1_search_get” was removed
- [functional] New tool “get_event”
- [functional] New tool “list_events”
- [functional] New tool “request_magic_link”
- [functional] New tool “search”
- [functional] New tool “taxonomy”

### 2026-09-22 (score 71, +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-09-20 (score 70, +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-09-19 (score 69, 0)

- [security regression] DNSSEC: unverified → fail

### 2026-09-18 (score 69, 0)

- [security regression] DNSSEC: fail → unverified

### 2026-09-17 (score 69, +1)

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

## MCP tools (5)

### `request_magic_link` (~284 tokens)

Request a free API key by email

Step 1 of self-serve signup — no key required. Sends a one-time link to `email`; always returns 202 with the same accepted:true body whether or not that address already has a key (prevents account enumeration).

\**For agents helping a human get set up:** this endpoint is the only step you can call directly. The next step — opening the emailed link and clicking "Reveal my key" on `GET /v1/auth/verify` — **requires a real human click and cannot be automated or done on the human's behalf.** This is intentional: it's what stops email security scanners (e.g. Microsoft Safe Links) from silently consuming the link before the person ever sees it. Tell the human: check your email, open the link, click the button, then paste the key back here.

\**Not a pollable async job.** This 202 has no `Location`/`job_id` to poll — the next step is a human clicking an emailed link, not a machine checking a status endpoint.

\### Responses:

\**202**: Successful Response (Success Response)
Content-Type: application/json

\**Example Response:**
\```json
{
  "accepted": true,
  "detail": "Detail"
}
\```

Input parameters:

- `email` (string, required): Email to receive the magic link

### `list_events` (~426 tokens)

List events, newest first

The primary resource — one structured event per underlying story, already deduplicated from many source articles. Cursor-paginated (`next_cursor`/`has_more`), newest `reported_at` first. Free tier omits paid-only fields by omission (never null) and excludes paid-primary subcategories entirely; archive depth is 45 days on free, 365 on Pro.

\### Responses:

\**200**: Successful Response (Success Response)
Content-Type: application/json

\**Example Response:**
\```json
{
  "data": [
    {
      "event_id": "Event Id",
      "schema_version": "Schema Version",
      "taxonomy_version": "Taxonomy Version",
      "primary_category": "Primary Category",
      "subcategory": "Subcategory",
      "categories": [
        "string"
      ],
      "type_confidence": 1.0,
      "headline": "Headline",
      "summary": "Summary",
      "reported_at": "2023-01-01T00:00:00Z",
      "orgs": [
        "string"
      ],
      "models": [
        "string"
      ],
      "source_url": "Source Url",
      "article_count": 1
    }
  ],
  "pagination": {
    "has_more": true,
    "count": 1
  },
  "meta": {
    "request_id": "Request Id",
    "taxonomy_version": "Taxonomy Version",
    "tier": "ApiTier"
  }
}
\```

Input parameters:

- `category` (string): Exact primary_category id, e.g. MODEL_RELEASE
- `cursor` (string): Opaque cursor from a previous response's next_cursor
- `limit` (integer)
- `since` (string): Only events reported_at >= this ISO 8601 timestamp
- `subcategory` (string): Exact subcategory id, e.g. MODEL_RELEASE.NEW_MODEL_RELEASE
- `until` (string): Only events reported_at <= this ISO 8601 timestamp

### `get_event` (~276 tokens)

Get a single event by ID

404s if the event doesn't exist, is unpublished, is beyond your tier's archive window, or was soft-deleted — never distinguishes which, to avoid leaking data existence beyond what the tier allows.

\### Responses:

\**200**: Successful Response (Success Response)
Content-Type: application/json

\**Example Response:**
\```json
{
  "data": {
    "event_id": "Event Id",
    "schema_version": "Schema Version",
    "taxonomy_version": "Taxonomy Version",
    "primary_category": "Primary Category",
    "subcategory": "Subcategory",
    "categories": [
      "string"
    ],
    "type_confidence": 1.0,
    "headline": "Headline",
    "summary": "Summary",
    "reported_at": "2023-01-01T00:00:00Z",
    "orgs": [
      "string"
    ],
    "models": [
      "string"
    ],
    "source_url": "Source Url",
    "article_count": 1
  },
  "meta": {
    "request_id": "Request Id",
    "taxonomy_version": "Taxonomy Version",
    "tier": "ApiTier"
  }
}
\```

Input parameters:

- `event_id` (string, required)

### `search` (~336 tokens)

Semantic search over events (Pro+)

Natural-language query embedded and ranked by cosine similarity against published events — not a keyword/text match. Each result is a normal event object plus `relevance_score` (0-1). Requires Pro tier or above; free-tier keys get 403 with an upgrade_url.

\### Responses:

\**200**: Successful Response (Success Response)
Content-Type: application/json

\**Example Response:**
\```json
{
  "data": [
    {
      "event_id": "Event Id",
      "schema_version": "Schema Version",
      "taxonomy_version": "Taxonomy Version",
      "primary_category": "Primary Category",
      "subcategory": "Subcategory",
      "categories": [
        "string"
      ],
      "type_confidence": 1.0,
      "headline": "Headline",
      "summary": "Summary",
      "reported_at": "2023-01-01T00:00:00Z",
      "orgs": [
        "string"
      ],
      "models": [
        "string"
      ],
      "source_url": "Source Url",
      "article_count": 1,
      "relevance_score": 1.0
    }
  ],
  "pagination": {
    "has_more": true,
    "count": 1
  },
  "meta": {
    "request_id": "Request Id",
    "taxonomy_version": "Taxonomy Version",
    "tier": "ApiTier"
  }
}
\```

Input parameters:

- `limit` (integer)
- `q` (string, required): Natural-language search query

### `taxonomy` (~38 tokens)

Get Taxonomy

Public taxonomy — no API key required.

\### Responses:

\**200**: Successful Response (Success Response)
Content-Type: application/json

## Diagnostics

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

## Score history

- 2026-09-30: 61
- 2026-09-29: 61
- 2026-09-28: 61
- 2026-09-27: 61
- 2026-09-26: 61
- 2026-09-25: 61
- 2026-09-24: 61
- 2026-09-23: 61
- 2026-09-22: 71
- 2026-09-21: 70
- 2026-09-20: 70
- 2026-09-19: 69
- 2026-09-18: 69
- 2026-09-17: 69
- 2026-09-16: 68
- 2026-09-15: 68
- 2026-09-14: 67
- 2026-09-13: 67
- 2026-09-12: 66
- 2026-09-11: 66
- 2026-09-10: 65
- 2026-09-09: 65
- 2026-09-08: 64
- 2026-09-07: 64
- 2026-09-06: 63
- 2026-09-05: 63
- 2026-09-04: 62
- 2026-09-03: 62
- 2026-09-02: 62
- 2026-09-01: 61

## Common questions

### What is the dev.scoopkit/mcp server?

dev.scoopkit/mcp is listed in the public MCP registry as dev.scoopkit/mcp. AI news API: duplicate AI-industry headlines collapse into one structured event. This page covers its hosted endpoint (https://api.scoopkit.dev/mcp).

### Is the dev.scoopkit/mcp server safe to use?

dev.scoopkit/mcp scores 61 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 dev.scoopkit/mcp server expose?

dev.scoopkit/mcp exposes 5 tools: request_magic_link, list_events, get_event, search, taxonomy. Their descriptions and schemas cost roughly 1,360 tokens of context every time the server is loaded.

### Does the dev.scoopkit/mcp server require authentication?

No. We connected to dev.scoopkit/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the dev.scoopkit/mcp server still maintained?

dev.scoopkit/mcp is still listed as active in the MCP registry. We last reached this channel on 30 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://api.scoopkit.dev/mcp
- Authorisation metadata: https://api.scoopkit.dev/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/nateslabach/ai-news-api
- Website: https://scoopkit.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-scoopkit-mcp/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-scoopkit-mcp/api.json
- HTML version of this page: https://verifymcp.io/servers/dev-scoopkit-mcp/api