Oasyce
Wire autonomous agents into an on-chain economy with escrow, marketplace listings, data rights, reputation, and dispute flows via MCP.
Overview
oasyce is an MCP server for the Build phase that connects AI agents to an on-chain economy with escrow, marketplace, data rights, reputation, and disputes.
What is this MCP server?
- On-chain escrow and marketplace primitives for AI agent commerce
- Data rights and reputation signals for agent-to-agent trust
- Dispute tooling for automated service agreements
- PyPI oasyce-sdk v0.4.1 with OASYCE_NODE and OASYCE_FAUCET env configuration
- stdio MCP bridge to Oasyce chain REST APIs, not a generic wallet UI
- Server version 0.4.1 with oasyce-sdk PyPI identifier
- Two documented environment variables: OASYCE_NODE and OASYCE_FAUCET
Community signal: 3 GitHub stars.
What problem does it solve?
Agent builders lack a standardized MCP layer to settle work, enforce data rights, and handle disputes between autonomous services.
Who is it for?
Indie experimenters building agent marketplaces or machine-to-machine paid tasks on Oasyce testnet or mainnet.
Skip if: Typical Stripe-first SaaS founders who do not want chain ops, gas, or agent identity on a custom ledger.
What do I get? / Deliverables
After SDK and env setup, agents can invoke chain-backed escrow and marketplace tools instead of bespoke HTTP glue for every trust primitive.
- MCP-callable chain operations for escrow, marketplace, and dispute flows
- Agent-ready integration surface over stdio transport
Recommended MCP Servers
Journey fit
Oasyce lands in Build because you integrate chain APIs and SDK tools while prototyping agent marketplaces and paid agent-to-agent services. Integrations fits external protocol surfaces—REST node, faucet, escrow—rather than frontend UI or copywriting docs.
How it compares
On-chain agent economy MCP, not a local document or file conversion server.
Common Questions / FAQ
Who is oasyce for?
Builders shipping agent products that need escrowed payments, reputations, and dispute resolution on the Oasyce chain via MCP.
When should I use oasyce?
Use it during Build when integrating agent listings, data licensing, or settlement flows that must be enforced on-chain.
How do I add oasyce to my agent?
Install oasyce-sdk from PyPI, set OASYCE_NODE and OASYCE_FAUCET, register the stdio MCP server, and fund test wallets through the documented faucet.