Skip to main content
Glama
CSOAI-ORG

Agent Audit Logger MCP

by CSOAI-ORG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a unique and well-defined purpose: logging, searching, daily stats, attestation, and chain verification. No two tools overlap in functionality.

Naming Consistency3/5

Naming is a mix: 'daily_stats' uses noun_verb, 'log' and 'search' are single verbs, while 'sign_day_attestation' and 'verify_chain' follow a verb_noun pattern. This inconsistency is noticeable but not chaotic.

Tool Count5/5

With 5 tools, the server covers the essential operations for an audit logging system: append, search, statistics, attestation, and verification. The count is well-scoped without being excessive.

Completeness5/5

The tool set provides a complete lifecycle for audit logging: log entry creation, querying, daily statistics, integrity attestation, and chain verification. No obvious gaps given the append-only nature of audit logs.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources