An MCP server that lets you browse and purchase AI skills via Alipay pay-per-use payments, and provides guides for integrating Alipay payments into your own applications.
Discover AI Skills (discover_skills): Browse all 5 available AI skills on the marketplace, including names, descriptions, prices (¥0.10–¥0.50), and endpoints.
Get Skill Details & Unlock Content (get_skill_detail): Retrieve full details of a specific AI skill. Returns a free preview first; pay via Alipay and retry with a receipt to unlock the full content.
Skill | Price |
🧠 MBTI Analysis – Analyze personality dynamics and group interaction | ¥0.10 |
📡 Weekly Radar – Curated AI tool picks with pros/cons/comparison | ¥0.10 |
🎮 Game Audio Brief – Generate professional audio specs from a single sentence | ¥0.10 |
🔍 Deep Analysis (灼见) – 5-layer penetration analysis from surface to prediction | ¥0.50 |
✅ Fact Check (辩真) – Triple adversarial verification with source tracing | ¥0.50 |
Get Alipay Integration Guide (get_alipay_integration_guide): Step-by-step instructions for integrating Alipay payment products (Pay-Per-Use, Website Payment, or App Payment) with code examples in Node.js, Python, Java, PHP, or C#.
Get Alipay Merchant Onboarding Guide (get_alipay_onboarding_guide): A walkthrough of the merchant sign-up/onboarding process, covering environment setup, product selection, authorization, required documents, and application submission.
Additional resources: Use the alipay://products resource to view supported Alipay products, and prompts like integrate-alipay or browse-skills to quickly start common workflows.
Provides Alipay payment integration capabilities, including pay-per-use (HTTP 402), website payment, and APP payment. Enables AI agents to discover AI skills, get skill details with pricing, access step-by-step integration guides, and retrieve merchant onboarding workflows.
An MCP (Model Context Protocol) server with 5 AI Skills that supports pay-per-use via Alipay HTTP 402.
Pay only when you use. ¥0.10–0.50 per call. No subscription.
Skill | Price | Description |
🧠 MBTI Analysis | ¥0.10 | 2-20 person personality dynamics, group interaction matrix |
📡 Weekly Radar | ¥0.10 | Curated AI tool picks with pros/cons/comparison |
🎮 Game Audio Brief | ¥0.10 | One sentence → professional audio specification doc |
🔍 Deep Analysis (灼见) | ¥0.50 | 5-layer penetration: surface → structure → logic → essence → prediction |
✅ Fact Check (辩真) | ¥0.50 | Triple adversarial verification + source tracing |
discover_skills → Browse all 5 skills with pricing
get_skill_detail → See free preview + value proposition
Pay via Alipay (¥0.10–0.50) → Get receipt
Retry with receipt → Full content unlocked
No registration. No subscription. No pre-payment. Just scan & pay.
Related MCP server: btcpay-mcp
Tool | Description |
| List all available AI skills on the marketplace with pricing |
| Get full SKILL.md content for a specific skill (handles HTTP 402 payment flow) |
| Step-by-step integration guide for a chosen product + language |
| Merchant onboarding workflow and required documents |
Prompt | Description |
| Start an Alipay payment integration project |
| Browse available AI skills on the marketplace |
URI | Description |
| List of supported Alipay payment products |
npx -y xiangguangyu-mcp-skills@latestgit clone https://github.com/Chromatic0618/alipay-mcp-server.git
cd alipay-mcp-server
npm install
npm run buildAdd to your claude_desktop_config.json:
{
"mcpServers": {
"alipay": {
"command": "npx",
"args": ["-y", "xiangguangyu-mcp-skills@latest"],
"env": {
"SKILL_API_BASE": "http://124.222.26.218:3000"
}
}
}
}Add to your MCP settings (.cursor/mcp.json):
{
"mcpServers": {
"alipay": {
"command": "npx",
"args": ["-y", "xiangguangyu-mcp-skills@latest"]
}
}
}claude mcp add alipay -- npx -y xiangguangyu-mcp-skills@latestVariable | Default | Description |
|
| Skill marketplace API base URL |
→ discover_skills
← 5 skills: MBTI Analysis (¥0.10), Weekly Radar (¥0.10), Game Audio (¥0.10),
Deep Analysis (¥0.50), Fact Check (¥0.50)→ get_skill_detail { skill: "mbti" }
← ## Skill: mbti
> MBTI 十六型人格关系推演
### 🎯 Free Preview
📋 示例输出（INFJ × ENFP）: 共鸣度 82%, 核心共鸣...
⚠️ Payment Required — Price: ¥0.10
Pay via Alipay → Retry with receipt → Full content→ get_alipay_integration_guide { product: "pay_per_use", language: "nodejs" }
← Step-by-step guide with SDK install, sandbox setup, and code paths.💬 Discussions — Feedback, ideas, questions
🐛 Issues — Bug reports
Chromatic0618 / 相光域
MIT
List all available AI skills on the marketplace. Returns name, description, price, and endpoint for each skill. Useful for browsing what payment-related AI capabilities are available.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, but the description clearly indicates a read-only listing operation with no side effects. It fully discloses behavior for a simple list tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences, no wasted words. Front-loaded with the main action and followed by return details and usage context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters, no output schema, and a simple list operation, the description adequately covers purpose, return fields, and usage context. It is complete for a tool of this complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has zero parameters (100% coverage). The description adds value by explaining the return fields, which is more context than the empty schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states 'List all available AI skills on the marketplace' with specific return fields (name, description, price, endpoint). It clearly distinguishes from sibling tools which are specific guides and details.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description says it's 'useful for browsing what payment-related AI capabilities are available,' providing context for use. It doesn't explicitly exclude alternatives but implies this is for overview before drilling into details.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get a step-by-step guide for integrating Alipay payments (Pay-Per-Use, Website Payment, or APP Payment). Returns product recommendation, sandbox setup instructions, and code example paths for Node.js/Python/Java/PHP/C#.
| Name | Required | Description | Default |
|---|---|---|---|
| product | Yes | Which Alipay product to integrate. Use 'auto' for product recommendation based on your use case. | |
| language | No | Programming language for code examples. Defaults to nodejs. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose behavioral traits. It describes outputs well but does not mention read-only nature, access requirements, or potential side effects. For a guide tool, this is acceptable but not fully transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, front-loaded with key information. No wasted words, efficient and clear.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Description covers the main output (recommendation, sandbox setup, code paths). Without output schema, this is fairly complete for a low-complexity tool with only 2 parameters.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with enum descriptions and defaults. Description adds value by explaining the 'auto' product option and listing programming languages. It clarifies the guide content beyond schema definitions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it returns a step-by-step integration guide for Alipay payments, listing specific product types and outputs. Distinguishes from sibling tools like get_alipay_onboarding_guide and get_skill_detail.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Clearly describes what the tool returns (guide content, code examples). While it doesn't explicitly state when not to use or alternatives, the context is sufficient for using the tool correctly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get merchant onboarding (签约/入驻) guide for Alipay. Covers environment check, product selection, login authorization, document collection, and application submission.
| Name | Required | Description | Default |
|---|---|---|---|
| product | Yes | Which Alipay product to sign up for. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden but only lists stages covered. It does not disclose side effects, authentication needs, or the nature of the response (e.g., that it is a read-only guide). Adequate but not thorough.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, using a single sentence with a comma-separated list of covered topics. No unnecessary words, though it could be slightly more structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple guide-retrieval tool with one parameter and no output schema, the description sufficiently outlines the purpose and contents. Missing return format is acceptable given the tool's nature.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with clear enum descriptions. The description adds no additional meaning beyond what the schema already provides, so baseline score is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves a merchant onboarding guide for Alipay, using a specific verb ('Get') and resource ('onboarding guide'). It distinguishes from siblings like 'discover_skills' and 'get_alipay_integration_guide' by focusing on the onboarding process.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or context for usage relative to sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get full details of a specific AI skill by its name or path. Returns the complete SKILL.md content including pricing, integration instructions, and API documentation.
| Name | Required | Description | Default |
|---|---|---|---|
| skill | Yes | Skill name (e.g. 'mbti', 'alipay-aipay') or full API path (e.g. '/api/skill/mbti') |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Clearly states return content (complete SKILL.md with pricing, integration, API docs). Does not mention error cases or permissions, but for a read-only tool it's sufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no wasted words. Purpose and return value clearly front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple retrieval tool with one well-documented parameter and no output schema, the description fully explains what the tool does and returns. No gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema already covers parameter with examples (skill name or path). Description reiterates 'by its name or path' without adding new meaning. Schema coverage is 100%, so baseline 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb 'Get' plus resource 'full details of a specific AI skill' clearly states purpose. Distinguishes from siblings: discover_skills (listing), get_alipay_* (specific integration).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies use when needing skill details, but no explicit guidance on when to use vs siblings like discover_skills or when not to use. Lacks alternatives or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0discover_skillsget_alipay_integration_guideget_alipay_onboarding_guideget_skill_detailEach tool has a clearly distinct purpose: discovering skills, getting skill details, integration guide, and onboarding guide. No overlap in functionality.
All tool names use a consistent verb_noun pattern in snake_case (discover_skills, get_alipay_integration_guide, etc.). The verbs are uniform ('discover' and 'get').
4 tools is appropriate for a focused Alipay integration assistant. It covers the key areas without being too few or too many.
The tools cover skill discovery, detail retrieval, integration guide, and onboarding guide. Minor gap: lacks a tool for actual sandbox or payment testing, but the guides provide instructions.
Discover and call 10,000+ production APIs from one MCP server. Pay-per-call billing for AI agents.
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
First AI Agent e-commerce marketplace with 74+ AI products, MCP protocol, and Alipay payments
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Chromatic0618/alipay-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
