Run any Skill in Manus with one click

codex-mcp-checker

Stars0

Forks0

UpdatedJuly 13, 2026 at 11:28

Check Codex MCP JSON or TOML definitions, transport completeness, launcher provenance, environment handling, and runtime connectivity. Use before enabling, bundling, or releasing an MCP server.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

NDDev-it-com

NDDev-it-com/nddev-codex-app

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	codex-mcp-checker
description	Check Codex MCP JSON or TOML definitions, transport completeness, launcher provenance, environment handling, and runtime connectivity. Use before enabling, bundling, or releasing an MCP server.

Codex MCP Checker

Resolve every ../../scripts and ../../references path relative to this SKILL.md directory, never the caller working directory.

Validate the source definition, then prove the declared transport can initialize without leaking live credentials.

Workflow

Identify whether the definition is plugin .mcp.json or Codex config TOML and read ../../references/codex-artifact-contracts.md.

For a plugin definition, run:

python3 ../../scripts/check_codex_artifact.py mcp .mcp.json

Check stable unique names, required transport fields, explicit argv, valid cwd and paths, pinned mutable launchers, and complete disabled-server metadata.
Reject inline tokens, secrets, synthetic inherited servers, ambiguous shell strings, and missing authentication ownership.
Use a temporary HOME and CODEX_HOME with stub credentials. Start stdio servers or perform HTTP initialization, list tools, and exercise one safe read-only call when available.
Confirm failures are actionable and do not hang indefinitely.

Result

Return PASS only when schema, security review, and available connectivity checks succeed. Otherwise return FAIL with server name, field or runtime evidence, and correction.

More from this repository

same repository

codex-builder-orientation

NDDev-it-com/nddev-codex-app

Start here for the nddev-builder toolkit. Indexes the Codex artifact families and the creator, checker, reviewer, and workflow skill that owns each, points at the single reference for schemas and current (Beta, experimental, or under-development) surfaces, and routes the task to the right skill. Use first whenever building, checking, reviewing, or releasing a Codex artifact, or when unsure which builder skill applies.

2026-07-190

codex-onboarding

NDDev-it-com/nddev-codex-app

A guided first run of the nddev-builder toolkit — from zero to a working, checked Codex artifact in ordered steps. Use when new to nddev-builder, onboarding, or unsure which builder skill to start with.

2026-07-190

codex-marketplace-creator

NDDev-it-com/nddev-codex-app

Create or revise a Codex marketplace catalog with valid plugin sources, categories, installation policy, and authentication policy. Use when publishing local or remote plugin collections.

2026-07-190

codex-requirements-checker

NDDev-it-com/nddev-codex-app

Check a managed Codex requirements.toml layer for supported keys, permission-profile consistency, and a valid lower-layer default. Use before delivering managed /etc/codex or MDM requirements.

2026-07-190

codex-requirements-creator

NDDev-it-com/nddev-codex-app

Create a managed Codex requirements.toml layer that constrains permission profiles and other admin policy. Use when authoring the /etc/codex or MDM-delivered managed requirements a lower config layer must satisfy.

2026-07-190

codex-plugin-devtest

NDDev-it-com/nddev-codex-app

Install and iterate on a Codex plugin locally in developer mode: the install, reinstall, and cachebuster test loop for a plugin under development, run against an isolated install and never live state. Use when running or iterating on a plugin, its skills, MCP, hooks, or bundled app locally.

2026-07-190

name	codex-mcp-checker
description	Check Codex MCP JSON or TOML definitions, transport completeness, launcher provenance, environment handling, and runtime connectivity. Use before enabling, bundling, or releasing an MCP server.

Codex MCP Checker

Resolve every ../../scripts and ../../references path relative to this SKILL.md directory, never the caller working directory.

Validate the source definition, then prove the declared transport can initialize without leaking live credentials.

Workflow

Identify whether the definition is plugin .mcp.json or Codex config TOML and read ../../references/codex-artifact-contracts.md.

For a plugin definition, run:

python3 ../../scripts/check_codex_artifact.py mcp .mcp.json

Check stable unique names, required transport fields, explicit argv, valid cwd and paths, pinned mutable launchers, and complete disabled-server metadata.
Reject inline tokens, secrets, synthetic inherited servers, ambiguous shell strings, and missing authentication ownership.
Use a temporary HOME and CODEX_HOME with stub credentials. Start stdio servers or perform HTTP initialization, list tools, and exercise one safe read-only call when available.
Confirm failures are actionable and do not hang indefinitely.

Result

Return PASS only when schema, security review, and available connectivity checks succeed. Otherwise return FAIL with server name, field or runtime evidence, and correction.