Triplewhale MCP Server

Created By
Triple-Whalea year ago
Triplewhale MCP Server
Overview

What is Triplewhale MCP Server?

Triplewhale MCP Server is a server that implements the Model Context Protocol (MCP), allowing users to manage context between large language models (LLMs) and external systems, specifically for the Triplewhale platform.

How to use Triplewhale MCP Server?

To use the server, install it via Smithery or run it locally using Node.js with your Triplewhale API key. You can then issue natural language commands to retrieve data from Triplewhale.

Key features of Triplewhale MCP Server?

  • Standardized protocol for managing context between LLMs and external systems.
  • Supports natural language queries for data retrieval.
  • Easy installation and setup via Smithery or local environment.

Use cases of Triplewhale MCP Server?

  1. Querying financial metrics like net profit or ad spend.
  2. Analyzing user engagement and revenue data.
  3. Integrating with other tools and systems for enhanced data management.

FAQ from Triplewhale MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a standardized protocol designed to facilitate communication between LLMs and external systems.

  • Do I need an API key to use the server?

Yes, you need a Triplewhale API key to access the server functionalities.

  • Is there a specific Node.js version required?

Yes, Node.js version 18.0.0 or higher is required.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Triple-Whale
Star
0
Language
TypeScript
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