Using VIA ID in MCP-based agents

VIA ID doesn't ship its own MCP server today. What exists — and works right now — is an Agent Skills package plus a plain CLI, which is how VIA ID reaches MCP-based coding agents in practice.

What works today

Claude Code, Cursor, Windsurf, and other MCP/agent-skills-capable clients pick up VIA ID through the standard skill-install flow:

npx skills add SathiaAI/viaid

Once installed, the agent has the SKILL.md instructions loaded and can shell out to bin/viaid.mjs (init / log / verify / rotate, and the GraphSmith/KnoSky-dependent eval / scan / gate) as part of its own workflow — for example, minting a badge for itself when it ships, or logging its own actions as it works. See Integrate your agent for the exact commands and phases.

This is "MCP-compatible" in the sense that it works inside MCP-based coding agents today — it's a skill + CLI they invoke, not a tool they call over the Model Context Protocol itself.

Planned: a dedicated MCP server

A VIA ID MCP server — exposing init / log / verify / rotate (and eventually eval / scan / gate) as proper MCP tools rather than shell-outs — is on the roadmap but not built yet. This page will be updated with real usage instructions once it exists; until then, the CLI/skill flow above is the supported integration path.

If your use case specifically needs MCP-native tool calls rather than a shell-out, that's useful signal — let us know what you're building.