trigslink-backend
Trigslink Backend — A modular blockchain backend that manages MCP (Modular Contract Providers) and consumer interactions, blockchain event listeners, AI-driven agents, and API services. Fully dockerized with multi-service architecture for scalable Web3 automation.
GitHub Stars
0
User Rating
Not Rated
Forks
0
Issues
0
Views
1
Favorites
0
Trigslink Backend Service
About
The MCP Backend is the central nervous system of the Modular Contract Providers ecosystem, featuring:
- Real-time blockchain event processing
- AI-powered decision automation
- Multi-chain smart contract integration
- Scalable microservice architecture
Core Capabilities
Blockchain Integration Layer
- Event-driven architecture for contract interactions
- Support for multiple contract standards
- Transaction verification and validation
AI Decision Engine
- Natural language processing for queries
- Dynamic tool selection based on MCP capabilities
- Context-aware response generation
Service Management
- End-to-end MCP lifecycle support
- Subscription management system
- Provider reputation tracking
🛠️ Technical Stack
Backend
- FastAPI (Python 3.8+)
- Uvicorn ASGI server
- Cloudinary media storage
Infrastructure
- Docker containerization
- Compose-based orchestration
- Trigslink tunneling
Data
- Blockchain-indexed data
API Documentation
MCP Registration
POST /register_mcp
Content-Type: multipart/form-data
Params:
- tx_hash: str (required) - Blockchain transaction hash
- logo: file (required) - Service logo image
Response:
{
"status": "registered",
"mcp_id": "0x..._123",
"logo_url": "https://res.cloudinary.com/...",
"metadata": { ... }
}
MCP Discovery
GET /available_mcps?[filters]
Filters:
- service_name: str - Partial name match
- wallet: str - Exact wallet match
- price_lte: float - Maximum price
Response:
[
{
"mcp_id": "0x..._123",
"service_name": "AI Oracle",
"price": 29.99,
"logo_url": "..."
}
]
AI Query Endpoint
POST /agent_query
Content-Type: application/json
Body:
{
"mcp_id": "0x..._123",
"user_prompt": "Analyze my portfolio risk",
"openai_api_key": "sk-...",
"env_vars": { ... }
}
Response:
{
"response": "Analysis shows...",
"sources": [...]
}
Deployment Guide
Prerequisites
- Docker and Docker Compose installed
- Required API keys (Blockchain RPC)
Step-by-Step Deployment
1️⃣ Clone the Repository:
git clone https://github.com/trigslink/backend.git
cd backend
2️⃣ Configure Environment:
cp .env.example .env
Edit the .env
file with your actual API keys and configuration.
3️⃣ Docker Deployment:
# Build and launch all services in detached mode
docker-compose up --build -d
# Monitor container logs
docker-compose logs -f
4️⃣ Verify Deployment:
curl http://localhost:8001/healthcheck
Expected response: {"status":"healthy"}
🔧 Environment Variables
Variable | Required | Description | Example |
---|---|---|---|
CLOUDINARY_CLOUD_NAME |
Yes | Cloudinary account name | your-cloud |
CLOUDINARY_API_KEY |
Yes | Cloudinary API key | 123456789 |
BLOCKCHAIN_RPC_URL |
Yes | Ethereum node RPC endpoint | https://mainnet.infura.io/v3/your-key |
OPENAI_DEFAULT_MODEL |
No | Default AI model | gpt-4-turbo |
Security
Implemented Protections
- CORS origin restrictions
- Request rate limiting (100 req/min)
- Input validation for all endpoints
- Quarterly API key rotation
Security Best Practices
- Always deploy behind HTTPS
- Restrict RPC access to whitelisted IPs
- Monitor logs for suspicious activity
- Use secrets management for sensitive keys
License
MIT License - Full text available in LICENSE.
Contact
Technical Support
Email: trigslink@gmail.com
YouTube: @trigslink
<<<<<<< HEAD © 2025 Trigslink. All rights reserved.
© 2025 Trigslink. All rights reserved.
7bb6a94 (WIP: before rebase)
108
Followers
828
Repositories
44
Gists
60
Total Contributions