artifacts-mcp

Created By
djcopleya year ago
MCP Server for Artifacts MMO
Overview

what is artifacts-mcp?

artifacts-mcp is a server repository designed for the Artifacts MMO, providing a framework for managing and running MCP servers.

how to use artifacts-mcp?

To use artifacts-mcp, clone the repository from GitHub, configure the server path in the provided command, and run the server using the specified command line arguments.

key features of artifacts-mcp?

  • Easy setup for MCP servers for Artifacts MMO
  • Customizable server commands and arguments
  • Environment variable support for secure token management

use cases of artifacts-mcp?

  1. Setting up a dedicated server for Artifacts MMO gameplay.
  2. Managing multiple MCP servers for different game instances.
  3. Customizing server configurations for enhanced gameplay experiences.

FAQ from artifacts-mcp?

  • What is the purpose of artifacts-mcp?

artifacts-mcp is designed to facilitate the setup and management of MCP servers for the Artifacts MMO.

  • How do I run the server?

You can run the server by executing the command with the specified arguments in your terminal.

  • Is there a license for using artifacts-mcp?

The repository does not specify a license, so please check the repository for any updates.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
djcopley
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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