Vengtoo MCP Server

@vengtoo/mcp-server npm v0.1.8

Published by @vengtoo — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Vengtoo MCP server — manage your authorization model and check access through any MCP-compatible AI tool

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 98/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 2 = 98. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 39

Each tool and what it can reach — statically extracted from the published source.

  • activate_policyno sensitive capability
  • approve_toolno sensitive capability
  • assign_policyno sensitive capability
  • assign_role_to_subjectno sensitive capability
  • block_toolno sensitive capability
  • create_namespaceno sensitive capability
  • create_policyno sensitive capability
  • create_resourceno sensitive capability
  • create_resource_typeno sensitive capability
  • create_roleno sensitive capability
Show 29 more tools ↓
  • create_subjectno sensitive capability
  • deactivate_policyno sensitive capability
  • define_subject_attributeno sensitive capability
  • delete_namespaceno sensitive capability
  • delete_policyno sensitive capability
  • delete_resourceno sensitive capability
  • delete_resource_typeno sensitive capability
  • delete_roleno sensitive capability
  • delete_subjectno sensitive capability
  • evaluate_accessno sensitive capability
  • get_namespaceno sensitive capability
  • get_policyno sensitive capability
  • get_resourceno sensitive capability
  • get_resource_typeno sensitive capability
  • get_roleno sensitive capability
  • get_subjectno sensitive capability
  • list_namespacesno sensitive capability
  • list_pending_toolsno sensitive capability
  • list_policiesno sensitive capability
  • list_policy_assignmentsno sensitive capability
  • list_resource_typesno sensitive capability
  • list_resourcesno sensitive capability
  • list_rolesno sensitive capability
  • list_subjectsno sensitive capability
  • unassign_policyno sensitive capability
  • unassign_role_from_subjectno sensitive capability
  • update_policyno sensitive capability
  • update_resourceno sensitive capability
  • update_subjectno sensitive capability

What this scan could not see

Versions 3

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.8 latest A 98/100 0 1.13.0 2026-09-09
v0.1.7 A 98/100 0 1.12.1 2026-08-14
v0.1.6 A 98/100 0 1.12.1 2026-07-28

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/vengtoo-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/vengtoo-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/vengtoo-mcp-server"><img src="https://mcptrustchecker.com/registry/vengtoo-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/vengtoo-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @vengtoo/mcp-server --online

Use the free API → How scoring works

More in Developer Tools