Scoopkit
dev.scoopkit/mcpVersion 1.0.1AI-industry news for agents: each story once, as a sourced event in a 10/57 taxonomy. No key needed.
Status
Responds231 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:27 UTC
- Latency
- 231 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://api.scoopkit.dev/mcpResponds231 msNo sign-in
Claude Code
claude mcp add --transport http scoopkit https://api.scoopkit.dev/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: scoopkit
Remote MCP server URL: https://api.scoopkit.dev/mcpCursor
{
"mcpServers": {
"scoopkit": {
"url": "https://api.scoopkit.dev/mcp"
}
}
}VS Code
code --add-mcp '{"name":"scoopkit","type":"http","url":"https://api.scoopkit.dev/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
5 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
get_eventGet 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. Over MCP the X-Api-Key header is optional (free tier without it).
### 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"
}
}
``` | Not declared | Yes | Not declared | No |
list_eventsList 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. Over MCP the X-Api-Key header is optional: without it you get the free tier, limited to 100 calls a day per caller.
### 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"
}
}
``` | Not declared | Yes | Not declared | No |
request_magic_linkRequest 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"
}
``` | No | No | No | Yes |
searchSemantic 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"
}
}
``` | Not declared | Yes | Not declared | No |
taxonomyGet Taxonomy
Public taxonomy — no API key required.
### Responses:
**200**: Successful Response (Success Response)
Content-Type: application/json | Not declared | Yes | Not declared | No |
Details
- Registry status
- Active
- Published
- Oct 28, 2026
- Updated
- Oct 28, 2026
- Categories (suggested)
- Search and webSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared