io.github.kartegagithub/laviya-agent-skills

MCPcommunity
v0.1.23io.github.kartegagithubUnknownUpdated 3mo agonpmGitHub

Laviya AI Orchestration MCP runtime for IDE and agent integrations.

Laviya AI Orchestration Developer Runtime is implemented as a single machine-level Node.js + TypeScript MCP server package (). Each repository provides only a lightweight local config ( or ) plus optional prompt/rule overrides. This is the recommended production model: Global shared runtime: installed once per developer machine. Project-local config: small, explicit, and secret-free. MCP-first…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3mo agoLast update
Package
Authorio.github.kartegagithub
LicenseUnknown
Version0.1.23
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface10 tools · 2 privileged
Security scan✓ Cleanv0.1.23 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · 2 privileged
Statically extracted from the published packagev0.1.23 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

laviya_add_task_commentNo description published

This tool published no description. Forge does not invent one.

laviya_cancel_local_workNo description published

This tool published no description. Forge does not invent one.

laviya_complete_executionprivilegedNo description published

This tool published no description. Forge does not invent one.

laviya_diagnosticsNo description published

This tool published no description. Forge does not invent one.

laviya_feed_taskNo description published

This tool published no description. Forge does not invent one.

laviya_get_local_work_statusNo description published

This tool published no description. Forge does not invent one.

laviya_get_my_workNo description published

This tool published no description. Forge does not invent one.

laviya_helpNo description published

This tool published no description. Forge does not invent one.

laviya_report_token_usageNo description published

This tool published no description. Forge does not invent one.

laviya_start_executionprivilegedNo description published

This tool published no description. Forge does not invent one.

0 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Laviya AI Orchestration Developer Runtime is implemented as a single machine-level Node.js + TypeScript MCP server package (). Each repository provides only a lightweight local config ( or ) plus optional prompt/rule overrides. This is the recommended production model: Global shared runtime: installed once per developer machine. Project-local config: small, explicit, and secret-free. MCP-first integration: IDEs/agents call MCP tools, not raw API. Runtime-enforced mechanics: retries, timeout,…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.