Agentic Mcp Server Builder Conflict

Scaffold MCP server projects and baseline tool contract checks. Use for defining tool schemas, generating starter server layouts, and validating MCP-ready st...

Security Scan

The skill's code and instructions match its stated purpose (scaffolding MCP servers); nothing requests external credentials or network access, though there are minor metadata inconsistencies and a writable-path option you should use cautiously.

Purpose & Capability

The SKILL.md, included Python script, and reference guide all implement scaffolding and contract-check behavior described by the skill. Minor incoherence: registry metadata (slug, ownerId, and version) in the skill bundle differs from values inside _meta.json and the SKILL.md name; this looks like packaging/versioning drift rather than functional mismatch.

Instruction Scope

Runtime instructions are limited: run scripts/scaffold_mcp_server.py and consult the guide. The script reads a JSON payload (with a 1MB cap), normalizes tool names, optionally writes a small set of starter files, and emits an artifact. It does not invoke network calls, read arbitrary system files, or attempt to exfiltrate data.

Install Mechanism

Instruction-only skill with no install spec and no external downloads. The only code executed is the included Python script; no dependencies are required beyond a Python runtime.

Credentials

The skill requests no environment variables, credentials, or config paths. The script operates on input/output file paths only, which is proportional to a scaffolding tool.

Persistence & Privilege

always is false and the skill does not request permanent presence or modify other skills. It may write files into the workspace (or outside it if --allow-outside-workspace is used), which is expected for a scaffolder.

Assessment

This skill appears to do only scaffolding and contract-summary generation and does not request secrets or network access. Before running: 1) prefer dry-run to inspect output without file writes; 2) avoid enabling --allow-outside-workspace unless you trust the payload and want files written outside the current directory; 3) review and validate any input JSON (it is capped at 1MB) and the generated artifact path to avoid overwriting important files; 4) note the metadata mismatches (ownerId/slug/version) — they suggest sloppy packaging but not necessarily malicious intent. If you plan to run this in an automated agent, test it interactively first in an isolated workspace.

Agentic MCP Server Builder

Overview

Create a minimal MCP server scaffold and contract summary from a structured tool list.

Workflow

1. Define server name and tool list with descriptions.
2. Generate scaffold file map and tool contract summary.
3. Optionally materialize starter files when not in dry-run mode.
4. Review generated contract checks before adding business logic.

Use Bundled Resources

• Run scripts/scaffold_mcp_server.py to generate starter artifacts.
• Read references/mcp-scaffold-guide.md for file layout and contract checks.

Guardrails

• Keep tool boundaries explicit and minimal.
• Include deterministic outputs and clear input/output schemas.