Elevar MCP Server

Created By
mattcoatswortha year ago
Overview

what is Elevar MCP Server?

Elevar MCP Server is a Model Context Protocol (MCP) server designed for interacting with the Elevar API, providing tools and resources for managing data sources and querying analytics data.

how to use Elevar MCP Server?

To use Elevar MCP Server, clone the repository, install the dependencies, create a .env file with your Elevar API key, and start the server using npm commands.

key features of Elevar MCP Server?

  • Manage data sources effectively
  • Query analytics data with ease
  • Test server functionality using MCP Inspector

use cases of Elevar MCP Server?

  1. Creating and managing data sources for analytics.
  2. Querying specific data from various data sources.
  3. Testing server responses and functionality through a web interface.

FAQ from Elevar MCP Server?

  • What is the purpose of the MCP Inspector?

The MCP Inspector allows users to browse resources, test tools with different inputs, and view server logs.

  • How do I set up the server?

Clone the repository, install dependencies, set up your API key in a .env file, and run the server.

  • Where can I find the API documentation?

The official documentation can be found at Elevar API Documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mattcoatsworth
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
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.

8 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago