Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
Agent tracing, cost tracking, anomaly detection for LLM agents
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"agentic-observability": {
"command": "npx",
"args": [
"-y",
"agentic-observability-mcp"
]
}
}
}在终端中运行这条命令
claude mcp add agentic-observability -- npx -y agentic-observability-mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"agentic-observability": {
"command": "npx",
"args": [
"-y",
"agentic-observability-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"agentic-observability": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"agentic-observability-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 mdfifty50-boop 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.1)于7个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Context7, Codebase Memory, Exa
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
AI agent observability for MCP. Tracing, cost tracking, performance monitoring, anomaly detection, and audit trails — all via Model Context Protocol.
AI agents burn tokens, call tools, make decisions, and sometimes get stuck in loops. You need to know what they're doing, what it costs, and when something goes wrong. No existing MCP server provides unified agent observability. This one does.
Track every LLM call, every tool invocation, every decision — with automatic cost calculation and anomaly detection.
trace_agent_action — Log any agent action (tool calls, LLM requests, decisions, errors) with metadata and timestampstrack_token_usage — Track token usage per LLM call with automatic cost calculation from built-in pricing tables (Claude, GPT, Gemini, Mistral)get_cost_report — Aggregate cost breakdown across sessions, grouped by model, provider, tool, or sessionlog_tool_call — Log MCP tool calls with latency, success/failure, and error detailsget_session_summary — Full session report: cost, tokens, tool stats, error count, model breakdown, durationdetect_anomaly — Flag unusual patterns:observability://pricing — Current LLM pricing table (per-token costs for all major models)observability://best-practices — Agent observability best practices guideAdd to your MCP configuration (~/.claude/settings.json or project .mcp.json):
{
"mcpServers": { "agent-observability": { "command": "npx", "args": ["agentic-observability-mcp"] } } }
Add to .cursor/mcp.json:
{
"mcpServers": { "agent-observability": { "command": "npx", "args": ["agentic-observability-mcp"] } } }
Same pattern — add the server to your MCP configuration file.
For agent framework developers: Instrument your agent loop with track_token_usage and log_tool_call to get real-time cost and performance data without building your own telemetry.
For teams running agents in production: Use detect_anomaly to catch stuck agents (loop detection), runaway costs (cost spike), and degraded tool performance (latency spike) before they become incidents.
For cost optimization: Use get_cost_report grouped by model to identify which models are eating your budget. Switch expensive reasoning calls to cheaper models where quality allows.
For compliance and audit: Every trace_agent_action with type "decision" creates an audit record. Include reasoning in the description for full traceability.
Agent: "Track that I just used 1,500 input tokens and 800 output tokens
with claude-sonnet-4 on Anthropic for session agent_run_001"
--> Returns: { "call_cost": 0.016500, "running_session_total": 0.016500, "model": "claude-sonnet-4", "provider": "anthropic", "pricing_used": { "input": 0.000003, "output": 0.000015 }, "model_breakdown": { "claude-sonnet-4": { "calls": 1, "input_tokens": 1500, "output_tokens": 800, "cost": 0.016500 } } }
Agent: "Check session agent_run_001 for anomalies — cost spike and loop detection"
--> Returns: { "anomalies_found": 0, "anomalies": [], "checks_performed": ["cost_spike", "loop_detection"] }
Automatically calculates costs for these models (override with custom pricing if needed):
| Provider | Models |
|---|---|
| Anthropic | Claude Opus 4, Sonnet 4, Haiku 4, 3.5 Sonnet, 3.5 Haiku, 3 Opus |
| OpenAI | GPT-4o, GPT-4o Mini, GPT-4 Turbo, o1, o1-mini, o3-mini |
| Gemini 2.5 Pro, 2.5 Flash, 2.0 Flash, 1.5 Pro | |
| Mistral | Large, Medium, Small, Codestral |
| Local | Zero cost (self-hosted models) |
| Tier | Price | Agents | Retention | Events/Month |
|---|---|---|---|---|
| Free | $0 | 1 | 7 days | 10,000 |
| Starter | $59/month | 5 | 30 days | 100,000 |
| Pro | $299/month | 25 | 90 days | 1,000,000 |
| Enterprise | $999/month | Unlimited | 1 year | Unlimited + SOC2 reporting |
v1 uses in-memory storage (Maps). Data is lost on server restart. The storage layer (src/storage.js) is structured for easy swap to Redis or Postgres in v2.
MIT
mcp, mcp-server, observability, agent-tracing, cost-tracking, token-usage, ai-agent, performance-monitoring, audit-trail, model-context-protocol