io.github.MukundaKatta/agentcast
NPM · @MUKUNDAKATTA/AGENTCAST-MCP · SCANNED AUG 3
Structured-output enforcer: extract and validate JSON from messy LLM text.
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 310 tokens (~103/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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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/agentcast-mcp
claude mcp add mukundakatta-agentcast -- npx -y @mukundakatta/agentcast-mcp
codex mcp add mukundakatta-agentcast -- npx -y @mukundakatta/agentcast-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mukundakatta-agentcast": {
"type": "local",
"command": [
"npx",
"-y",
"@mukundakatta/agentcast-mcp"
],
"enabled": true
}
}
} openclaw mcp add mukundakatta-agentcast --command npx --arg -y --arg @mukundakatta/agentcast-mcp
mcp_servers:
mukundakatta-agentcast:
command: "npx"
args: ["-y", "@mukundakatta/agentcast-mcp"] {
"mcpServers": {
"mukundakatta-agentcast": {
"command": "npx",
"args": [
"-y",
"@mukundakatta/agentcast-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 +47
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- License: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
- 31 Jul 26 −7
- 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 +4
- Malware scan: pass → unverified ▼ security
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
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.
build_retry_prompt ~100
Given an attempt history, produce the retry feedback message agentcast would append to the conversation when the model returned the wrong shape. Codifies the "validation error as feedback" pattern for non-Node MCP clients.
| Name | Type | Req | Description |
|---|---|---|---|
| attempts | array | yes | List of prior attempts. Each item should have the assistant text plus either a parsed value or an error string. |
| expected_shape | object | — | Optional agentcast shape spec to include in the feedback for extra grounding. |
No output schema declared.
No examples provided.
extract_json ~71
Pull a JSON value out of messy LLM output. Tries the whole text, then a fenced ```json``` block, then the largest balanced {...}/[...] substring. Returns the parsed value plus which strategy succeeded.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Free-form text from an LLM that may contain JSON anywhere inside. |
No output schema declared.
No examples provided.
validate_response ~139
Validate a parsed JSON value against an agentcast shape spec. Spec maps field name to type: 'string', 'number', 'boolean', 'array', 'object'. Suffix with '?' for optional. Returns valid=true on success, or valid=false with a human-readable error string suitable for retry feedback.
| Name | Type | Req | Description |
|---|---|---|---|
| shape | object | yes | Shape spec: { fieldName: 'string' | 'number' | 'boolean' | 'array' | 'object', ... }. Append '?' for optional fields, e.g. { name: 'string', age: 'number?' }. |
| value | — | yes | The parsed JSON value to validate (any shape). |
No output schema declared.
No examples provided.