Closeread Verify
Let your coding agent request a verified dependency-audit verdict over MCP before merge or release instead of parsing raw scan dumps.
Overview
Closeread Verify is a Ship-phase MCP server that delivers verified dependency-audit verdicts for AI coding agents instead of raw scan output.
What is this MCP server?
- Returns a verified dependency-audit verdict callable by any MCP agent
- PyPI package closeread-verify over stdio MCP
- Designed as structured verdict output, not an unstructured raw scan export
- Version 0.1.2 per server manifest
- Server version 0.1.2
- PyPI identifier closeread-verify
- stdio MCP transport
What problem does it solve?
Raw dependency scanners flood your agent with noise, so you cannot get a clear ship/no-ship verdict inside an automated coding loop.
Who is it for?
Solo builders who want MCP-native supply-chain checks inside Claude Code or Cursor before shipping dependency changes.
Skip if: Enterprises needing full SCA policy consoles, license compliance suites, or infra pentesting rather than dependency verdicts.
What do I get? / Deliverables
After registering the server, your agent receives a structured audit verdict you can gate merges and releases on.
- Agent-callable verified dependency-audit verdict
- Structured output suitable for merge or release gates
- Repeatable audit step in ship workflows
Recommended MCP Servers
Journey fit
Dependency trust decisions belong in Ship when you are hardening what goes to production, not when you are still sketching features. Security subphase covers supply-chain and dependency risk; a verdict-oriented audit MCP fits release gates better than generic build scaffolding.
How it compares
Verdict-first dependency audit MCP, not a generic code-review skill or interactive OS vulnerability scanner.
Common Questions / FAQ
Who is Closeread Verify for?
It is for developers and agents that need a concise, verified dependency-audit result over MCP during ship and security workflows.
When should I use Closeread Verify?
Use it when dependencies change, before release tags, or when an agent adds packages and you want a verdict instead of parsing raw scanner logs.
How do I add Closeread Verify to my agent?
Add a stdio MCP server entry pointing at the closeread-verify PyPI package per your agent’s MCP config format.