Skip to main content
Glama

pulsefeed-x402

by io.github.Nikolife2016

Audit an MCP server before installing

mcp_check_server
Read-onlyIdempotent

Before installing an MCP server or npm package, audit it: does it run an INSTALL SCRIPT (arbitrary code execution at npm i), is it abandoned, does it ship a repository and license, weekly downloads, provenance — with a safe/caution/avoid verdict. ~11% of audited MCP servers run install scripts. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageYesnpm package name of the MCP server, e.g. @scope/name

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare safety hints (read-only, open-world, idempotent, non-destructive). The description adds valuable behavioral context: it checks for install scripts, abandonment, repository/license, downloads, provenance, and provides a verdict. No contradictions.

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

Conciseness5/5

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

The description is two sentences long, front-loaded with the core purpose and details, and every sentence adds value (what it checks, frequency of issue, cost). No waste.

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

Completeness4/5

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

Given the single parameter and simple audit functionality, the description covers the main checks and verdict categories. It could hint at output format but overall is sufficiently complete.

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

Parameters3/5

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

With only one parameter and 100% schema coverage, the schema already documents 'package' with example format. The description does not add further semantics beyond the schema, meeting the baseline.

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?

The description explicitly states the tool's purpose: auditing an MCP server or npm package before installation. It uses specific verbs ('audit') and resources (npm package) and distinguishes from siblings by focusing on pre-install safety checks.

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

Usage Guidelines4/5

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

The description clearly indicates when to use the tool ('Before installing...'), but does not explicitly mention when not to use it or alternatives among siblings. It provides a strong usage trigger.

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

All pulsefeed-x402 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools target distinct data or actions, but x402_working_services and x402_leaderboard both list services ranked by trust score, and x402_changes vs x402_incidents both cover ecosystem changes. Descriptions help differentiate them, so only minor confusion is possible.

Naming Consistency3/5

Naming is mixed: some tools use a verb_noun pattern (check_x402_endpoint, mcp_check_server), while most use noun phrases (x402_incidents, pulsefeed_products). The consistent x402_/mcp_/pulsefeed_ prefixes add some structure, but the overall pattern is inconsistent.

Tool Count5/5

Ten tools is well within the ideal range for a domain-specific data/audit server. Each tool covers a distinct facet (endpoint safety, ecosystem stats, MCP audits, product listings), and none feel redundant or out of place.

Completeness4/5

The set covers endpoint checking, incident feeds, leaderboards, stats, change history, MCP security, and product info. A minor gap is the lack of a per-endpoint full historical record beyond the check verdict, but the available tools serve the core use cases well.

Resources