boopai

Created By
boopaispacea year ago
The boopai-mcp server implements Solana blockchain functionality for the Letsboopai launchpad.
Overview

what is boopai?

boopai is a server that implements Solana blockchain functionality specifically designed for the Letsboopai launchpad, enabling decentralized applications and services on the Solana network.

how to use boopai?

To use boopai, developers can integrate the server with their applications by following the documentation provided in the GitHub repository. This includes setting up the server and utilizing its API for blockchain interactions.

key features of boopai?

  • Implements Solana blockchain functionality
  • Supports decentralized application development
  • Provides a launchpad for new projects on Solana

use cases of boopai?

  1. Launching new decentralized applications on the Solana blockchain.
  2. Facilitating transactions and smart contracts on Solana.
  3. Supporting developers in building and deploying blockchain-based solutions.

FAQ from boopai?

  • What is the purpose of boopai?

boopai serves as a backend server for developers to leverage Solana's blockchain capabilities for their projects.

  • Is boopai open source?

Yes! boopai is available on GitHub under the MIT license.

  • How can I contribute to boopai?

Contributions can be made by submitting pull requests on the GitHub repository.

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