# AGASTHY (mcpb · agasthy-mcp-0.1.10.mcpb)

Read-only dev-machine intelligence: repos, packages, ports, agent sessions and token cost.

- Trust score: 40/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- mcpb · `agasthy-mcp-0.1.10.mcpb`: 40/100 (this document), [markdown](https://verifymcp.io/servers/hmakt99-agasthy/agasthy-mcp.md), [page](https://verifymcp.io/servers/hmakt99-agasthy/agasthy-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/HMAKT99/Agasthy/releases/download/v0.1.10/agasthy-mcp-0.1.10.mcpb`
- Version: `0.1.10`
- Transport: `stdio`
- SHA-256: `83387f459d6ee07d5913801ab88eab18c526e6e3f7c78463f7dd69751399aa76`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 701 tokens (~77/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 85/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 56% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the AGASTHY MCP server?

AGASTHY ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 83387f459d6ee07d5913801ab88eab18c526e6e3f7c78463f7dd69751399aa76; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/HMAKT99/Agasthy/releases/download/v0.1.10/agasthy-mcp-0.1.10.mcpb`
- SHA-256: `83387f459d6ee07d5913801ab88eab18c526e6e3f7c78463f7dd69751399aa76`

### Verify on macOS / Linux

```bash
echo "83387f459d6ee07d5913801ab88eab18c526e6e3f7c78463f7dd69751399aa76  agasthy-mcp-0.1.10.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\agasthy-mcp-0.1.10.mcpb).Hash -eq "83387f459d6ee07d5913801ab88eab18c526e6e3f7c78463f7dd69751399aa76"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 40, +1)

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

### 2026-11-19 (score 39, 0)

- [security regression] Stability: 0.03 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.8 → 0.1.10

### 2026-11-18 (score 39, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.1.6 → 0.1.8
- [functional] Package version: 0.1.6 → 0.1.7

### 2026-11-17 (score 38)

First indexed and scored.

## MCP tools (9)

### `status` (~44 tokens)

Data freshness

When each kind of data (repositories, software, packages, AI tools) was last scanned, as `age_hours`, and how many items of each kind exist. Call this first.

### `find` (~137 tokens)

Find items

Search everything AGASTHY found: repositories, applications, runtimes, packages, package managers, tools, AI tools and providers, MCP servers, AI instruction files, security findings. Returns ids for `entity` and `impact`. Use `full` for all attributes, such as a repository's uncommitted work (`attributes.working_tree.value`) and branch (`attributes.head.value.branch`).

Input parameters:

- `full` (boolean): Include every attribute.
- `kind` (string): Only this kind.
- `limit` (integer)
- `text` (string): Words to search for in names, paths and attributes. Omit to list by kind.

### `entity` (~61 tokens)

Item details

One item with all its attributes, the evidence each fact came from, and its relationships (what it depends on, what depends on it).

Input parameters:

- `id` (string, required): Entity id from `find`, e.g. `package:homebrew:openssl@3`.

### `impact` (~88 tokens)

What breaks if removed

Before uninstalling a package, runtime or tool: which projects would break or fall back to another installed copy, a `risk` level (low, medium, high), a plan and how to recover. Read-only; it removes nothing.

Input parameters:

- `id` (string, required): Entity id from `find`, e.g. `package:homebrew:openssl@3`. The item you are thinking of removing.

### `shared_dependencies` (~18 tokens)

Shared dependencies

Dependencies used by the most projects on this machine.

### `agents` (~64 tokens)

Coding agents

Live coding-agent sessions (Claude Code, Codex, Cursor, Gemini CLI, Hermes, OpenClaw and others): project, memory, CPU, MCP servers and dev servers each started, and ports. `leftovers` are processes still running after the agent that started them exited.

### `processes` (~54 tokens)

Processes and ports

Running processes with the ports they listen on, memory, command line and the project each belongs to. Use it to answer "what is on port 3000?". Lists the largest by memory first.

Input parameters:

- `limit` (integer)

### `token_usage` (~74 tokens)

Token usage

Tokens used by coding agents, from their own local logs (counters only, never message text), with estimated cost from API list prices. Totals per agent; `full` adds per-session and per-day rows with project folder (`cwd`) and model.

Input parameters:

- `days` (integer)
- `full` (boolean)

### `telemetry` (~29 tokens)

Memory, CPU and disk

Memory, swap, CPU, load and disk usage right now, with the top processes by memory and CPU.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/hmakt99-agasthy/agasthy-mcp#diagnostics

## Score history

- 2026-11-21: 40
- 2026-11-20: 40
- 2026-11-19: 39
- 2026-11-18: 39
- 2026-11-17: 38

## Common questions

### What is the AGASTHY MCP server?

AGASTHY is an MCP server listed in the public MCP registry as io.github.HMAKT99/agasthy. Read-only dev-machine intelligence: repos, packages, ports, agent sessions and token cost. This page covers its MCPB bundle (https://github.com/HMAKT99/Agasthy/releases/download/v0.1.10/agasthy-mcp-0.1.10.mcpb).

### Is the AGASTHY MCP server safe to use?

AGASTHY scores 40 out of 100 on VerifyMCP. 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 AGASTHY MCP server expose?

AGASTHY exposes 9 tools: status, find, entity, impact, shared_dependencies, and 4 more. Their descriptions and schemas cost roughly 569 tokens of context every time the server is loaded.

### What licence is the AGASTHY MCP server under?

AGASTHY declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the AGASTHY MCP server?

VerifyMCP ran 12 checks on AGASTHY, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about AGASTHY: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/HMAKT99/Agasthy
- Website: https://github.com/HMAKT99/Agasthy/tree/main/integrations/mcp
- Changelog RSS feed: https://verifymcp.io/servers/hmakt99-agasthy/agasthy-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/hmakt99-agasthy/agasthy-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/hmakt99-agasthy/agasthy-mcp.json
- HTML version of this page: https://verifymcp.io/servers/hmakt99-agasthy/agasthy-mcp
