MPP Router — Service Discovery
v1.0.2Discover and search 489 paid API services on MPP Router — pay with Stellar USDC via x402 or mppx.
⭐ 0· 73·0 current·0 all-time
byShawn Muggle@shawnmuggle
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description match the runtime instructions: the SKILL.md only instructs searching a public catalog and reading service docs on apiserver.mpprouter.dev. There are no unexplained credentials, binaries, or config access required for discovery.
Instruction Scope
Instructions direct the agent to fetch the router endpoints and service docs (llms_txt) and to forward call parameters to a separate payment skill for 402 flows. This stays within discovery/call flow, but the agent will fetch arbitrary upstream docs URLs (third-party llms_txt) which could contain endpoints or instructions the agent will read — a legitimate part of the workflow but something to be aware of.
Install Mechanism
There is no install spec and no code files; this is instruction-only so nothing is written to disk. Lowest-risk install posture.
Credentials
The skill declares no required environment variables, credentials, or config paths. Payment actions are delegated to a separate 'stellar-agent-wallet-skill' which would separately request wallet credentials; this skill itself does not demand secrets.
Persistence & Privilege
always is false and the skill does not request persistent system modifications. It is user-invocable and can be invoked autonomously by the agent (default), which is normal for skills — no extra privileges requested here.
Assessment
This skill is a discovery/integration guide for a public router and appears internally consistent. Before installing or using it: (1) verify the mpprouter.dev homepage and that you trust the operator; (2) do not provide wallet private keys or secrets to this skill — payment is handled by a separate wallet skill, so only install that companion from a trusted source; (3) be aware the agent will fetch third-party docs (llms_txt URLs) and may follow instructions contained there — only allow network calls if you trust those upstream endpoints; (4) if you plan to actually pay/call services, audit the companion wallet skill and double-check which headers/credentials are sent; (5) if you need higher assurance, request the skill author/source code or an official distribution before enabling payment flows.Like a lobster shell, security has layers — review code before you run it.
latestvk9772ttn0a2a8ts8maa44gjs5s84xddq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🔍 Clawdis