Agent Observability

io.github.blueskylineassetsPublished by GitHub account blueskylineassetsv1.1.0Updated Oct 24, 2026

Agent observability: structured logging, cost tracking, and compliance audit trails

VerifiedSTDIODesktop onlySecurity & MonitoringData & Analytics

Overview

AI-generated overview

Lets an assistant record structured logs, track costs, and keep compliance audit trails for agent activity.

What you can do
Agent Observability is a local MCP server that connects an assistant to an Agent Observability service for structured logging, cost tracking, and compliance audit trails. The manifest does not list individual tools, so the exact operations are not documented here. It runs as a local process over stdio and sends activity to the configured API endpoint.
When to use it
Worth adding when you need a record of what an assistant or agent did, how much it cost, or evidence for a compliance audit. Less useful if you only want ad hoc local logging with no external service.
Requirements
Runs locally as an npm package over stdio, so Node.js is needed. Requires an API key in the AGENT_OBS_API_KEY environment variable, obtained by registering with the service. The AGENT_OBS_API_URL variable sets the API endpoint and defaults to a hosted URL, so network access is required.
Before you install
The server sends agent activity to an external observability service, so log content leaves your machine. It requires the secret AGENT_OBS_API_KEY, which should be stored securely and not shared. The default API URL points to a third-party host; confirm that host is acceptable before use. The manifest lists no tools, so review what data is recorded before relying on it.

Installation

In SourceWeft

  1. Open Agent Observability in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.