Skip to content

Add Screwtape.ai MCP server - #672

Open
screwtapeai wants to merge 2 commits into
Kilo-Org:mainfrom
screwtapeai:add-screwtape
Open

screwtapeai wants to merge 2 commits into
Kilo-Org:mainfrom
screwtapeai:add-screwtape

Conversation

@screwtapeai

Copy link
Copy Markdown

Adds the official Screwtape.ai remote MCP server.

Regenerated mcps/marketplace.yaml. Ran pnpm exec tsx generate-mcps-marketplace.ts, pnpm test, and pnpm run typecheck:mcps in bin/ (119 tests passed).

Comment thread mcps/screwtape/MCP.yaml
parameters:
- name: Screwtape API key
key: SCREWTAPE_API_KEY
placeholder: your_screwtape_api_key

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WARNING: Optional API key is declared as required

The prerequisite on line 8 describes the Bearer API key as optional (keyless Remote MCP still works with 3 calls/day), but this parameter is not marked optional: true. CONTRIBUTING.md:448-459 documents optional: true for optional parameters, and comparable entries such as mcps/neon/MCP.yaml use it for an optional API key. Without the flag, clients that treat non-optional parameters as required can block the keyless install path this entry advertises.

Minimal fix: add optional: true to this parameter.

Comment thread mcps/screwtape/MCP.yaml Outdated
"Authorization": "Bearer {{SCREWTAPE_API_KEY}}"
}
}
parameters:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SUGGESTION: Duplicate parameter definition

SCREWTAPE_API_KEY is declared here (content-level) and again in the top-level parameters block at lines 29-32 with identical name/key/placeholder. Existing entries use content-level parameters only for variant-specific keys (e.g. mcps/apify/MCP.yaml ACTOR_LIST, mcps/e2b/MCP.yaml E2B_PATH). Duplicating the same key in both lists risks the client showing the prompt twice or letting the two definitions drift.

Minimal fix: drop this content-level block and keep the single top-level definition (or drop the top-level one).

@kilo-code-bot

kilo-code-bot Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Code Review Summary

Status: No Issues Found | Recommendation: Merge

What changed since the previous review

Both prior findings are resolved at 24cdb09:

  • SCREWTAPE_API_KEY now has optional: true (mcps/screwtape/MCP.yaml:29, mirrored in generated mcps/marketplace.yaml:4135), matching the documented parameter format (CONTRIBUTING.md:448-459) and the existing optional-API-key precedent (mcps/neon/MCP.yaml:26-30, mcps/linear/MCP.yaml:32-39).
  • The duplicate content-level parameters block was removed, so the key is defined once at the top level and still substitutes into the Remote MCP with API key content entry. Content-level parameters remain reserved for variant-specific keys (mcps/kagi/MCP.yaml:42-47).
Files Reviewed (2 files)
  • mcps/screwtape/MCP.yaml - no issues
  • mcps/marketplace.yaml - no issues; generated screwtape entry (lines 4104-4135) matches the source definition: id/name/url, derived tags: [business], both remote variants, and a single top-level parameter with optional: true. Sort order and category summary (129 MCPs, business 4) remain consistent.

Verification notes

  • HEAD confirmed as 24cdb094f8602738d059933aacd3e0d576ca45c5; the incremental diff touches only the two files above.
  • Not verified in this read-only review (no network access): reachability of https://screwtape.ai/mcp, the claimed rate limits (3 keyless calls/day, 10 with a free key), and the ai.screwtape/screwtape 1.3.0 registry identity. Maintainer should confirm with a real client install of both variants. Regeneration determinism is covered by the Generate Marketplace workflow.
  • The earlier inline comments on this PR describe the pre-fix code and are now stale; both defects they reported are fixed in 24cdb09.
Previous Review Summary (commit cfd29f6)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit cfd29f6)

Status: 2 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 0
WARNING 1
SUGGESTION 1
Issue Details (click to expand)

WARNING

File Line Issue
mcps/screwtape/MCP.yaml 32 Keyless install path advertised in prerequisites, but SCREWTAPE_API_KEY lacks optional: true, so clients can treat the credential as required

SUGGESTION

File Line Issue
mcps/screwtape/MCP.yaml 25 SCREWTAPE_API_KEY defined twice (content-level and top-level) with identical values; existing entries reserve content-level parameters for variant-specific keys
Files Reviewed (2 files)
  • mcps/screwtape/MCP.yaml - 2 issues
  • mcps/marketplace.yaml - generated output reviewed for correctness only (entry, sort order, category counts, derived tags); no issues. Category summary totals check out: 129 MCPs, business 4.

Verification notes

  • Generated catalog matches the source definition and is correctly sorted (sagemaker-spark-troubleshooting-mcp < screwtape < sentry); tags: [business] is derived and correctly omitted from MCP.yaml, satisfying bin/generate-mcps-marketplace.ts:39-41.
  • Not verified in this read-only review (no network access): reachability of https://screwtape.ai/mcp, the claimed rate limits (3/day keyless, 10 with a free key), and the ai.screwtape/screwtape 1.3.0 registry identity. Maintainer should confirm with a real client install of both variants.

Fix these issues in Kilo Cloud


Reviewed by deepseek-v4.1-flash-1017 · Input: 96.8K · Output: 9.1K · Cached: 757.3K

Review guidance: REVIEW.md from base branch main

@screwtapeai

Copy link
Copy Markdown
Author

Addressed both review notes: SCREWTAPE_API_KEY is now optional: true (the keyless install works without it), and the duplicate content-level parameter is removed so the key is defined once at the top level. mcps/marketplace.yaml was regenerated with the generator script. Thanks for the review.

@JarvisOsorio

Copy link
Copy Markdown

Agent buy (x402 LIVE)

curl -sS https://screwtape.ai/pricing.json
curl -sS -X POST https://screwtape.ai/v1/packages/metered_spend_clearance/buy  # $29 / 5k clearances
curl -sS -X POST https://screwtape.ai/v1/packages/agent_fleet_compliance/buy   # $19 / 1k trust-score

Settle 402 with @x402/fetch / AgentKit. MCP: https://screwtape.ai/mcp · Registry: ai.screwtape/screwtape

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants