Skip to main content
Glama

Presend MCP Server

by io.github.presendapp
OverviewDiscussionsAdmin

Package supply-chain check

supply_chain_check
Read-onlyIdempotent

Call this before installing or adding a package (npm install, pip install, a new entry in a manifest), especially one whose name you recalled or that a model suggested. One-call risk check: combines vulnerability_check (OSV.dev), typosquat_check, maintainer_change_check (npm only) and repo_health_check (when the GitHub repo can be resolved) into one overall verdict. A package that does not exist on npm or PyPI gets overall_risk 'package_not_found': the name may be invented and should not be installed. A package first published less than 30 days ago gets the 'new_package' flag and overall_risk 'review_recommended': new packages are where invented and look-alike names get registered, so the name is worth confirming against the project's own documentation before installing (on PyPI the age is that of the oldest release still published; being new does not make a package malicious). Use the individual tools to investigate one signal. Vulnerabilities are checked for the given version, or the latest published one (version_checked, version_source). If a check could not run (rate limit, upstream error), it is listed in unavailable_checks and overall_risk is 'incomplete', never 'no_signals_found'. Also flags a version marked deprecated on npm or yanked on PyPI.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageYesPackage name to check.
versionNoExact version to check for known vulnerabilities. Optional: defaults to the latest published version (npm and PyPI).
ecosystemYesPackage ecosystem, e.g. npm. maintainer-change-check only runs for npm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / version
      Added value: +{
+  "description": "Exact version to check for known vulnerabilities. Optional: defaults to the latest published version (npm and PyPI).",
+  "type": "string"
+}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only/idempotent/non-destructive/open-world, and the description adds substantial context beyond that: the package_not_found verdict, the 30-day new_package rule and review_recommended, the rule that failed checks become 'incomplete' rather than 'no_signals_found', and deprecated/yanked flagging. This is exactly the behavioral disclosure the annotations can't carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The actionable instruction is front-loaded and every clause adds a distinct behavior (not_found verdict, new-package threshold, unavailable_checks semantics). It is long and dense, but almost no sentence is filler; slightly heavy for 3 parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Though there is no output schema, the description explains the return semantics (overall_risk values, flags, version_checked, unavailable_checks) in enough detail that an agent can interpret the result. Nothing needed to call or act on the tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage the baseline is 3, but the description adds real semantic value: vulnerabilities are checked against the given version or the latest published one (version_checked/version_source), and it restates that maintainer_change_check is npm-only. Minor duplication of the schema rather than new meaning for 'package'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb+resource ("One-call risk check") and enumerates exactly what it aggregates — vulnerability_check, typosquat_check, maintainer_change_check, repo_health_check — into a single verdict. It also distinguishes itself from the siblings by saying to use the individual tools to investigate one signal.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ("Call this before installing or adding a package ... especially one whose name you recalled or that a model suggested") and an explicit alternative (the individual per-signal tools). The conditions that select this tool are unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Presend MCP Server toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources