io.github.MukundaKatta/agentvet
NPM · @MUKUNDAKATTA/AGENTVET-MCP · SCANNED AUG 3
Validate tool-call args before execution. Returns LLM-friendly retry hints.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- 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 (MIT).Pass
- Actively maintained (last published 98 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 295 tokens (~98/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @mukundakatta/agentvet-mcp
claude mcp add mukundakatta-agentvet -- npx -y @mukundakatta/agentvet-mcp
codex mcp add mukundakatta-agentvet -- npx -y @mukundakatta/agentvet-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mukundakatta-agentvet": {
"type": "local",
"command": [
"npx",
"-y",
"@mukundakatta/agentvet-mcp"
],
"enabled": true
}
}
} openclaw mcp add mukundakatta-agentvet --command npx --arg -y --arg @mukundakatta/agentvet-mcp
mcp_servers:
mukundakatta-agentvet:
command: "npx"
args: ["-y", "@mukundakatta/agentvet-mcp"] {
"mcpServers": {
"mukundakatta-agentvet": {
"command": "npx",
"args": [
"-y",
"@mukundakatta/agentvet-mcp"
]
}
}
} 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.
- 2 Aug 26 +7
- Install scripts: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Known CVEs: unverified → partial ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- License: pass → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- Licence: MIT functional
- 1 Aug 26 −10
- Known CVEs: partial → unverified ▼ security
- Dependency health: partial → unverified ▼ functional
- 31 Jul 26 +51
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −61
- Known CVEs: partial → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Dependency health: partial → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 29 Jul 26 +52
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Schema quality: unverified → good ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
- 28 Jul 26 −20
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 44
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@mukundakatta/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
generate_retry_message ~77
Given a tool name, validation error, and attempted args, build the canonical LLM-facing retry feedback message. Uses agentvet's ToolArgError.toLLMFeedback() formatting so the wording matches what runtime callers see.
| Name | Type | Req | Description |
|---|---|---|---|
| attempted_args | object | yes | — |
| tool_name | string | yes | — |
| validation_error | string | yes | — |
No output schema declared.
No examples provided.
lint_tool_definition ~66
Sanity-check a tool definition for common mistakes that hurt LLM tool-use accuracy: missing description, vague description, no required fields, schema fields without descriptions, non-snake_case names.
| Name | Type | Req | Description |
|---|---|---|---|
| tool | object | yes | A tool definition: { name, description, inputSchema }. |
No output schema declared.
No examples provided.
validate_tool_args ~152
Validate a tool-call args object against a small shape spec. Returns { valid, error?, retry_hint? } where retry_hint is a ready-to-send LLM feedback message describing exactly what was wrong.
| Name | Type | Req | Description |
|---|---|---|---|
| args | object | yes | The args object the LLM wants to pass. |
| shape | object | yes | Shape spec mapping field name to type. Types: "string", "number", "boolean", "array", "object". Suffix with "?" for optional. Example: { "name": "string", "age": "number", "tags": "array", "notes": "… |
| tool_name | string | yes | Name of the tool being called (surfaces in retry_hint). |
No output schema declared.
No examples provided.