
Agentic Observability MCP
io.github.mdfifty50-boop由 GitHub 账号 mdfifty50-boop 发布v0.1.1更新于 Oct 24, 2026
Agent tracing, cost tracking, anomaly detection for LLM agents
发布方自己的服务:agentic.no
概览
一个本地 MCP 服务器,让助手记录智能体动作、追踪 token 用量与 LLM 成本、监控工具性能并标记异常。
- 可以做什么
- 记录智能体动作、工具调用与决策,附带元数据和时戳,用于追踪与审计。按每次 LLM 调用追踪 token 用量,并依据内置价格表自动计算成本。生成按模型、提供商、工具或会话分组的成本报告。汇总会话的成本、token、工具统计、错误数与时长。检测成本激增、错误率过高、延迟激增、重复工具循环和 token 爆炸等异常。读取价格表与可观测性最佳实践等静态资源。
- 适用场景
- 适合为智能体循环加入埋点,无需自建遥测即可获得成本与性能数据;也适合在生产环境运行智能体时,提前发现卡死循环、成本失控和工具性能下降。
- 运行要求
- 通过 npx 以 stdio 在本地运行,需要 Node.js 18 或更高版本。无需 API 密钥或环境变量。存储为内存实现,服务器重启后数据丢失。
安装
在 SourceWeft 中
- 打开 控制台中的 Agentic Observability MCP,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
agentic-observability-mcp
AI agent observability for MCP. Tracing, cost tracking, performance monitoring, anomaly detection, and audit trails — all via Model Context Protocol.
Why This Exists
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.
What It Does
Tracing
trace_agent_action— Log any agent action (tool calls, LLM requests, decisions, errors) with metadata and timestamps
Cost Tracking
track_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 session
Performance Monitoring
log_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, duration
Anomaly Detection
detect_anomaly— Flag unusual patterns:- cost_spike — Session or single-call cost exceeds thresholds
- error_rate — Tool failure rate above 30%
- latency_spike — Tool calls exceeding 10s
- loop_detection — Same tool called with same params 3+ times (agent stuck)
- token_explosion — Single call or session using excessive tokens
Resources (Static Knowledge)
observability://pricing— Current LLM pricing table (per-token costs for all major models)observability://best-practices— Agent observability best practices guide
Installation
Claude Desktop / Claude Code
Add to your MCP configuration (~/.claude/settings.json or project .mcp.json):
Cursor
Add to .cursor/mcp.json:
Windsurf / VS Code
Same pattern — add the server to your MCP configuration file.
Use Cases
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.
Example
Built-in Pricing Table
Automatically calculates costs for these models (override with custom pricing if needed):
Pricing
Architecture
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.
Requirements
- Node.js 18+
- No API keys needed
- No external dependencies beyond MCP SDK and Zod
License
MIT
Keywords
mcp, mcp-server, observability, agent-tracing, cost-tracking, token-usage, ai-agent, performance-monitoring, audit-trail, model-context-protocol
来源:README.md,提交 ef24de7
工具
0版本历史
1- v0.1.1最新Sep 16, 2026
评分
已满足适用检查项的 40%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
请在仓库或注册中心条目中声明许可证。
其他 Agentic 集成
agentic.no
no.agentic官方发布者
一个远程 MCP 端点,帮助助手按模型查找 AI 推理的 GPU 卖家,按价格从低到高排序,并通过 x402 按次付费。
Agentic Engineering Periodic System
academy.ase官方发布者
使用编码代理构建软件的实践,每项实践都附带一个可在你的代码库中检查的测试。AI 翻译
Agentic RL: Credit Assignment and CLI Agents
space.hf.hoyant-su-agentic-rl官方发布者
让助手按监督方式、critic 和任务设定筛选智能体强化学习方法,并获取来源链接与 BibTeX。

Agentic Video
由 GitHub 账号 tlq5l 发布
本地 stdio MCP 服务器,让只能读文字和图片的助手检查视频文件:联系表、转录、剪辑点、响度与音画同步检查。

Agentic Os
由 GitHub 账号 kinnister 发布
只读、不执行任何操作的 MCP 服务器,向助手提供 agentic-os 的治理、SDLC 与质量工程方法论。