MianshiyaServer

Created By
springaialibabaa year ago
Overview

what is MianshiyaServer?

MianshiyaServer is a repository containing various examples to demonstrate the usage of Spring AI Alibaba, ranging from basic to advanced applications and best practices in AI projects.

how to use MianshiyaServer?

To use MianshiyaServer, explore the examples provided in the repository, and refer to the README.md files for detailed instructions on each sub-project.

key features of MianshiyaServer?

  • Comprehensive examples for Spring AI Alibaba usage
  • Modular project structure for easy navigation
  • Integration with various AI models and tools

use cases of MianshiyaServer?

  1. Learning how to implement AI solutions using Spring AI Alibaba.
  2. Contributing to the project by adding new examples or best practices.
  3. Exploring different AI model integrations and their applications.

FAQ from MianshiyaServer?

  • How can I contribute to MianshiyaServer?

Contributions are welcome in any form, including usage examples, API usage, and best practices.

  • Is there documentation available?

Yes! Each example has its own README.md for detailed instructions, and a roadmap is available for future developments.

  • What AI models are integrated?

The project includes models like DashScope, OpenAI, and others for various functionalities.

Server Config

{
  "mcpServers": {
    "mianshiyaServer": {
      "command": "java"
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
springaialibaba
Star
-
Language
-
License
-

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

13 hours ago