Agent Infra Mcp
Give your coding agent persistent memory, API drift alerts, and cryptographically signed trust receipts while you ship and run agent workflows.
Overview
io.github.lulzasaur9192/agent-infra-mcp is an Operate-phase MCP server that exposes 18 tools for agent memory, API drift detection, and HMAC-signed trust receipts.
What is this MCP server?
- 18 MCP tools across agent memory, API drift detection, and HMAC-signed trust receipts
- Stdio npm package @lulzasaur9192/agent-infra-mcp (server version 1.0.2)
- Separate API keys for Agent Memory, Agent Drift Detection, and Trust Receipt services
- Designed for long-running agent stacks that must prove what changed and what was trusted
- GitHub source at lulzasaur9192/agent-infra-mcp
- 18 MCP tools documented in the server description
- 3 environment variables: AGENT_MEMORY_API_KEY, AGENT_DRIFT_API_KEY, TRUST_RECEIPT_API_KEY
- npm package @lulzasaur9192/agent-infra-mcp at server schema version 1.0.2
What problem does it solve?
Agents forget prior runs, upstream APIs change without warning, and you have no signed record when an automated action needs to be defended later.
Who is it for?
Solo builders operating Claude Code or Cursor agents that call external APIs repeatedly and need memory plus drift and receipt tooling in one MCP bundle.
Skip if: Teams that only need a simple notes file or a full enterprise security operations center without third-party agent-infra API accounts.
What do I get? / Deliverables
After install and API keys, your agent can persist memory, flag drift, and produce HMAC-signed trust receipts on demand inside the same chat workflow.
- Agent-accessible memory persistence across tool calls
- Drift detection signals when external APIs diverge from expected behavior
- HMAC-signed trust receipts for selected agent actions
Recommended MCP Servers
Journey fit
Agent memory, drift detection, and trust artifacts matter once agents are in daily use and you need observability and integrity beyond a single session. Monitoring is the canonical shelf because the 18 tools center on remembering state, catching API contract drift, and issuing HMAC-signed receipts—not one-off build tasks.
How it compares
MCP-backed agent operations toolkit, not a single Claude skill or generic logging CLI.
Common Questions / FAQ
Who is io.github.lulzasaur9192/agent-infra-mcp for?
It is for indie and solo builders who run coding agents in production-like loops and want memory, drift checks, and signed trust receipts without building custom infra.
When should I use io.github.lulzasaur9192/agent-infra-mcp?
Use it during Operate and late Ship when agents call live APIs, you care about contract drift, and you need auditable receipts after automated changes.
How do I add io.github.lulzasaur9192/agent-infra-mcp to my agent?
Install the npm stdio package @lulzasaur9192/agent-infra-mcp, set AGENT_MEMORY_API_KEY, AGENT_DRIFT_API_KEY, and TRUST_RECEIPT_API_KEY, then register the server in your Claude Code or Cursor MCP config.