Mcporter Cli

Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type gene...

Security Scan

The skill is internally consistent: it exposes an instruction-only wrapper around an external mcporter CLI, requires the mcporter binary (installed from npm), and the requested artifacts align with the stated purpose.

Purpose & Capability

Name/description match the behavior in SKILL.md: the skill simply instructs the agent to run the mcporter CLI to list, auth, call, and configure MCP servers. The declared requirement (mcporter binary) and the node install spec (npm package 'mcporter') are appropriate for that purpose.

Instruction Scope

SKILL.md stays within the CLI's domain (list/call/auth/config/daemon/codegen). It references a default config path (./config/mcporter.json) which is relevant to the CLI but means credentials or tokens may be written to disk; be aware the agent running this skill will call out to network endpoints specified via mcporter (including ad-hoc URLs) as part of normal operation.

Install Mechanism

The install uses the npm package 'mcporter' to create the mcporter binary. This is a reasonable install method for a Node-based CLI but carries the usual npm risks: verify the package name, owner, and package contents before installing. The declared homepage uses http (not https), which is less reassuring; verify the project's authenticity on npm/GitHub.

Credentials

The skill declares no required environment variables or credentials, which is proportional. However, mcporter's auth commands can perform OAuth flows and will likely store tokens in the config path (./config/mcporter.json by default). That stored data is outside the skill bundle and should be treated as local secrets.

Persistence & Privilege

always is false and the skill is not requesting elevated or persistent platform privileges. It does not attempt to modify other skills or system-wide settings according to the provided files.

Assessment

This skill is an instruction wrapper for an external mcporter CLI. Before installing or using it: 1) Verify the npm package 'mcporter' and its publisher (check the package page, README, and source repository) and prefer installing from a trustworthy registry; 2) Be aware mcporter may perform network calls to servers you specify and will store auth tokens/config at ./config/mcporter.json by default — treat that file as sensitive; 3) Confirm the homepage/owner information (there is a mismatch between registry metadata and the included _meta.json ownerId) to ensure you're installing the intended project; 4) For initial use, run the CLI in a controlled environment (sandbox or VM) and inspect the config file created by mcporter to see what credentials are stored.

mcporter

Use mcporter to work with MCP servers directly.

Quick start

• mcporter list
• mcporter list <server> --schema
• mcporter call <server.tool> key=value

Call tools

• Selector: mcporter call linear.list_issues team=ENG limit:5
• Function syntax: mcporter call "linear.create_issue(title: \"Bug\")"
• Full URL: mcporter call https://api.example.com/mcp.fetch url:https://example.com
• Stdio: mcporter call --stdio "bun run ./server.ts" scrape url=https://example.com
• JSON payload: mcporter call <server.tool> --args '{"limit":5}'

Auth + config

• OAuth: mcporter auth <server | url> [--reset]
• Config: mcporter config list|get|add|remove|import|login|logout

Daemon

• mcporter daemon start|status|stop|restart

Codegen

• CLI: mcporter generate-cli --server <name> or --command <url>
• Inspect: mcporter inspect-cli <path> [--json]
• TS: mcporter emit-ts <server> --mode client|types

Notes

• Config default: ./config/mcporter.json (override with --config).
• Prefer --output json for machine-readable results.