mcp-creator
Build, audit, debug, or integrate an MCP server. Use for protocol and SDK compatibility, tools/resources/prompts, transport, authorization, host setup, and interoperability testing.
v2026.11.13-21cd5683 installs+3 in 7 days39 StarsMITsynced 10 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/mcp-creatorWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package2879837e…fdf49d25
2879837e66f7…4776fdf49d258 files · 30.1 KBScanMedium5 findings
- injection.no_confirmationreferences/patterns.md:101
- injection.no_confirmationreferences/patterns.md:148
- Executable script shipped with the skillscripts/check_mcp_conformance.py
Sourcegithub.com/AeonDave/malskill/tree/main/knowledge/mcp-creator@21cd568
On this page
Build the smallest MCP surface that serves the active workflow. Preserve existing supported operations and deployment constraints when reviewing or extending a server.
Establish the project's installed SDK, target host, transport, and supported revisions first. For new servers, consider MCP 2026-07-28; verify compatibility against the official specification and the selected SDK release. Do not migrate a working server merely to repair its launch configuration. Load protocol-v2.md before changing wire behavior or making an MCP conformance claim. Distinguish:
- MCP Core 2026-07-28 — normative core protocol requirement;
- Official MCP Extension — optional, negotiated, disabled by default;
- Custom Application Pattern — architecture built with ordinary tools, resources, and explicit handles;
- Deprecated / Legacy — retained only in an isolated compatibility path;
- Experimental / Incubating — only when an official MCP source assigns that status.
Never present a custom pattern as an MCP primitive, or an official extension as core behavior.
Workflow
- Define the server's job, users, external systems, authorization model, and data sensitivity. Inspect existing entrypoints, configuration, dependencies, and tests.
- Reuse the repository's language and stack. Prefer an official MCP SDK that supports the selected revision and pin its version. Separate SDK-facing handlers from serialized protocol messages: the SDK may supply discovery, metadata, and result discriminators. Do not add wire fields to domain results or replace SDK transport logic to satisfy a text scan.
- Choose stdio for a host-launched local process; use Streamable HTTP for a service or shared endpoint when the host supports it. Load local-integration.md for launch configuration, SDK migration, local connection failures, or packaging.
- Select tools for model-callable operations (including read-only search), resources for URI-addressed context, and prompts for user-selected workflow templates. Check what the target host actually exposes. Load patterns.md for these contracts or when catalog routing, state, artifacts, Apps, or adapters require design.
- Classify each operation's execution class (wire names below are for
2026-07-28):- short and bounded: synchronous
resultType: "complete"; - needs more client input mid-call: MRTR
resultType: "input_required"; - durable asynchronous work: Tasks extension
resultType: "task"when negotiated; - arbitrary stdin, incremental output, REPL, debugger, or long-lived process: custom explicit-handle interactive lifecycle.
- short and bounded: synchronous
- Model required cross-call state with explicit server-minted handles. Add workspaces, artifacts, large-output handoff, or lifecycle tools only when the workflow needs them.
- Implement only the capabilities and extensions the workflow needs; define a bounded fallback or explicit unsupported case when host or SDK support is absent. Use protocol-v2.md for their wire contract, not as a requirement to implement every feature.
- Load security.md before exposing file, network, command, credential, UI, destructive, stateful, asynchronous, or external-handle capabilities.
- Keep MCP transport code thin. Isolate domain APIs, SDKs, subprocesses, storage, and external jobs in testable adapters.
- Load testing.md, select checks for the implemented features and deployment, then test through the configured transport with an independent MCP-aware client and the target host before claiming host compatibility.
Default Design Guidance
The wire-specific rules below apply to 2026-07-28. For an older supported revision, keep its SDK lifecycle and test that contract; do not manually remove a required handshake or session mechanism.
- Direct surface: expose stable operations directly; use
server/discoverfor protocol capabilities and application tools such aslist_catalog,get_tool, andrun_toolonly for product-level discovery and routing. - Explicit state: never rely on a connection, process, or removed protocol session as the continuity boundary.
- Optional state and data planes: when the workflow needs mutable state or large durable output, use authorized explicit handles and choose the smallest fitting workspace, artifact, or handoff pattern.
- Lifecycle visibility: make only the stateful objects the server actually exposes recoverable and cleanable without inventing MCP primitives.
- Policy visibility: when a router hides internal operations, expose a safe routing selector through
x-mcp-header, or use direct tools when infrastructure policy cannot distinguish operations safely. - Compatibility: isolate pre-
2026-07-28behavior in an adapter. Modern2026-07-28flows do not requireinitialize,notifications/initialized,Mcp-Session-Id, or connection-affine state.
Deliverables
For a plan or review, include only applicable items. Mark unsupported categories explicitly instead of designing speculative machinery:
- core RPCs, supported official extensions, and fallback behavior;
- direct tools/resources and any custom catalog families;
- operation execution classes;
- explicit-handle, workspace, artifact, and retention design when state or large data requires it;
- applicable result, error, cache, subscription, and transport-header contracts;
- authorization and safety controls;
- real-transport validation and, when publishing, publication checks;
- material open questions and explicit unsupported cases.
For implementation, make the smallest cohesive change that establishes these contracts, then verify it with repository-native tooling and a real transport.
Resources
Load the narrowest reference that matches the current subtask. Keep SKILL.md as the navigation layer; keep heavy detail in references/.
| Reference | Load when |
|---|---|
| protocol-v2.md | Wire-level implementation, migration, or any MCP conformance claim |
| patterns.md | Surface design: tools/resources/prompts, instructions, catalogs, execution, state, artifacts, Apps, adapters |
| local-integration.md | SDK/version selection or migration, host launch configuration, local connection failures, packaging |
| security.md | Exposing sensitive, stateful, asynchronous, destructive, UI, file, network, command, or credential behavior |
| testing.md | Before claiming implementation readiness or publication quality |
Scripts
Deterministic helper under scripts/:
| Script | Run when |
|---|---|
scripts/check_mcp_conformance.py |
Review raw 2026-07-28 handlers or migration notes with python scripts/check_mcp_conformance.py <path> [--strict]. It checks textual hints only: SDK-managed fields, client code, and older-version adapters can produce false positives. Run against server code, not this skill's references; neither findings nor a clean scan establish conformance. |
Files in this version
references/578.2 KB
- local-integration.md5.5 KB
- patterns.md18.9 KB
- protocol-v2.md19.6 KB
- security.md15.0 KB
- testing.md19.2 KB
scripts/29.5 KB
- check_mcp_conformance.py6.6 KB
- test_check_mcp_conformance.py3.0 KB
- SKILL.md7.3 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | Yes | Yes |
| Writes files | Yes | Yes |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | Yes | Yes |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumPrompt injection · injection.no_confirmationreferences/patterns.md:101
- MediumPrompt injection · injection.no_confirmationreferences/patterns.md:148
- MediumFile · Executable script shipped with the skillscripts/check_mcp_conformance.py
- MediumFile · Executable script shipped with the skillscripts/test_check_mcp_conformance.py
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | 2879837e | Signed | – |
More from AeonDave
All from this publisherMore in AI, agents and MCP
See the category- fal-assetsrehan-remade/fal-assets5
- ai-system-prompt-leakagenoorqureshi/ai-system-prompt-leakage4
- ai-prompt-injectionnoorqureshi/ai-prompt-injection4
- testing-prompt-injection-in-rag-pipelinesmukul975/testing-prompt-injection-in-rag-pipelines4
- implementing-llm-guardrails-for-securitymukul975/implementing-llm-guardrails-for-security4
- defending-llms-with-guardrailsmukul975/defending-llms-with-guardrails4
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login