Agent skill · Databases

mcp-spec-checker

Predicate-level semantic diff for MCP protocol specs. Compares 0618 vs 1125 specs via Narya types, GF(3) evaluators, and Unison-style effects. Use for protocol verification, spec migration, or detecting breaking changes.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill mcp-spec-checker-plurigrid-asi-2 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 9 KB
Bundled scripts: none
Path: skills/analysis/mcp-spec-checker-plurigrid-asi-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# MCP Spec Checker Semantic diff engine for MCP protocol specifications using three independent verification approaches with mandatory cross-validation. ## Three Verification Approaches | Approach | File | Trit | Role | |----------|------|------|------| | **Narya Types** | `src/mcp_narya_types.py` | -1 (MINUS) | chk/syn/nosyn bidirectional typing | | **Agent-o-rama Evaluators** | `src/mcp_evaluators.py` | 0 (ERGODIC) | GF(3) predicate evaluation | | **Unison Effects** | `src/mcp_effects.py` | +1 (PLUS) | Algebraic effect handlers | GF(3) Conservation: `(-1) + 0 + (+1) = 0 ✓` ## GF(3) Trit Assignments for Predicates ```python # From src/mcp_spec_predicates.py PREDICATE_TRITS = { # MINUS (-1): Constraint/validation predicates "has_required_field": -1, "type_matches": -1, "schema_valid": -1, # ERGODIC (0): Coordination predicates "version_compatible": 0, "capability_negotiated": 0, "session_active": 0, # PLUS (+1): Generation/action predicates "tool_invoked": +1, "response_emitted": +1, "resource_created": +1, } ``` ## Denotation > **This skill compares MCP protocol specs at the predicate level, detecting semantic differences between versions and generating minimal counterexamples for

What's inside
Steps it walks through
  1. Three Verification Approaches
  2. GF(3) Trit Assignments for Predicates
  3. Denotation
  4. Invariant Set
  5. GF(3) Typed Effects
  6. Narya Compatibility
  7. Condensation Policy
  8. Invariant Sets
  9. Inv0618 (June 2024 Spec)
  10. Inv1125 (November 2025 Spec)
  11. Semantic Diff (Not Text Diff)
  12. Counterexample Generation
  13. Cross-Validation (All 3 Approaches Must Agree)
  14. Disagreement Handling
Ships with 1 file
  • metadata.json
Commands it runs
Compare two spec versions
just mcp-spec-diff 0618 1125
Validate message against spec
just mcp-spec-check message.json --spec 1125
Generate counterexamples for all breaking changes
just mcp-spec-counterex 0618 1125
Cross-validate with all three approaches
just mcp-spec-validate message.json --cross-validate
Run test trace
just mcp-spec-trace tests/protocol_trace.jsonl
More from claude-skill-registry
All skills →
About this skill
What does the mcp-spec-checker skill do?

Predicate-level semantic diff for MCP protocol specs. Compares 0618 vs 1125 specs via Narya types, GF(3) evaluators, and Unison-style effects. Use for protocol verification, spec migration, or detecting breaking changes.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill mcp-spec-checker-plurigrid-asi-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going