About Agent Infra Mcp
Agent Infra Mcp is an MCP server for AI agent infrastructure, combining persistent memory, API drift monitoring, and signed action records. Its 18 tools cover storage and search, scheduled tests, and audit receipts.
Key features
- 01Namespaced memory with TTL
- 02Batch storage and full-text search
- 03API drift tests with cron scheduling
- 04Test history and drift dashboard
- 05HMAC-signed, verifiable action receipts
Use cases
- 01Persist and search agent context
- 02Monitor endpoints for API changes
- 03Review drift test history and response times
- 04Create and verify agent action audit records
MCP support
Exposes 18 tools to MCP clients for memory, API drift detection, and trust receipts.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @lulzasaur9192/agent-infra-mcpAGENT_MEMORY_API_KEYSecretAPI key for Agent Memory serviceAGENT_DRIFT_API_KEYSecretAPI key for Agent Drift Detection serviceTRUST_RECEIPT_API_KEYSecretAPI key for Trust Receipt serviceLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
18Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| namespace | string | Yes | Namespace to organize memories (e.g. agent name, project) |
| key | string | Yes | Unique key within the namespace |
| value | any | No | Value to store (string, object, array, etc.) |
| metadata | object | No | Optional metadata tags for filtering |
| ttl_seconds | integer | No | Auto-expire after N seconds (omit for permanent) |
Details
From the project README@lulzasaur9192/agent-infra-mcp
MCP server with 18 tools for AI agent infrastructure — persistent memory, API drift detection, and HMAC-signed trust receipts.
Installation
npx @lulzasaur9192/agent-infra-mcp
Claude Desktop / Cursor
{
"mcpServers": {
"agent-infra": {
"command": "npx",
"args": ["-y", "@lulzasaur9192/agent-infra-mcp"],
"env": {
"AGENT_MEMORY_API_KEY": "your-key",
"AGENT_DRIFT_API_KEY": "your-key",
"TRUST_RECEIPT_API_KEY": "your-key"
}
}
}
}
Tools (18)
Memory (8 tools)
Persistent key-value store with namespaces, metadata, TTL, and FTS5 full-text search.
memory_store— Store a memory (namespace + key + value)memory_store_batch— Batch store up to 100 memoriesmemory_list— List memories in a namespacememory_get— Get a specific memorymemory_update— Update value, metadata, or TTLmemory_delete— Delete a memory or entire namespacememory_search— Full-text search with metadata filteringmemory_stats— Usage statistics
Drift Detection (7 tools)
Monitor API endpoints for unexpected changes with golden test cases and cron scheduling.
drift_create_test— Register a golden test (exact/subset/contains/status match)drift_list_tests— List all testsdrift_run_test— Execute a test manuallydrift_test_history— View run history and diffsdrift_update_test— Update test configurationdrift_delete_test— Remove a testdrift_dashboard— Overview with drift rate and response times
Trust Receipts (3 tools)
HMAC-SHA256 signed, tamper-proof records of agent actions for audit trails.
receipt_issue— Issue a signed receipt for an agent actionreceipt_verify— Verify receipt integrity (online or offline)receipt_list— List receipts with filters
API Keys
Each service uses its own API key:
| Service | Env Var | API |
|---|---|---|
| Memory | AGENT_MEMORY_API_KEY | agent-memory-api |
| Drift | AGENT_DRIFT_API_KEY | agent-drift-api |
| Receipts | TRUST_RECEIPT_API_KEY | trust-receipt-api |
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.