Slipmark

Name: Slipmark
Author: founder-ship-it

제작자: founder-ship-it버전 0.6.2i★ –i내 컴퓨터에서 실행

레지스트리 이름io.github.founder-ship-it/slipmark

설치

개요

제작자가 쓴 설명(영어 원문)

Record AI agent verdicts bound to file hashes; refuse ones whose files or instructions changed.

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

사용자 의견i아직 리뷰가 없어요리뷰는 다음 단계에서 계정 기능과 함께 열려요
우리의 기본 점검i1개 중 1개 통과공개된 정보로 점검했으며, 코드는 아직 스캔하지 않았어요
사용 정도i아직 측정 안 함★ –

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

연결 방식: 내 컴퓨터에서 실행
전송 방식: stdio
카테고리: 기타

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

기본 점검: 1개 중 1개 통과
내 컴퓨터에서 내 사용자 계정의 권한(파일, 네트워크, 앱)으로 실행돼요.
레지스트리에 입력해야 할 키가 나와 있지 않아요.

필요한 것

npmNode.js 설치(npx 명령어용)

어떤 앱을 쓰세요?

ClaudeClaude CodeCursorVS CodeChatGPT

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요

{
  "mcpServers": {
    "slipmark": {
      "command": "npx",
      "args": [
        "-y",
        "slipmark",
        "mcp"
      ]
    }
  }
}

터미널에서 이 명령어를 실행하세요

claude mcp add slipmark -- npx -y slipmark mcp

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

