zed-metta-mcp

Created By
JungeWerthera year ago
MCP server for interfacing with MeTTa
Overview

what is zed-metta-mcp?

zed-metta-mcp is an MCP server designed for interfacing with MeTTa, providing a platform for developers to connect and interact with the MeTTa framework.

how to use zed-metta-mcp?

To use zed-metta-mcp, clone the repository from GitHub, set up the server environment, and follow the documentation to configure the server for your specific needs.

key features of zed-metta-mcp?

  • Easy integration with the MeTTa framework
  • Supports various configurations for server setup
  • Open-source with an MIT license

use cases of zed-metta-mcp?

  1. Developing applications that require interaction with the MeTTa framework.
  2. Creating custom interfaces for data processing using MeTTa.
  3. Facilitating communication between different components of a software system.

FAQ from zed-metta-mcp?

  • Is zed-metta-mcp free to use?

Yes! zed-metta-mcp is open-source and available under the MIT license.

  • How can I contribute to zed-metta-mcp?

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

  • What programming languages does zed-metta-mcp support?

zed-metta-mcp is designed to be language-agnostic, allowing integration with various programming languages.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JungeWerther
Star
0
Language
-
License
MIT 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