mcp-server

Created By
MCPStudioa year ago
The main crate that composes the server from the previous components.
Overview

what is mcp-server?

The mcp-server is a main crate that composes the server from previous components, serving as a foundational element for building server applications.

how to use mcp-server?

To use mcp-server, integrate it into your project by including it as a dependency in your Rust project and follow the documentation for setup and configuration.

key features of mcp-server?

  • Modular architecture for server components
  • Easy integration with existing Rust projects
  • Supports various server functionalities through its components

use cases of mcp-server?

  1. Building custom server applications in Rust.
  2. Composing complex server architectures using modular components.
  3. Facilitating server development for various applications.

FAQ from mcp-server?

  • What programming language is mcp-server built with?

mcp-server is built using Rust.

  • Is mcp-server open source?

Yes! mcp-server is available under the MIT license.

  • How can I contribute to mcp-server?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCPStudio
Star
0
Language
-
License
MIT license

Recommend Servers

View All
Payai X402 Tools

2 hours ago
Payai X402 Tools

2 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.

a day ago