mcp-registry/dev.scoopkit/mcp · vScoopkit MCP server — v0.1.0
As of 2026-10-19 02:55 UTC, the Scoopkit MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 7 minutes.
AI news API: duplicate AI-industry headlines collapse into one structured event.
Claude Code
claude mcp add --transport http scoopkit-mcp-server https://api.scoopkit.dev/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"scoopkit-mcp-server": {
"type": "http",
"url": "https://api.scoopkit.dev/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
3 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Handshake + tools/list takes ~2,610 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 5 tool(s) removed and 0 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.scoopkit%2Fmcp/fixes
{
"name": "get_event",
"description": "Get a single event by ID\n\n404s 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.\n\n### Responses:\n\n**200**: Successful Response (Success Response)\nContent-Type: application/json\n\n**Example Response:**\n```json\n{\n \"data\": {\n \"event_id\": \"Event Id\",\n \"schema_version\": \"Schema Version\",\n \"taxonomy_version\": \"Taxonomy Version\",\n \"primary_category\": ",
"inputSchema": {
"type": "object",
"title": "get_eventArguments",
"required": [
"event_id"
],
"properties": {
"event_id": {
"type": "string",
"title": "event_id"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "list_events",
"description": "List events, newest first\n\nThe 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.\n\n### Responses:\n\n**200**: Successful Response (Success Response)\nContent-Type: application/json\n\n**Example Response:**\n```json\n{\n \"",
"inputSchema": {
"type": "object",
"title": "list_eventsArguments",
"properties": {
"limit": {
"type": "integer",
"title": "limit",
"default": 50,
"maximum": 100,
"minimum": 1
},
"since": {
"type": "string",
"anyOf": [
{
"type": "string",
"format": "date-time"
},
{
"type": "null"
}
],
"title": "since",
"description": "Only events reported_at >= this ISO 8601 timestamp"
},
"until": {
"type": "string",
"anyOf": [
{
"type": "string",
"format": "date-time"
},
{
"type": "null"
}
],
"title": "until",
"description": "Only events reported_at <= this ISO 8601 timestamp"
},
"cursor": {
"type": "string",
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "cursor",
"description": "Opaque cursor from a previous response's next_cursor"
},
"category": {
"type": "string",
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "category",
"description": "Exact primary_category id, e.g. MODEL_RELEASE"
},
"subcategory": {
"type": "string",
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "subcategory",
"description": "Exact subcategory id, e.g. MODEL_RELEASE.NEW_MODEL_RELEASE"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "search",
"description": "Semantic search over events (Pro+)\n\nNatural-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.\n\n### Responses:\n\n**200**: Successful Response (Success Response)\nContent-Type: application/json\n\n**Example Response:**\n```json\n{\n \"data\": [\n {\n \"event_id\": \"Event Id\",\n \"schema_version\": \"Schema",
"inputSchema": {
"type": "object",
"title": "searchArguments",
"required": [
"q"
],
"properties": {
"q": {
"type": "string",
"title": "q",
"minLength": 1,
"description": "Natural-language search query"
},
"limit": {
"type": "integer",
"title": "limit",
"default": 20,
"maximum": 100,
"minimum": 1
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.scoopkit/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/dev.scoopkit/mcp"}) over MCP.
list_events ~429 tokenssearch ~229 tokensrequest_magic_link ~213 tokensget_event ~200 tokenstaxonomy ~75 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fdev.scoopkit%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fdev.scoopkit%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.scoopkit%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.scoopkit%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fdev.scoopkit%2Fmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:2bbfc9c22b259081…, first seen 2026-10-17, included at leaf 5600 of 24,479. Version history · verify what your client received.
Compare: most reliable data servers · most reliable communication servers · most reliable search servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 02:55 UTC, the Scoopkit MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 7 minutes.
Scoopkit MCP server advertises 5 tools, including get_event, list_events, request_magic_link, search, taxonomy.
Point your MCP client at this streamable-http endpoint: https://api.scoopkit.dev/mcp
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.