Schema | Agent Audit Logger MCP

Agent Audit Logger MCP

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
logA	Append a signed, hash-chained log entry. tenant_id: customer / organisation identifier from_agent: calling agent id (e.g. "orchestrator") to_agent: receiving agent id (e.g. "compliance-scorer") action: what was requested (e.g. "score_dora_compliance") payload_hash: SHA256 of the payload body (keeps logs small + hides PII) outcome: success \| fail \| timeout \| blocked context_csv: optional comma-separated tags (e.g. "high-risk,financial")
verify_chainB	Re-verify the integrity of the log chain for a tenant. Returns OK or the first sequence number where the chain breaks.
searchB	Query the log. Empty filters match everything. Returns newest-first.
daily_statsC	Return daily log volume stats for a tenant.
sign_day_attestationA	Emit a signed attestation certifying the log integrity + volume for a given day. Pro/Enterprise only. Use this as end-of-day evidence for your auditor / Trust Center. The attestation includes the tip hash at end-of-day so anyone can later prove the log wasn't retroactively modified.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CSOAI-ORG/agent-audit-logger-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server