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/Shangri-la-0428/oasyce-sdkWrote 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/shangri-la-0428/oasyce-sdk/oasyce)<a href="https://agentmods.dev/mcp/shangri-la-0428/oasyce-sdk/oasyce"><img src="https://agentmods.dev/badge/mcp/shangri-la-0428/oasyce-sdk/oasyce/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/shangri-la-0428/oasyce-sdk/oasyce"><img src="https://agentmods.dev/badge/mcp/shangri-la-0428/oasyce-sdk/oasyce.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
oasyce 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 11d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 11d ago First seen · 12 lines scan A 19276b5f14dd
oasyce is an MCP server published in the GitHub repository Shangri-la-0428/oasyce-sdk (3 stars, last pushed 4mo ago), with no licence file. 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-08-31.
Other mcp servers, from other repositories
agent-trust
Trustless XRPL escrow oracle for AI agents. Create jobs, verify work, release XRP/RLUSD payments. Runs locally from the @eamwhite1/agenttrust-sdk npm package.
mcp
Paid work for agents: claim verifier-checked jobs, submit, earn USDC. Some need no bond or funding. Remote server at api.averray.com.
agent-insurance-mcp-server
MCP server for agent transaction insurance and escrow — protect AI agent-to-agent payments with smart escrow, dispute resolution, and risk scoring. Runs locally from the agent-insurance-mcp-server Python package.
x402-bridge
Pay any x402 endpoint on the open web: auto-paying bridge with Bazaar discovery and spend caps. Runs locally from the @three-ws/mcp-bridge npm package. Needs 13 environment variables to run.
three-token-mcp
Price, hold, and burn $THREE on Solana — the first MCP server whose actions burn a token. Runs locally from the @three-ws/three-token-mcp npm package. Needs 5 environment variables to run.
x402-mcp
Self-custodial x402 wallet for AI agents: pay any service in USDC or $THREE from your own key. Runs locally from the @three-ws/x402-mcp npm package. Needs 5 environment variables to run.