Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AgentLens

NPM · @AGENTKITAI/AGENTLENS-MCP

Tamper-evident, SHA-256 hash-chained audit trail and observability for AI agents.

0 this week 82 Trust /100

Last scanned (7 hours ago)

Scores higher than 72% of npm servers

Category Monitoring and Observability

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4297 tokens (~195/item across 22 items; 22 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Nov 26 +1
    • Stability: 0.97 → pass security
  • 1 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 26 Oct 26 +1
    • Stability: 0.97 → pass security
  • 25 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.90 → pass security
  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 −3
    • Stability: pass → 0.83 functional
  • 13 Oct 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail ▼ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@agentkitai/agentlens-mcp@0.13.7

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 22 exposed · ~4,297 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
agentlens_agents ~136

List, inspect, and manage AgentLens agents. **When to use:** To see which agents are registered, check agent details and error rates, or unpause a paused agent. **Actions:** - `list`: List all agents with error rates - `detail`: Get agent detail by ID - `unpause`: Clear paused state for an agent **Example:** agentlens_agents({ action: "list" })

NameTypeReqDescription
actionstringyesAction to perform
agentIdstring–Agent ID (required for detail/unpause)
clearModelOverrideboolean–Clear model override on unpause

No output schema declared.

No examples provided.

agentlens_alerts ~277

Manage alert rules and view alert history. **When to use:** To create alerting rules for error rates, costs, or latency thresholds; manage existing rules; or review past alert triggers. **Actions:** - `list`: List all alert rules - `create`: Create a new alert rule - `update`: Update an existing alert rule - `delete`: Delete an alert rule - `history`: View recent alert triggers **Example:** agentlens_alerts({ action: "create", name: "High error rate", condition: "error_rate_above", threshold: 0.1, windowMinutes: 60 })

NameTypeReqDescription
actionstringyesAction to perform
conditionstring–Condition: error_rate_above, cost_above, latency_above (required for create)
enabledboolean–Enable/disable rule
limitnumber–Max history results
namestring–Alert rule name (required for create)
notifyChannelsarray–Notification channels
ruleIdstring–Rule ID (required for update/delete)
scopestring–Scope: global or agentId
thresholdnumber–Threshold value (required for create)
windowMinutesnumber–Evaluation window in minutes (required for create)

No output schema declared.

No examples provided.

agentlens_analytics ~201

Query operational analytics: metrics, costs, agent performance, and tool usage. **When to use:** To understand system performance trends, cost breakdowns, agent activity, or tool usage patterns over time. **Actions:** - `metrics`: Get bucketed metrics with optional range/date filters - `costs`: Get cost breakdown - `agents`: Get per-agent metrics - `tools`: Get tool usage statistics **Example:** agentlens_analytics({ action: "metrics", range: "24h" })

NameTypeReqDescription
actionstringyesAction to perform
agentIdstring–Filter by agent ID
fromstring–Start date ISO
granularitystring–Bucket granularity
rangestring–Shorthand: 1h, 6h, 24h, 3d, 7d, 30d
tostring–End date ISO

No output schema declared.

No examples provided.

agentlens_benchmark ~431

Manage A/B benchmarks: create, list, check status, get results, and control lifecycle. **When to use:** To set up controlled experiments comparing different agent configurations (models, prompts, parameters), track which variant performs better, and get statistical results. **Workflow:** 1. `create` — Define a benchmark with 2+ variants and metrics 2. Tag sessions with variant tags during data collection 3. `start` — Transition benchmark to running 4. `status` — Check progress (session counts per variant) 5. `results` — Get statistical comparison with p-values 6. `complete` — Finalize the benchmark **Actions:** - `create`: Set up a new benchmark (name, variants[], metrics[]) - `list`: List benchmarks, optionally filter by status - `status`: Get benchmark detail with per-variant session counts - `results`: Get formatted comparison table with statistical analysis - `start`: Transition benchmark to running state - `complete`: Transition benchmark to completed state **Example:** agentlens_benchmark({ action: "create", name: "GPT-4o vs Claude", variants: [{name: "gpt4o", tag: "v-gpt4o"}, {name: "claude", tag: "v-claude"}], metrics: ["cost", "latency", "success_rate"] })

NameTypeReqDescription
actionstringyesAction to perform
agentIdstring–Agent ID to scope the benchmark to
benchmarkIdstring–Benchmark ID (required for status/results/start/complete)
descriptionstring–Benchmark description
metricsarray–Metrics to track (e.g., ["cost", "latency", "success_rate"])
minSessionsinteger–Minimum sessions per variant before results are meaningful
namestring–Benchmark name (required for create)
statusstring–Filter by status (for list action)
variantsarray–Variants to compare (required for create, min 2)

No output schema declared.

No examples provided.

agentlens_context ~231

Retrieve cross-session context for a topic — related session summaries and lessons ranked by relevance. **When to use:** At the start of a session to load relevant history, when building a system prompt with past experience, when starting work on a topic the agent has handled before, or to audit what happened with a specific topic. **What it returns:** Related sessions (with summaries, key events, and relevance scores) and related lessons, all ranked by relevance to the topic. Includes an overall summary. **Example:** agentlens_context({ topic: "database migrations", limit: 5 }) → returns past sessions about DB migrations with key events, plus any lessons learned about migrations.

NameTypeReqDescription
agentIdstring–Filter by agent ID
fromstring–Start date filter (ISO 8601)
limitnumber–Maximum number of sessions to include (default: 5)
tostring–End date filter (ISO 8601)
topicstringyesTopic to retrieve context for (natural language)
userIdstring–Filter by user ID

No output schema declared.

No examples provided.

agentlens_cost_budgets ~294

Manage cost budgets and anomaly detection. **When to use:** To create/manage spending limits, check budget utilization, or configure cost anomaly detection. **Actions:** - `list`: List all cost budgets - `create`: Create a new budget - `update`: Update an existing budget - `delete`: Delete a budget - `status`: Check spend vs limit for a budget - `anomaly_config`: Get anomaly detection configuration - `anomaly_update`: Update anomaly detection settings **Example:** agentlens_cost_budgets({ action: "create", scope: "global", period: "daily", limitUsd: 10, onBreach: "alert" })

NameTypeReqDescription
actionstringyesAction to perform
agentIdstring–Agent ID (for agent-scoped budgets)
budgetIdstring–Budget ID (required for update/delete/status)
downgradeTargetModelstring–Target model for downgrade action
enabledboolean–Enable/disable budget
limitUsdnumber–Spending limit in USD
lookbackDaysnumber–Lookback period in days for anomaly detection
onBreachstring–Action on budget breach
periodstring–Budget period
scopestring–Budget scope
zScoreThresholdnumber–Z-score threshold for anomaly detection

No output schema declared.

No examples provided.

agentlens_delegate ~207

Delegate a task to another agent in the AgentLens network. **When to use:** When you've discovered an agent capable of handling a specific task (via agentlens_discover) and want to delegate work to it. **Example:** agentlens_delegate({ action: "delegate", targetAgentId: "anon-abc123", taskType: "translation", input: { text: "Hello", targetLang: "es" } })

NameTypeReqDescription
actionstringyesOperation to perform: delegate
fallbackEnabledboolean–Enable fallback to alternative agents on failure (default: false)
input–yesInput data for the delegated task
maxRetriesnumber–Maximum retry attempts with alternative agents (default: 3, max: 10)
targetAgentIdstringyesAnonymous agent ID (from discovery results)
taskTypestringyesTask type to delegate
timeoutMsnumber–Timeout in milliseconds (default: 30000)

No output schema declared.

No examples provided.

agentlens_discover ~199

Discover available agent capabilities in the network. **When to use:** Before delegating a task, to find agents that can handle a specific task type. Returns ranked results with trust scores, estimated cost, and latency. **Example:** agentlens_discover({ action: "discover", taskType: "code-review", minTrustScore: 70, limit: 5 })

NameTypeReqDescription
actionstringyesOperation to perform: discover
limitnumber–Max results to return (default: 10, max: 20)
maxCostnumber–Maximum estimated cost in USD
maxLatencynumber–Maximum estimated latency in milliseconds
minTrustScorenumber–Minimum trust score percentile (0-100)
taskTypestringyesTask type to search for (e.g., translation, summarization, code-review, data-extraction, classification, generation, analysis, transformation, custom)

No output schema declared.

No examples provided.

agentlens_guardrails ~134

Check guardrail status for the current agent. Returns active guardrail rules, their current state, and recent trigger history. **When to use:** To check what guardrails are protecting this agent, whether any have been triggered recently, and what conditions/actions are configured. **What it returns:** A list of configured guardrail rules with their status (enabled/disabled, trigger count, last trigger time) and recent trigger history. **Example:** agentlens_guardrails({}) → returns all guardrail rules and their status.

NameTypeReqDescription
agentIdstring–Agent ID to check guardrails for (defaults to current agent)

No output schema declared.

No examples provided.

agentlens_health ~159

Check the health score of the current agent. Returns overall score (0-100), trend, and dimension breakdown. **When to use:** To assess the current health and performance of the agent, to check if error rates or latency are degrading, or to get a quick overview of agent reliability metrics. **What it returns:** An overall health score (0-100), a trend indicator (improving/stable/degrading), and a breakdown by five dimensions: error rate, cost efficiency, tool success, latency, and completion rate. **Example:** agentlens_health({ window: 7 }) → returns health score with dimension breakdown for the last 7 days.

NameTypeReqDescription
windownumber–Rolling window in days (default: 7)

No output schema declared.

No examples provided.

agentlens_log_event ~101

Log an event to an active AgentLens session.

NameTypeReqDescription
eventTypestringyesEvent type (e.g., tool_call, tool_response, custom)
metadataobject–Arbitrary metadata (tags, labels, correlation IDs)
payloadobjectyesEvent payload — structure depends on eventType
sessionIdstringyesSession ID from agentlens_session_start
severitystring–Severity level (default: info)

No output schema declared.

No examples provided.

agentlens_log_llm_call ~264

Log a complete LLM call (request + response) to an active AgentLens session. Emits paired llm_call and llm_response events.

NameTypeReqDescription
completionstring|nullyesThe completion content returned by the model
costUsdnumberyesCost of this call in USD
finishReasonstringyesStop reason (e.g., "stop", "length", "tool_use", "content_filter", "error")
latencyMsnumberyesLatency in milliseconds
messagesarrayyesThe prompt messages sent to the model
modelstringyesModel identifier (e.g., "claude-opus-4-6", "gpt-4o")
parametersobject–Model parameters (temperature, maxTokens, etc.)
providerstringyesLLM provider name (e.g., "anthropic", "openai", "google")
sessionIdstringyesSession ID from agentlens_session_start
systemPromptstring–System prompt (if separate from messages)
toolCallsarray–Tool calls requested by the model
toolsarray–Tool/function definitions provided to the model
usageobjectyesToken usage counts

No output schema declared.

No examples provided.

agentlens_optimize ~183

Get cost optimization recommendations. Analyzes LLM call patterns and suggests cheaper model alternatives. **When to use:** To identify cost-saving opportunities by switching expensive models to cheaper alternatives for tasks that don't require the most capable model. Analyzes call complexity (simple/moderate/complex) and success rates. **What it returns:** A list of model switch recommendations with estimated monthly savings, confidence levels, and success rate comparisons. Sorted by potential savings. **Example:** agentlens_optimize({ period: 7 }) → returns recommendations like "Switch gpt-4o → gpt-4o-mini for SIMPLE tasks, saving $89/month".

NameTypeReqDescription
limitnumber–Max recommendations to return (default: 5, max: 50)
periodnumber–Analysis period in days (default: 7, max: 90)

No output schema declared.

No examples provided.

agentlens_prompts ~273

Manage prompt templates and versions. **Actions:** - `list`: List prompt templates (optional category, search filters) - `get`: Get a template with all versions by ID - `create`: Create a new prompt template with initial content - `update`: Create a new version of an existing template - `analytics`: Get per-version metrics for a template - `fingerprints`: List auto-discovered prompt fingerprints **Example:** agentlens_prompts({ action: "list", category: "system" })

NameTypeReqDescription
actionstringyesAction to perform
agentIdstring–Agent ID filter (for fingerprints)
categorystring–Category filter or value
changelogstring–Change description (for update)
contentstring–Prompt content (for create, update)
descriptionstring–Template description (for create)
fromstring–Start date ISO (for analytics)
namestring–Template name (for create)
searchstring–Name search filter (for list)
templateIdstring–Template ID (for get, update, analytics)
tostring–End date ISO (for analytics)
variablesstring–JSON array of variable definitions (for create)

No output schema declared.

No examples provided.

agentlens_query_events ~62

Query events from an AgentLens session.

NameTypeReqDescription
eventTypestring–Filter by event type
limitnumber–Maximum number of events to return (default: 50)
sessionIdstringyesSession ID to query events from

No output schema declared.

No examples provided.

agentlens_reflect ~308

Analyze behavioral patterns from agent sessions — error patterns, tool sequences, cost analysis, and performance trends. **When to use:** To identify recurring errors and their root causes (error_patterns), to understand cost drivers and optimize model usage (cost_analysis), to discover common tool usage chains and their success rates (tool_sequences), or to track performance over time (performance_trends). **What it returns:** A list of structured insights with type, summary, data, and confidence score, plus metadata about how many sessions/events were analyzed. Each analysis type returns different data shapes. **Example:** agentlens_reflect({ analysis: "error_patterns", agentId: "my-agent", from: "2026-01-01" }) → returns recurring error patterns with counts, first/last seen, and affected sessions.

NameTypeReqDescription
agentIdstring–Filter analysis to a specific agent
analysisstringyesType of analysis to run: error_patterns (recurring errors), tool_sequences (common tool usage patterns), cost_analysis (cost breakdown and trends), performance_trends (success rate and duration trend…
fromstring–Start of time range (ISO 8601)
limitnumber–Maximum number of results to return (default: 20)
paramsobject–Additional parameters (e.g., { model: "gpt-4o" } for cost_analysis)
tostring–End of time range (ISO 8601)

No output schema declared.

No examples provided.

agentlens_replay ~272

Replay a past session as a structured, human-readable timeline. **When to use:** To review what happened in a previous session — understand failures, decision patterns, timing, or cost accumulation. Great for debugging or post-mortem analysis. **What it returns:** A session header (agent, status, duration, cost, event counts) followed by numbered, timestamped steps with event type icons and context annotations. **Parameters:** - sessionId (required): The session to replay - fromStep/toStep: Replay a specific step range - eventTypes: Comma-separated filter (e.g., "llm_call,tool_call") - summaryOnly: Set true to get just the summary header (fast for large sessions) **Example:** agentlens_replay({ sessionId: "ses_abc123", summaryOnly: true }) → returns session summary without steps.

NameTypeReqDescription
eventTypesstring–Comma-separated event types to filter (e.g., "llm_call,tool_call")
fromStepinteger–Start step number (0-based)
sessionIdstringyesSession ID to replay
summaryOnlyboolean–Return only the summary header (no steps). Default: false
toStepinteger–End step number (inclusive)

No output schema declared.

No examples provided.

agentlens_session_end ~54

End an active AgentLens monitoring session.

NameTypeReqDescription
reasonstringyesReason for ending the session
sessionIdstringyesSession ID to end
summarystring–Optional summary of the session

No output schema declared.

No examples provided.

agentlens_session_start ~66

Start a new AgentLens monitoring session. Returns a sessionId to use for subsequent events.

NameTypeReqDescription
agentIdstringyesUnique identifier for the agent
agentNamestring–Human-readable agent name
tagsarray–Tags for categorizing this session

No output schema declared.

No examples provided.

agentlens_sessions ~248

Browse and inspect AgentLens sessions. **When to use:** To find past sessions, inspect session details, or view a timeline of events within a session. Useful for debugging, auditing, or reviewing agent activity. **Actions:** - `list`: List sessions with optional filters (agentId, status, date range, tags) - `detail`: Get full session detail with aggregates - `timeline`: Get timestamped event list for a session **Example:** agentlens_sessions({ action: "list", agentId: "my-agent", status: "completed", limit: 10 })

NameTypeReqDescription
actionstringyesAction to perform
agentIdstring–Filter by agent ID (list)
fromstring–Start date ISO (list)
limitnumber–Max results, default 20 (list)
offsetnumber–Pagination offset (list)
sessionIdstring–Session ID (required for detail/timeline)
statusstring–Filter by status: active, completed, error (list)
tagsarray–Filter by tags (list)
tostring–End date ISO (list)

No output schema declared.

No examples provided.

agentlens_stats ~94

Get storage statistics and system overview metrics. **When to use:** To check database/storage utilization or get a high-level system overview. **Actions:** - `storage`: Get storage stats (database size, event counts, etc.) - `overview`: Get overview metrics (active sessions, agents, recent activity) **Example:** agentlens_stats({ action: "storage" })

NameTypeReqDescription
actionstringyesAction to perform

No output schema declared.

No examples provided.

agentlens_trust ~103

Get trust scores for agents. **When to use:** To check the trust/reliability score of an agent before delegating tasks or to monitor agent reputation. **Actions:** - `score`: Get trust score for a specific agent **Example:** agentlens_trust({ action: "score", agentId: "my-agent" })

NameTypeReqDescription
actionstringyesAction to perform
agentIdstring–Agent ID (required for score)

No output schema declared.

No examples provided.

Install

How do I install the AgentLens MCP server?

AgentLens runs locally as an npm package, launched with npx -y @agentkitai/agentlens-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @agentkitai/agentlens-mcp

# add to Claude Code
claude mcp add agentkitai-agentlens -- npx -y @agentkitai/agentlens-mcp
Common questions

What is the AgentLens MCP server?

AgentLens is an MCP server listed in the public MCP registry as io.github.agentkitai/agentlens. Tamper-evident, SHA-256 hash-chained audit trail and observability for AI agents. This page covers its npm package (@agentkitai/agentlens-mcp).

Is the AgentLens MCP server safe to use?

AgentLens scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AgentLens MCP server expose?

AgentLens exposes 22 tools: agentlens_session_start, agentlens_log_event, agentlens_session_end, agentlens_query_events, agentlens_log_llm_call, and 17 more. Their descriptions and schemas cost roughly 4,297 tokens of context every time the server is loaded.

Is the AgentLens MCP server still maintained?

AgentLens is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the AgentLens MCP server under?

AgentLens declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the AgentLens MCP server?

VerifyMCP ran 16 checks on AgentLens, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.