Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add JansenAnalytics/claudex --skill mcportergit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jansenanalytics/claudex/mcporter)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/mcporter"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/mcporter.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00041 | $0.00469 |
| Opus 5 | $0.00020 | $0.00234 |
| Sonnet 5 | $0.00008 | $0.00094 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
mcporter scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
95% identical to mcporter — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
mcporter
Use mcporter to work with MCP servers directly.
Quick start
mcporter listmcporter list <server> --schemamcporter 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 jsonfor machine-readable results.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 65 lines · 41 tokens per session scan A 7b2f20bb14bb
mcporter is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 469 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to mcporter, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
pixiv-cli
Operate Pixiv through the pixiv-cli binary — search illustrations, novels, and users; reverse-search images with SauceNAO or ascii2d; inspect Pixiv artwork or user IDs/URLs; view rankings and recommendations; manage bookmarks/follows; and download works. Load only when the user explicitly mentions Pixiv or pixiv-cli…
pixiv-cli-ci
Diagnose, verify, monitor, and safely operate pixiv-cli GitHub Actions runs and local CI gates, including PR Quality gate, workflow policy, platform smoke, native/browser evidence, release handoffs, and approved reruns. Use when checks fail or hang, a PR needs readiness verification, a workflow run needs root-cause…
pixiv-cli-review
Review pixiv-cli worktree, commit range, or GitHub pull request for architectural boundaries, public CLI/MCP/SDK contracts, security, documentation obligations, tests, and workflow policy. Use for code review, PR review, pre-release review, or review of agent/workflow changes.
pixiv-cli-release-notes
Audit pixiv-cli release sources, write and validate bilingual Markdown release notes, publish immutable tags, synchronize historical GitHub Release bodies, and hand off SkillHub/ClawHub verification. Use for release preparation, version selection, tag publication, release monitoring, or historical note synchronization.
pixiv-cli-docs
Maintain pixiv-cli README, locale contracts, maintainer documentation, contribution guidance, and documentation checks. Use when adding, changing, reviewing, or routing repository documentation; use pixiv-cli-release-notes for versioned bilingual changelog or release-prep work.
pixiv-cli-pr
Prepare, create, update, and monitor pixiv-cli pull requests using the repository template, verification checklist, review handoff, and authorization boundaries. Use when drafting a PR body, opening or editing a PR, requesting review, checking readiness, or handing a merged PR to release preparation.