@oobe-protocol-labs/sap-mcp-server 0.1.0

package/skills/sap-social-gaming/SKILL.md

@@ -0,0 +1,30 @@
+# SAP Social Gaming
+
+Use this skill for Solana Actions/Blinks, Gibwork bounties, and Send Arcade
+gaming flows.
+
+## Tools
+
+- `blinks_getAction`
+- `blinks_executeAction`
+- `blinks_confirmAction`
+- `blinks_buildActionUrl`
+- `blinks_resolveBlinkUrl`
+- `blinks_validateActionsJson`
+- `gibwork_createBounty`
+- `gibwork_listBounties`
+- `gibwork_submitWork`
+- `send-arcade_listGames`
+- `send-arcade_playGame`
+
+## Flow
+
+1. Validate action URLs or `actions.json` before execution.
+2. Read bounties/games before creating or paying.
+3. Explain entry fees, bounty amounts, or transaction effects before write
+   tools.
+
+## Safety
+
+Bounties, games, and actions can spend funds or trigger arbitrary protocol
+actions. Preview and require explicit user intent.

package/skills/sap-solana-token/SKILL.md

@@ -0,0 +1,32 @@
+# SAP Solana Token
+
+Use this skill for SOL balances, SPL token balances, token accounts, transfers,
+minting, burning, account close/freeze/thaw, and token security checks.
+
+## Tools
+
+- `sol_get_balance`
+- `spl-token_getBalance`
+- `spl-token_getTokenAccounts`
+- `spl-token_transfer`
+- `spl-token_transferSol`
+- `spl-token_deployToken`
+- `spl-token_mintTo`
+- `spl-token_burn`
+- `spl-token_closeAccount`
+- `spl-token_freezeAccount`
+- `spl-token_thawAccount`
+- `spl-token_rugCheck`
+
+## Flow
+
+1. Read profile/network with `sap_profile_current`.
+2. Read balances before transfers or mint/burn operations.
+3. Use `spl-token_rugCheck` before interacting with unknown token mints.
+4. Preview/sign transaction-producing outputs through SAP transaction tools
+   when a serialized transaction is involved.
+
+## Safety
+
+Transfers, minting, burning, freezing, thawing, and account closing are
+high-risk. Do not execute without explicit user intent.

package/skills/sap-staking/SKILL.md

@@ -0,0 +1,24 @@
+# SAP Staking
+
+Use this skill for SAP stake initialization, deposits, unstake requests,
+complete unstake flows, and stake reads.
+
+## Tools
+
+- `sap_init_stake`
+- `sap_deposit_stake`
+- `sap_request_unstake`
+- `sap_complete_unstake`
+- `sap_fetch_stake`
+
+## Flow
+
+1. Read `sap_fetch_stake` before write operations.
+2. Use `sap_init_stake` only when no stake account exists.
+3. Explain lockup, amount, and unstake timing before deposits or unstake
+   requests.
+
+## Safety
+
+Stake operations affect capital and trust guarantees. Respect local policy and
+ask for explicit approval when thresholds require it.

package/skills/sap-tool-registry/SKILL.md

@@ -0,0 +1,29 @@
+# SAP Tool Registry
+
+Use this skill for publishing, fetching, updating, deactivating, reactivating,
+and reporting SAP tool descriptors.
+
+## Tools
+
+- `sap_publish_tool_by_name`
+- `sap_update_tool`
+- `sap_deactivate_tool`
+- `sap_reactivate_tool`
+- `sap_fetch_tool`
+- `sap_report_tool_invocations`
+- `sap_find_tools_by_category`
+- `sap_get_tool_category_summary`
+- `sap_fetch_tool_category_index`
+
+## Flow
+
+1. Inspect `sap_profile_current`.
+2. For discovery, use `sap_find_tools_by_category` or `sap_fetch_tool`.
+3. For publishing or updates, explain protocol ID, category, params, and schema
+   impact before calling the write tool.
+4. Report invocations only after real usage has occurred.
+
+## Safety
+
+Tool registry writes affect on-chain discoverability. Do not publish placeholder
+schemas, fake HTTP methods, or unverifiable descriptions.