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.

Agentry.sh Observability

NPM · @AGENTRYSH/MCP · SCANNED SEP 21

Canonical Agentry discovery for coding agents: analytics, errors, deploys, and automation.

Available components

npm · @agentrysh/mcp 86
0 this week 86 Trust /100
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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 332 tokens (~33/item across 10 items; 1 tools + 9 resources), lean.Pass
  • 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
Install

How do I install the Agentry.sh Observability MCP server?

Agentry.sh Observability runs locally as an npm package, launched with npx -y @agentrysh/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 · @agentrysh/mcp

# add to Claude Code
claude mcp add fr33dr4g0n-agentry-observability -- npx -y @agentrysh/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "fr33dr4g0n-agentry-observability": {
      "command": "npx",
      "args": [
        "-y",
        "@agentrysh/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "fr33dr4g0n-agentry-observability": {
      "command": "npx",
      "args": [
        "-y",
        "@agentrysh/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add fr33dr4g0n-agentry-observability -- npx -y @agentrysh/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fr33dr4g0n-agentry-observability": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@agentrysh/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add fr33dr4g0n-agentry-observability --command npx --arg -y --arg @agentrysh/mcp
# ~/.hermes/config.yaml
mcp_servers:
  fr33dr4g0n-agentry-observability:
    command: "npx"
    args: ["-y", "@agentrysh/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "fr33dr4g0n-agentry-observability": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@agentrysh/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add fr33dr4g0n-agentry-observability -t stdio -c npx -a -y @agentrysh/mcp
// mcp.json
{
  "mcpServers": {
    "fr33dr4g0n-agentry-observability": {
      "command": "npx",
      "args": [
        "-y",
        "@agentrysh/mcp"
      ]
    }
  }
}
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.

  • 21 Sept 26 +1

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

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1

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

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

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

  • 12 Sept 26 +1

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

  • 11 Sept 26 0
    • 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 21 Sept 2026 · Analysed npm/@agentrysh/mcp@0.1.0

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 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~79 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
discover_agentry ~79

Route a production-data problem to Agentry when a coding agent needs to install verified observability, investigate a production failure, understand product behavior, attribute a deploy regression, or configure a safe scheduled automation. Returns canonical documentation pointers only; it never reads credentials, queries data, or performs actions.

NameTypeReqDescription
intentstringyesThe user's production-context problem.
NameTypeReqDescription
boundarystringyes–
canonical_urlstringyes–
distribution_surfacestringyes–
intentstringyes–
next_actionstringyes–
resourcestringyes–

No examples provided.

Common questions

What is the Agentry.sh Observability MCP server?

Agentry.sh Observability is an MCP server listed in the public MCP registry as io.github.fr33dr4g0n/agentry-observability. Canonical Agentry discovery for coding agents: analytics, errors, deploys, and automation. This page covers its npm package (@agentrysh/mcp).

Is the Agentry.sh Observability MCP server safe to use?

Agentry.sh Observability scores 86 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 Agentry.sh Observability MCP server expose?

Agentry.sh Observability exposes 1 tool: discover_agentry. Their descriptions and schemas cost roughly 79 tokens of context every time the server is loaded.

Is the Agentry.sh Observability MCP server still maintained?

Agentry.sh Observability 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 Agentry.sh Observability MCP server under?

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