esp-component-registry-mcp

Created By
kumekaya year ago
MCP Server for ESP Component Registry (
Overview

what is esp-component-registry-mcp?

The esp-component-registry-mcp is a server designed for managing and providing access to the ESP Component Registry, which is a repository for various components used in ESP projects.

how to use esp-component-registry-mcp?

To use the esp-component-registry-mcp, you can clone the repository from GitHub and set up the server according to the provided documentation. Once set up, you can access the component registry through the specified endpoints.

key features of esp-component-registry-mcp?

  • Centralized management of ESP components
  • Easy access to component information and updates
  • Integration with existing ESP projects

use cases of esp-component-registry-mcp?

  1. Managing components for IoT projects using ESP technology.
  2. Providing a unified interface for developers to access component data.
  3. Facilitating updates and version control for ESP components.

FAQ from esp-component-registry-mcp?

  • What is the purpose of the esp-component-registry-mcp?

It serves as a server for managing and accessing the ESP Component Registry, making it easier for developers to find and use components.

  • Is there any documentation available?

Yes! Documentation is available in the GitHub repository to help you set up and use the server.

  • What license is the project under?

The project is licensed under the Apache-2.0 license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kumekay
Star
0
Language
-
License
Apache-2.0 license

Recommend Servers

View All
Gpt Scrambler

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

2 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago