Pure skill · Codex-first

Make your MCPhold up.

Build with the right contract. Trace what actually runs. Keep every claim within the evidence you have.

Inspect a specimen Use the skill

One skill/No extra service/Useful at the seam

Boundary study / 001Synthetic specimen

Source contractinspected

Local processobserved

Named hostnot verified

The local result stands. The host question stays open.

At the seam

Protocol. SDK. Transport. Host. A good implementation knows which layer owns the work—and checks that layer before claiming success.

01 / In practice

Green tests.
A more useful question.

Look at the evidence, then choose the claim it can support. Sometimes that reveals a defect. Sometimes it removes an unnecessary requirement.

Observed materialIllustrative only

specimen/host-observation.txt

claim:  "Ready in the target host"
source: self-contained HTML resource
local:  renders in Playwright
host:   no recorded observation

A browser surrogate exercises local behavior. It cannot record what a different host admitted or rejected.

Bounded conclusionNOT VERIFIED

A local render leaves the host question open.

The local rendering observation is useful. There is no host-side observation for this exact resource, so target-host compatibility remains unverified. That does not establish a host failure.

Next useful check
Exercise the exact resource in the named host and record its observed disposition.

Verified, contradicted, not verified, and not applicable describe different relationships to a claim. They are not a universal progress bar.

02 / The method

A small skill.
A sharper judgment.

The plugin brings the relevant engineering method into the repository task already in front of you. No second management system. No report required for a one-line change.

Read the Field Guide

Choose the actual contract.

Identify the declared protocol, the SDK generation, and the path the implementation exercises. An upgrade target does not rewrite a historical baseline.

Find the layer that can enforce it.

A parent-owned stdio tool and a browser-reachable HTTP service have different surfaces. Keep controls at their actual point of effect.

Finish the change the user asked for.

Implementation requests should reach a working change and relevant verification. Migrations also check retained compatibility and deliberately retired behavior.

Say exactly what was established.

Keep source inspection, runtime observation, host admission and owner acceptance distinct. Preserve a valid result without stretching it.

03 / Work with it

Start from
the real task.

Install from the public repository, then use one entrypoint at the depth the task actually needs.

codex plugin marketplace add IndelibleVivi/mcp-boundary --ref main
codex plugin add mcp-boundary@mcp-boundary

Use $mcp-boundary to inspect this MCP implementation against its declared protocol, actual transport and intended deployment. Trace the relevant behavior. Report actionable findings, valid results and any material verification gaps. Do not edit the repository.

Prompt template / installed plugin required

Installing from source is separate from directory publication. The plugin adds one skill and no service, auth flow, telemetry or runtime dependency.

The status is part of the design.

Version 0.1.0 / explicitly bounded

Source & Codex-native package

included

Author source, canonical Codex manifest, provenance, legal map, tests and one approved website are included in the repository.

Installed model behavior

not verified

Static trigger design and fixtures do not establish implicit model invocation or comparative behavior.

Directory & named-host release

not published

No external directory listing, production integration or named-host acceptance is implied.