io.github.MukundaKatta/agentvet
NPM · @MUKUNDAKATTA/AGENTVET-MCP
Validate tool-call args before execution. Returns LLM-friendly retry hints.
Available components
Last scanned (17 hours ago)
Scores higher than 73% of npm servers
Category Developer Tools
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 Security98
- 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
- 31 of 93 dependencies flagged as unhealthy. 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 208 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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 0
- Stability: 0.97 → pass security
- 19 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.97 functional
- 16 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 13 Nov 26 0
- Stability: 0.97 → pass security
- 12 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 11 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 10 Nov 26 −1
- Stability: pass → 0.90 functional
- 7 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
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 npm/@mukundakatta/agentvet-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 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
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.
How do I install the io.github.MukundaKatta/agentvet MCP server?
io.github.MukundaKatta/agentvet runs locally as an npm package, launched with npx -y @mukundakatta/agentvet-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 · @mukundakatta/agentvet-mcp
claude mcp add mukundakatta-agentvet -- npx -y @mukundakatta/agentvet-mcp
What is the io.github.MukundaKatta/agentvet MCP server?
io.github.MukundaKatta/agentvet is an MCP server listed in the public MCP registry as io.github.MukundaKatta/agentvet. Validate tool-call args before execution. Returns LLM-friendly retry hints. This page covers its npm package (@mukundakatta/agentvet-mcp).
Is the io.github.MukundaKatta/agentvet MCP server safe to use?
io.github.MukundaKatta/agentvet scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 io.github.MukundaKatta/agentvet MCP server expose?
io.github.MukundaKatta/agentvet exposes 3 tools: validate_tool_args, lint_tool_definition, generate_retry_message. Their descriptions and schemas cost roughly 295 tokens of context every time the server is loaded.
Is the io.github.MukundaKatta/agentvet MCP server still maintained?
io.github.MukundaKatta/agentvet is still listed as active in the MCP registry. We last reached this channel on 21 November 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 io.github.MukundaKatta/agentvet MCP server under?
io.github.MukundaKatta/agentvet declares the MIT 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 io.github.MukundaKatta/agentvet MCP server?
VerifyMCP ran 16 checks on io.github.MukundaKatta/agentvet, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.