Skip to content

Keesan12/Martin-Loop

vmcp-v0.3.1 scope: mcp Feature

This release adds 3 notable features for engineering teams evaluating rollout.

Published 1mo AI Agents & Assistants
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

agent-runtime ai-agent-runtime ai-coding-agents ai-control-plane ai-governance ai-safety
+13 more
audit-trail budget-enforcement claude-code codex coding-agents control-plane governed-runtime llmops mcp model-context-protocol observability policy-as-code rollback

Summary

AI summary

Improves post-run review clarity with stronger guidance and compact resources.

Full changelog

@martinloop/mcp 0.3.1

0.3.1 is the staged review and handoff release for the standalone MartinLoop MCP server.

Release story

Make post-run review feel crisp instead of forensic.

Scope in this cut

  • stronger dossier and eval guidance
  • clearer triage and publish-readiness prompts
  • compact review resources that answer what happened, what failed, and what comes next
  • handoff-safe outputs for humans and agents

Out of scope

  • hosted evidence explorer
  • audit export
  • org policy
  • fleet controls

Release gate for ship

A human reviewer or AI host should be able to understand a governed run without reconstructing MartinLoop from raw receipts.

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track Keesan12/Martin-Loop

Get notified when new releases ship.

Sign up free

About Keesan12/Martin-Loop

All releases →

Related context

Earlier breaking changes

  • vmcp-v0.1.3 martin_status uses oneOf for selector exclusivity, latest as const.
  • vmcp-v0.1.3 maxIterations and maxTokens modeled as integers in tool schemas.
  • vmcp-v0.1.3 Tool schemas enforce additionalProperties: false on public contracts.
  • vmcp-v0.1.3 Packaged artifacts now require and ship server.json alongside package.json.

Beta — feedback welcome: [email protected]