Keldyn MCP

    Your requirements, inside your coding agent.

    Keldyn MCP gives your software agents your security and compliance requirements, so they build it right the first time.

    Claude Code · keldyn connected
    > Which SOC 2 requirements does the payments service meet?
    keldyn
    ✓ Encryption at rest
    ✓ Access logging on admin routes
    ✓ Input validation on public endpoints
    ✕ Key rotation: no rotation policy found for the payments key
    Created task TSK-018: Add key rotation for payments
    > Add it, following our requirements
    How it works

    Built right while the code is written.

    Connect once. From then on, your agent knows which requirements apply to what it is building, and builds to them.

    Claude session using Keldyn MCP: an architecture analysis with prioritised remediation and findings by framework
    For agent pipelines

    Check at the gates, not on every draft.

    When hundreds of agents work in parallel, most of what they write never ships. Keldyn plugs into the gates your orchestrator already has, so compliance costs scale with what you ship, not with what you try.

    01
    ExploreAgents try ideas in worktrees. Most get thrown away, so Keldyn stays out of the way.
    02
    JudgeCritic and judge agents keep what is worth building.
    03
    Keldyn gateRequirements checked and evidence recorded before anything merges.
    04
    ShipOnly checked work reaches production.
    Give Keldyn to the agents that need it
    Architects, reviewers and judges get your requirements. Agents brainstorming in a worktree don't, so you don't spend tokens on them.
    Fits the orchestrator you have
    Plug Keldyn into the gates between exploring and shipping, so you only check what survives.
    Requirements travel with the spec
    Agents pull the controls that apply into the spec before they build, so compliance moves with the work.
    What is an MCP?

    One plug between your agent and Keldyn.

    MCP is an open standard that lets AI agents use outside tools. Think USB-C for AI. Connect Keldyn once, and your coding agent can look up your security and compliance requirements, and record the work it does against them.

    Setup guide →
    Your coding agent
    Claude Code
    Cursor
    Keldyn MCP server
    Signed in as you · scoped to your team
    keldyn
    Requirements · Evidence · Tasks
    Read your requirements
    Frameworks, controls and the audits they are in scope for, so the agent knows what applies before it writes a line.
    Record the proof
    Update controls, add evidence, log risk decisions and create or close tasks, straight from the session.
    Map your architecture
    Run one prompt and your architecture, data flows and threats appear in Keldyn, ready for your policies and audit.
    Private by design
    ✓Your code stays with you✓Nothing written to disk✓Never used for trainingHow data flows →
    "The first time I ran it, it went through the whole codebase, told me what was missing, and pushed the lot into Jira as tickets. It did a serious amount of my work for me."
    Tim BrownTim Brown, Co-Founder, Kyance
    Read the Kyance story →
    Kyance at a glance

    Trust infrastructure for agentic commerce

    ✓
    SOC 2 from day one

    Mapped while the architecture was still moving.

    ✓
    Checked where the code is written

    Findings surface in the coding agent and land in Jira.

    ✓
    Evidence, not archaeology

    Fixes and configuration build up against the audit from the start.

    Google CloudGitHubJiraClaude Code

    Give your agents your requirements.