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.

AGASTHY

MCPB · AGASTHY-MCP-0.1.10.MCPB

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

40 Trust /100

Last scanned (15 hours ago)

Scores higher than 72% of MCPB servers

Category Developer Tools

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 Security0
  • 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.Unverified
  • 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).Unverified
  • Install-script risk not yet assessed.Unverified
  • 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).Unverified
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 701 tokens (~77/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 56% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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

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.

What we tested

Checks we ran (12)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (4)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain Security (scores 0 for this)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 in Supply Chain Security (scores 0 for this)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 scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)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).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +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.

  • 19 Nov 26 0
    • Stability: 0.03 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.1.8 → 0.1.10 functional
  • 18 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.1.6 → 0.1.8 functional
    • Package version: 0.1.6 → 0.1.7 functional
  • 17 Nov 26 38

    First indexed and scored.

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 Nov 2026 · Analysed mcpb/https://github.com/HMAKT99/Agasthy/releases/download/v0.1.10/agasthy-mcp-0.1.10.mcpb@0.1.10

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 9 exposed · ~569 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
agents ~64

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

entity ~61

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

NameTypeReqDescription
idstringyesEntity id from `find`, e.g. `package:homebrew:openssl@3`.

No output schema declared.

No examples provided.

find ~137

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`).

NameTypeReqDescription
fullboolean–Include every attribute.
kindstring–Only this kind.
limitinteger––
textstring–Words to search for in names, paths and attributes. Omit to list by kind.

No output schema declared.

No examples provided.

impact ~88

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.

NameTypeReqDescription
idstringyesEntity id from `find`, e.g. `package:homebrew:openssl@3`. The item you are thinking of removing.

No output schema declared.

No examples provided.

processes ~54

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.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

shared_dependencies ~18

Dependencies used by the most projects on this machine.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

status ~44

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

telemetry ~29

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

token_usage ~74

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.

NameTypeReqDescription
daysinteger––
fullboolean––

No output schema declared.

No examples provided.

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.

mcpb · agasthy-mcp-0.1.10.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

83387f459d6ee07d5913801ab88eab18c526e6e3f7c78463f7dd69751399aa76

macOS / Linux

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

Windows (PowerShell)

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

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

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.