Scoopkit MCP server
dev.scoopkit/mcpscoopkit.devstreamable-httpv1.0.1Scanned
AI-industry news for agents: each story once, as a sourced event in a 10/57 taxonomy. No key needed.
5 tools: 1 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Scoopkit MCP server can do
The Scoopkit MCP server is published by scoopkit.dev, a domain the MCP Registry verified. It has 5 tools. It can create or change data (1 tool: request_magic_link), but cannot delete data. 4 tools only read.
1 tool brings in text other people can write (request_magic_link).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 1Claude Code: ask
request_magic_linkRequest a free API key by email Step 1 of self-serve signup — no key required.Reads text others writeNo findings
Why it is in this group
- The name "request_magic_link" says "request": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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" } ```
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 4Show 4 read-only tools
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 da…No findings
Why it is in this group
- The name "get_event" says "get": a word for reading.
Description, as the server wrote it 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. 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" } } ```
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
list_eventsList events, newest first The primary resource — one structured event per underlying story, already deduplicated from many source articles.No findings
Why it is in this group
- The name "list_events" says "list": a word for reading.
Description, as the server wrote it 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. 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" } } ```
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
searchSemantic search over events (Pro+) Natural-language query embedded and ranked by cosine similarity against published events — not a keyword/text match.No findings
Why it is in this group
- The name "search" says "search": a word for reading.
Description, as the server wrote it 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" } } ```
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
taxonomyGet Taxonomy Public taxonomy — no API key required.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get Taxonomy Public taxonomy — no API key required. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:52 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.scoopkit.dev/mcp: tools/list returned 5 tools to an anonymous client, including request_magic_link (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools5 changed.~5 changedView diff
- Changed:get_eventOnly readstitledescriptionannotations
- Changed:list_eventsOnly readstitledescriptionannotations
- Changed:request_magic_linkChanges thingstitleannotations
- Changed:searchOnly readstitleannotations
- Changed:taxonomyOnly readstitleannotations
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http scoopkit https://api.scoopkit.dev/mcpclaude mcp add --transport http scoopkit https://api.scoopkit.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__scoopkit__list_events",
"mcp__scoopkit__get_event",
"mcp__scoopkit__search",
"mcp__scoopkit__taxonomy"
],
"ask": [
"mcp__scoopkit__request_magic_link"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as scoopkit. Review it before you use it.
Capability tags behind 1 rule
- mcp__scoopkit__request_magic_link untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.scoopkit/mcp/verify?hash=9fc985ba5b814df1a42283fd1c514478396196cf1e5b88ee8d90e29ae6b0f941" | jq -e '.changed == false'Pinned hash 9fc985ba5b81, from Nov 9, 2026, 21:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.scoopkit/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.scoopkit/mcp)Source: MCP Registry · repository. Synced Oct 28, 2026, 03:17 UTC.
Scoopkit MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Scoopkit MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Scoopkit MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Scoopkit MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Scoopkit MCP server have?
- 5 tools: 1 write, 4 read. request_magic_link, list_events, get_event, search and taxonomy.
Does the Scoopkit MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Scoopkit MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Scoopkit MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 28, 2026. Every change is on this page and in its Atom feed.