@mastyf_ai/server

MCP@mastyf-ai
v4.1.12io.github.mastyf-aiUnknownUpdated 3mo agonpmGitHub

Runtime proxy for MCP security, cost governance & audit

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.

@mastyf-ai
Identity-verified publisher GitHub@mastyf-ai
Verified Jul 8, 2026
3mo agoLast update
Package
Authorio.github.mastyf-ai
LicenseUnknown
Version4.1.12
Sourcenpm+mcp-registry
Trust Status
A
80/100Trusted
✓Listed in Forge index+10/10
✓Publisher identity verified+20/20
—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
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
Publisher@mastyf-ai
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface—
Security scan✓ Cleanv4.1.12 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 5, 2026

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

Tools

Source not readable1mo ago

The published package tarball could not be read at scan time (tarball exceeds 15MB cap), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.

About

Runtime proxy for MCP security, cost governance & audit

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-28 — observed resolution, not a publisher declaration.

60 packages resolved · 30 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

189 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+177 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.