JPYC Commerce MCP
by ackey-web
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHAIN_ID | Yes | Chain ID (80002 for Amoy, 137 for Mainnet) | |
| AMOY_RPC_URL | Yes | Amoy Testnet RPC URL | |
| DATABASE_URL | Yes | Neon PostgreSQL connection string | |
| POLYGON_RPC_URL | Yes | Polygon Mainnet RPC URL | |
| ANTHROPIC_API_KEY | Yes | Claude API key for task evaluation | |
| JPYC_CONTRACT_ADDRESS | Yes | JPYC v2 ERC-20 contract address | |
| SBT_CONTRACT_ADDRESS_AMOY | Yes | TrustSBT contract address on Amoy |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ackey-web/JPYC-commerce-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server