AgentLens
NPM · @AGENTKITAI/AGENTLENS-MCP · SCANNED SEP 21
Tamper-evident, SHA-256 hash-chained audit trail and observability for AI agents.
Available components
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
- 31 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 85 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add agentkitai-agentlens -- npx -y @agentkitai/agentlens-mcp
{
"mcpServers": {
"agentkitai-agentlens": {
"command": "npx",
"args": [
"-y",
"@agentkitai/agentlens-mcp"
]
}
}
} {
"servers": {
"agentkitai-agentlens": {
"command": "npx",
"args": [
"-y",
"@agentkitai/agentlens-mcp"
]
}
}
} codex mcp add agentkitai-agentlens -- npx -y @agentkitai/agentlens-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"agentkitai-agentlens": {
"type": "local",
"command": [
"npx",
"-y",
"@agentkitai/agentlens-mcp"
],
"enabled": true
}
}
} openclaw mcp add agentkitai-agentlens --command npx --arg -y --arg @agentkitai/agentlens-mcp
mcp_servers:
agentkitai-agentlens:
command: "npx"
args: ["-y", "@agentkitai/agentlens-mcp"] {
"McpServers": {
"agentkitai-agentlens": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@agentkitai/agentlens-mcp"
]
}
}
} assistant mcp add agentkitai-agentlens -t stdio -c npx -a -y @agentkitai/agentlens-mcp
{
"mcpServers": {
"agentkitai-agentlens": {
"command": "npx",
"args": [
"-y",
"@agentkitai/agentlens-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 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.
- 15 Sept 26 −3
- Stability: pass → 0.77 functional
- 14 Sept 26 +1
- Stability: 0.97 → pass security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 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.
- 9 Sept 26 −3
- Stability: pass → 0.83 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
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 21 Sept 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 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
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" })
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| agentId | string | – | Agent ID (required for detail/unpause) |
| clearModelOverride | boolean | – | 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 })
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| condition | string | – | Condition: error_rate_above, cost_above, latency_above (required for create) |
| enabled | boolean | – | Enable/disable rule |
| limit | number | – | Max history results |
| name | string | – | Alert rule name (required for create) |
| notifyChannels | array | – | Notification channels |
| ruleId | string | – | Rule ID (required for update/delete) |
| scope | string | – | Scope: global or agentId |
| threshold | number | – | Threshold value (required for create) |
| windowMinutes | number | – | 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" })
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| agentId | string | – | Filter by agent ID |
| from | string | – | Start date ISO |
| granularity | string | – | Bucket granularity |
| range | string | – | Shorthand: 1h, 6h, 24h, 3d, 7d, 30d |
| to | string | – | 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"] })
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| agentId | string | – | Agent ID to scope the benchmark to |
| benchmarkId | string | – | Benchmark ID (required for status/results/start/complete) |
| description | string | – | Benchmark description |
| metrics | array | – | Metrics to track (e.g., ["cost", "latency", "success_rate"]) |
| minSessions | integer | – | Minimum sessions per variant before results are meaningful |
| name | string | – | Benchmark name (required for create) |
| status | string | – | Filter by status (for list action) |
| variants | array | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | – | Filter by agent ID |
| from | string | – | Start date filter (ISO 8601) |
| limit | number | – | Maximum number of sessions to include (default: 5) |
| to | string | – | End date filter (ISO 8601) |
| topic | string | yes | Topic to retrieve context for (natural language) |
| userId | string | – | 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" })
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| agentId | string | – | Agent ID (for agent-scoped budgets) |
| budgetId | string | – | Budget ID (required for update/delete/status) |
| downgradeTargetModel | string | – | Target model for downgrade action |
| enabled | boolean | – | Enable/disable budget |
| limitUsd | number | – | Spending limit in USD |
| lookbackDays | number | – | Lookback period in days for anomaly detection |
| onBreach | string | – | Action on budget breach |
| period | string | – | Budget period |
| scope | string | – | Budget scope |
| zScoreThreshold | number | – | 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" } })
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Operation to perform: delegate |
| fallbackEnabled | boolean | – | Enable fallback to alternative agents on failure (default: false) |
| input | – | yes | Input data for the delegated task |
| maxRetries | number | – | Maximum retry attempts with alternative agents (default: 3, max: 10) |
| targetAgentId | string | yes | Anonymous agent ID (from discovery results) |
| taskType | string | yes | Task type to delegate |
| timeoutMs | number | – | 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 })
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Operation to perform: discover |
| limit | number | – | Max results to return (default: 10, max: 20) |
| maxCost | number | – | Maximum estimated cost in USD |
| maxLatency | number | – | Maximum estimated latency in milliseconds |
| minTrustScore | number | – | Minimum trust score percentile (0-100) |
| taskType | string | yes | Task 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| window | number | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| eventType | string | yes | Event type (e.g., tool_call, tool_response, custom) |
| metadata | object | – | Arbitrary metadata (tags, labels, correlation IDs) |
| payload | object | yes | Event payload — structure depends on eventType |
| sessionId | string | yes | Session ID from agentlens_session_start |
| severity | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| completion | string|null | yes | The completion content returned by the model |
| costUsd | number | yes | Cost of this call in USD |
| finishReason | string | yes | Stop reason (e.g., "stop", "length", "tool_use", "content_filter", "error") |
| latencyMs | number | yes | Latency in milliseconds |
| messages | array | yes | The prompt messages sent to the model |
| model | string | yes | Model identifier (e.g., "claude-opus-4-6", "gpt-4o") |
| parameters | object | – | Model parameters (temperature, maxTokens, etc.) |
| provider | string | yes | LLM provider name (e.g., "anthropic", "openai", "google") |
| sessionId | string | yes | Session ID from agentlens_session_start |
| systemPrompt | string | – | System prompt (if separate from messages) |
| toolCalls | array | – | Tool calls requested by the model |
| tools | array | – | Tool/function definitions provided to the model |
| usage | object | yes | Token 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".
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max recommendations to return (default: 5, max: 50) |
| period | number | – | 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" })
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| agentId | string | – | Agent ID filter (for fingerprints) |
| category | string | – | Category filter or value |
| changelog | string | – | Change description (for update) |
| content | string | – | Prompt content (for create, update) |
| description | string | – | Template description (for create) |
| from | string | – | Start date ISO (for analytics) |
| name | string | – | Template name (for create) |
| search | string | – | Name search filter (for list) |
| templateId | string | – | Template ID (for get, update, analytics) |
| to | string | – | End date ISO (for analytics) |
| variables | string | – | JSON array of variable definitions (for create) |
No output schema declared.
No examples provided.
agentlens_query_events ~62
Query events from an AgentLens session.
| Name | Type | Req | Description |
|---|---|---|---|
| eventType | string | – | Filter by event type |
| limit | number | – | Maximum number of events to return (default: 50) |
| sessionId | string | yes | Session 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | – | Filter analysis to a specific agent |
| analysis | string | yes | Type 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… |
| from | string | – | Start of time range (ISO 8601) |
| limit | number | – | Maximum number of results to return (default: 20) |
| params | object | – | Additional parameters (e.g., { model: "gpt-4o" } for cost_analysis) |
| to | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| eventTypes | string | – | Comma-separated event types to filter (e.g., "llm_call,tool_call") |
| fromStep | integer | – | Start step number (0-based) |
| sessionId | string | yes | Session ID to replay |
| summaryOnly | boolean | – | Return only the summary header (no steps). Default: false |
| toStep | integer | – | End step number (inclusive) |
No output schema declared.
No examples provided.
agentlens_session_end ~54
End an active AgentLens monitoring session.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | yes | Reason for ending the session |
| sessionId | string | yes | Session ID to end |
| summary | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Unique identifier for the agent |
| agentName | string | – | Human-readable agent name |
| tags | array | – | 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 })
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| agentId | string | – | Filter by agent ID (list) |
| from | string | – | Start date ISO (list) |
| limit | number | – | Max results, default 20 (list) |
| offset | number | – | Pagination offset (list) |
| sessionId | string | – | Session ID (required for detail/timeline) |
| status | string | – | Filter by status: active, completed, error (list) |
| tags | array | – | Filter by tags (list) |
| to | string | – | 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" })
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action 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" })
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform |
| agentId | string | – | Agent ID (required for score) |
No output schema declared.
No examples provided.
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 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 21 September 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.