{
  "mcpServers": {
    "slipmark": {
      "command": "npx",
      "args": [
        "-y",
        "slipmark",
        "mcp"
      ]
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

{
  "servers": {
    "slipmark": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "slipmark",
        "mcp"
      ]
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검

✓ 통과
제작자와 저장소 일치
레지스트리 이름이 GitHub 계정 founder-ship-it 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
… 아직 점검 안 함
계속 관리되고 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
… 아직 점검 안 함
라이선스 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
– 해당 없음
엔드포인트 응답
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
– 해당 없음
OAuth로 로그인
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
… 아직 점검 안 함
도구 설명에 숨겨진 지시 없음
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요

기타 카테고리의 다른 서버와 비교i

이 카테고리의 다른 서버 32583개 중 0%보다 스타가 많아요
이 카테고리의 다른 서버 32583개 중 88%보다 최근에 레지스트리에 공개됐어요
기본 점검 결과가 이 카테고리의 다른 서버 32583개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

Slipmark, 안전한가요?

해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.6.2)은 4일 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, sync. labs

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Spec Driven Development

제작자: formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

내 컴퓨터에서 실행★ 440MIT14개월 전 업데이트

설치

Remote Desktop Commander

제작자: desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

클라우드에서 실행★ 211어제 업데이트

설치

sync. labs

제작자: synchronicity-labs

Lipsync videos, dub them into other languages, make talking videos and open sync. Studio.

컴퓨터 또는 클라우드오늘 업데이트

설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

Slipmark

*A Reply Intelligence Group project.*

Make AI agents prove what they checked.

Add it to a workflow:

- uses: actions/checkout@v4

uses: founder-ship-it/Slipmark@v0.6.2 with: require: | specs/your-spec.md

When a file changes after an agent signed it off, the build refuses:

Slipmark verify: 1 verified · 1 refused

✓ verified review-agent verified examples/attestation/brief.md ✗ hash_mismatch security-audit-agent gave "cleared" for a different version of examples/attestation/spec.md. The file changed after the verdict.

Set it up in one command: npx slipmark init. Your coding agents then write their sign-off with slipmark attest (see Works with your coding agent). No model calls, no account, one GitHub Action.

A slip mark is the paint line engineers draw across a bolt once it has been tightened and checked. If the bolt ever moves, the line breaks and everyone can see it. Slipmark does the same for AI agent verdicts: once an agent signs off a file, any change after that breaks the mark.

Agents now review code, audit specs and sign off their own work. The weak point is the verdict. An agent can report "passed" about a file that has since changed, or that it never looked at, and nothing downstream can tell.

Slipmark does two things:

Verdict attestation. Every agent verdict is bound to a SHA-256 hash of the exact files the agent read. Before anything ships, the gate re-hashes them. Mismatch, missing file, failing verdict, or nothing attested at all: it refuses. Deterministic, no model calls, one GitHub Action.
Drift diagnosis. Behavioural "locks" for your AI features. When a change breaks one, Slipmark says what likely broke it, how sure it is (and refuses to fake confidence it doesn't have), and hands your coding agent a repair prompt.

Status: v0.6.2, early. Apache-2.0. Optional hosted layer: Slipmark Cloud.

Why the gate exists

We run a nightly pipeline of 20+ agents: research, architecture, security audit, build, QA. Every morning they reported what passed.

Then we found the final verification job had been checking the wrong branch for months. It could not fail, so it never did. Months of green ticks, proving nothing.

So we built the gate: bind every verdict to the hash of what it read, and re-check before shipping. Pointed at 23 open agent pull requests, it refused all 23.

What Slipmark proves, and what it doesn't

Slipmark doesn't decide whether your agent is right. It makes sure the verdict you are trusting is about the code you are shipping.

It proves:

The verdict was given on these exact bytes. Change one and the verdict stops counting.
Every file you require has a current, passing verdict. A missing verdict is a refusal, not a silent pass.
The answer is the same every time. No model calls, no scoring, no judgement.

It doesn't prove:

That the agent was smart. If an agent misses a bug on day one, Slipmark will pass that file for as long as it stays unchanged. That is the agent's verdict, faithfully kept.
Who wrote an unsigned attestation. Anyone who can push can write "by": "security-reviewer". Require signed verdicts and only verdicts signed by a workflow you trust count.

So pair it with the checks you already trust. Slipmark is the lock on the verdict, not the verdict. If you want stronger verdicts, require more of them: coverage of every changed file, checks Slipmark runs itself, or a re-review when the model changes. Those are on main now (docs/attestation.md). Two independent reviewers on sensitive paths, and the rest of attestation v2, are next.

Quick start

In the repository you want to protect (Node 22.6 or later):

npx slipmark init

  + create .slipmark/attestations/.gitkeep      attestation directory, committed with the repo

create .github/workflows/slipmark.yml report-only gate on pull requests
create AGENTS.md agent instructions for attesting verdicts ~ update CLAUDE.md agent instructions for attesting verdicts

That is the whole setup:

A workflow that runs the gate on every pull request. It starts in report-only mode, because a repo with no verdicts yet would otherwise fail. Set fail-on-refusal: "true" once your agents are attesting.
Agent instructions in AGENTS.md, plus CLAUDE.md, Cursor rules or Copilot instructions if your repo already has them. Re-running init updates the block in place and never touches anything else in those files.

Check any time with npx slipmark verify. Commit .slipmark/attestations/.

Works with your coding agent

The instructions init writes are enough for agents to attest on their own. We gave Claude Code a plain review task in a fresh repo, with no mention of Slipmark:

Review src/export.ts against specs/invoice-export.md. Does it meet the spec?

It read both files, found the export was not CSV, and recorded:

"by": "reviewer", "verdict": "fail", "subjects": [ { "path": "src/export.ts", "sha256": "0ea6029f…" }, { "path": "specs/invoice-export.md", "sha256": "81994e0f…" } ], "note": "Tenant filter and 10k limit OK; no CSV output, returns raw query result" }

Both files it based the verdict on, not just the one under review. When the code is fixed, the old verdict stops counting until the agent reads it again.

Setup notes for Claude Code, Cursor, Copilot and Codex are in docs/agents.md.

Claude Code plugin

For Claude Code there is also a plugin. It adds a skill so Claude records verdicts without any repo instructions, /slipmark:verify and /slipmark:setup commands, and a stop check that asks Claude to re-read and re-attest when a file it signed off has changed since.

/plugin marketplace add founder-ship-it/Slipmark

/plugin install slipmark@slipmark

Details, including exactly what it runs, in claude-plugin/.

MCP server: Codex, Cursor, Copilot, Gemini

slipmark mcp serves slipmark_attest and slipmark_verify as MCP tools, so any agent that speaks MCP can record and check verdicts. For OpenAI Codex, in ~/.codex/config.toml:

[mcp_servers.slipmark]

command = "npx" args = ["-y", "slipmark@0.6.2", "mcp"]

Setup for Claude Code, Cursor, Copilot in VS Code and Gemini CLI is in docs/mcp.md. Agents can't record a human approval through it.

Verdict attestation

1. The agent attests what it read. Call this at the end of any agent step that gives a verdict:

slipmark attest --by security-audit-agent --verdict cleared \

--subject specs/invoice-export.md --subject src/export.ts

That writes .slipmark/attestations/ -- .json:

"schema": "slipmark/attestation@1", "by": "security-audit-agent", "verdict": "cleared", "at": "2026-10-17T09:00:00.000Z", "subjects": [ { "path": "specs/invoice-export.md", "sha256": "cf89da70…" } ] }

2. The gate checks it before anything ships.

slipmark verify --require specs/invoice-export.md

Result	Meaning
`verified`	Passing verdict, and the file is byte-for-byte what the agent saw
`hash_mismatch`	The file changed after the verdict. The verdict is about a different file.
`subject_missing`	The attested file no longer exists
`verdict_not_passing`	The agent said fail or blocked
`unattested`	A `--require`d file has no current, passing verdict, or there are no attestations at all
`invalid`	Malformed attestation, or a path outside the repo

Passing verdicts are pass and cleared. An empty gate is a refusal, never a silent pass. --json prints the full report for other tools.

Stronger verdicts (on main, unreleased). Record what the verdict was checked against, and let Slipmark run the checks itself:

slipmark attest --by reviewer --verdict pass --subject src/export.ts \

--against specs/invoice-export.md --run "npm test"

A failing --run refuses a passing verdict. Then require a verdict for every changed file, not just the ones you listed:

slipmark verify --coverage diff --base origin/main

Details in docs/attestation.md.

Agent context

Your reviewer passed the code. But who wrote the reviewer's instructions? The coding-agent attacks of 2026 changed AGENTS.md, skills and MCP configs and left the reviewed code alone. Add "context": {} to .slipmark/policy.json and Slipmark binds each verdict to the agent's instructions too:

a verdict given under instructions that later changed stops counting
a change to AGENTS.md, CLAUDE.md, a skill or an MCP config needs an approver's verdict (pair it with CODEOWNERS, or require signed approvals)
changed instructions must be plain Markdown that GitHub shows in full: an allow-list refuses anything else (HTML, comments, images, diagrams, anything GitHub adds later), and in GitHub Actions each file is checked against GitHub's own renderer
context files that link outside the watched set are refused

The policy is read from the base branch, so a pull request can't switch this off. What it doesn't cover yet is listed in the docs. Details in docs/attestation.md.

See it refuse five real attack patterns (Ghostcommit, Deadbugz, hidden comments, invisible Unicode, a PR switching the checks off) as open pull requests in slipmark-context-demo.

Signed verdicts

Prove who gave the verdict, not just what it was about (on main, unreleased). Run the review agent in a GitHub Actions job and sign as it attests:

slipmark attest --by security-reviewer --verdict pass --subject src/auth/session.ts --sign

The verdict is signed with the job's own GitHub identity through Sigstore: no keys to manage, and every signature is in a public transparency log. Then only count verdicts from the workflow you trust:

- uses: founder-ship-it/Slipmark@main

with: require-signed: "true" trusted-signers: | https://github.com/acme/api/.github/workflows/agent-review.yml@refs/heads/main

A verdict typed by hand, made by another workflow, or edited after signing is refused. Details, including which ref to trust, in docs/attestation.md.

As a GitHub Action:

- uses: actions/checkout@v4

uses: founder-ship-it/Slipmark@v0.6.2 with: require: | specs/invoice-export.md

Rolling it out gently? Set fail-on-refusal: "false" to report refusals as warnings without failing the build. The step's result output is passed or refused either way.

Formatters. A formatter run changes the bytes, so it breaks a verdict like any other change. Run formatters before your agent attests (first in your pre-commit hooks) and most of this goes away. Formatting-tolerant hash modes and re-reviewing only the diff are planned for v0.5.

Run it on the branch you are about to merge. Because it checks content, not branch names, a verdict produced on one branch can't clear a different tree.

Slipmark Cloud

The gate above is free, open source and needs no account. Slipmark Cloud is the optional hosted layer for teams that need the record, not just the build result:

An append-only, hash-chained ledger o

앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요

Slipmark

개요

PopNx MCP의 세 기둥

할 수 있는 일

설치

설치하기 전에

할 수 있는 일

기본 점검i

제작자와 저장소 일치

계속 관리되고 있음

라이선스 있음

엔드포인트 응답

OAuth로 로그인

도구 설명에 숨겨진 지시 없음

기타 카테고리의 다른 서버와 비교i

자주 묻는 질문

대안

Spec Driven Development

Remote Desktop Commander

sync. labs

제작자의 README

Slipmark

Why the gate exists

What Slipmark proves, and what it doesn't

Quick start

Works with your coding agent

Claude Code plugin

MCP server: Codex, Cursor, Copilot, Gemini

Verdict attestation

Agent context

Signed verdicts

Slipmark Cloud