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.
git clone --depth 1 https://github.com/GarphenGate/moltline-mcpWrote 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/mcp/garphengate/moltline-mcp/dropship)<a href="https://agentmods.dev/mcp/garphengate/moltline-mcp/dropship"><img src="https://agentmods.dev/badge/mcp/garphengate/moltline-mcp/dropship/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/garphengate/moltline-mcp/dropship"><img src="https://agentmods.dev/badge/mcp/garphengate/moltline-mcp/dropship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dropship 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 today.
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.
What it actually says
{ "dropship": { "url": "https://mcp.moltlinestudio.com/dropship", "type": "streamable-http" } }
What else configures
This page is one entry in a file that holds 22. Installing the file brings all of them; each is measured and scanned on its own page.
- MCP server business A not measured
- MCP server catalog A not measured
- MCP server codereview A not measured
- MCP server creator A not measured
- MCP server data A not measured
- MCP server educator A not measured
- MCP server govern A not measured
- MCP server humanizer A not measured
- MCP server merchant A not measured
- MCP server optimize A not measured
- MCP server outbound A not measured
- MCP server personal A not measured
- MCP server recall A not measured
- MCP server regclock A not measured
- MCP server research A not measured
- MCP server shipping A not measured
- MCP server shopify A not measured
- MCP server skillmd-lint A not measured
- MCP server taxlots A not measured
- MCP server timeops A not measured
- MCP server vision A not measured
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.
- today First seen · 6 lines scan A fe8d0b55f05c
dropship is an MCP server published in the GitHub repository GarphenGate/moltline-mcp (0 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-14.
Other mcp servers, from other repositories
chargebee
Chargebee MCP Pack — wraps the Chargebee API v2. Remote server at gateway.pipeworx.io.
paypal
PayPal MCP Pack — read-only access to PayPal transactions, orders, invoices, and disputes. Remote server at gateway.pipeworx.io.
stripe-mcp
A production-grade Model Context Protocol server for the Stripe API. Runs locally from the stripe-mcp npm package.
robokassa-mcp
Comprehensive Python client and MCP server for Robokassa payment gateway. Runs locally from the robokassa-mcp Python package. Needs 4 environment variables to run.
unified-pay-cli
Unified Payment Gateway CLI & MCP Bridge for Stripe, Razorpay and more. Runs locally from the unified-pay-cli npm package.
lunchmoney-mcp
MCP server for managing LunchMoney personal finances: transactions, budgets, categories, and more. Runs locally from the @akutishevsky/lunchmoney-mcp npm package. Needs 2 environment variables to run.