home / mcp / cryptotwitter.space x402 mcp server
Provides gated pay-per-use access to premium CryptoTwitter.Space reports with automated revenue distribution to host, curator, and platform.
Configuration
View docs{
"mcpServers": {
"benschiller-cts-x402-mcp": {
"command": "node",
"args": [
"dist/x402McpServer.js"
],
"env": {
"PRIVATE_KEY": "YOUR_PRIVATE_KEY",
"HOST_ADDRESS": "0xHostAddress",
"CDP_API_KEY_ID": "cdp_key_id",
"CURATOR_ADDRESS": "0xCuratorAddress",
"PLATFORM_ADDRESS": "0xPlatformAddress",
"REPORTS_API_BASE": "https://cryptotwitter.space",
"CDP_WALLET_SECRET": "cdp_wallet_secret",
"CDP_API_KEY_SECRET": "cdp_key_secret",
"SMART_ACCOUNT_ADDRESS": "0xSmartAccountAddress",
"USDC_CONTRACT_ADDRESS": "0x036CbD53842c5426634e7929541eC2318f3dCF7e",
"RECEIVING_WALLET_ADDRESS": "0xYourReceivingWalletAddress"
}
}
}
}CryptoTwitter.Space x402 MCP Server enables authorized, pay-per-use access to premium CryptoTwitter.Space reports with automated on-chain revenue distribution. You interact with it through an MCP client to search, browse, and unlock paid content while funds are split automatically among host, curator, and platform wallets.
You connect an MCP client to the server and perform lookups for paid reports. Typical flows include searching for relevant reports, browsing available entries, and retrieving a paid report resource after completing a payment. The system uses x402pay for per-use access and CDP Wallet Smart Accounts to automatically distribute revenue to the host (50%), curator (30%), and platform (20%). Ensure your client is configured to handle paid content resources and to display secure links to verification audio where applicable.
Prerequisites: Node.js installed on your machine. You will also need access to an Ethereum-compatible environment for on-chain interactions.
# 1. Clone the project repository
git clone https://github.com/benschiller/cts-x402-mcp.git
cd cts-x402-mcp
# 2. Install dependencies
npm install
# 3. Configure environment variables
# Copy the example environment file and fill in keys and addresses
cp .env.example .env4. Start the Express server that powers the MCP interface.
npm run start:expressConfiguration and runtime flow are defined in the local setup and MCP client integration. The MCP server exposes a local Express-based API running on port 4021 for handling paid report requests and the distribution of funds through the CDP Wallet.
MCP client integration is guided by a separate MCP configuration block that demonstrates how to connect an external client to the local MCP server and enable common actions such as search, browse, and get-report-resource.
{
"mcpServers": {
"cts-reports-x402": {
"autoApprove": [
"search-reports",
"browse-reports",
"get-report-resource"
],
"timeout": 60,
"type": "stdio",
"command": "node",
"args": [
"dist/x402McpServer.js" // Path to your compiled server file
],
"env": {
"PRIVATE_KEY": "your_private_key_here"
}
}
}
}{
"mcpServers": {
"cts-reports-x402": {
"autoApprove": [
"search-reports",
"browse-reports",
"get-report-resource"
],
"timeout": 60,
"type": "stdio",
"command": "node",
"args": [
"dist/x402McpServer.js" // Path to your compiled server file
],
"env": {
"PRIVATE_KEY": "your_private_key_here"
}
}
}
}Query available paid reports by criteria and receive a list of results with summaries, timestamps, and access controls.
Browse through the paid reports catalog to preview previews and verify content before purchase.
Retrieve the paid report resources after completing a purchase, including metadata and access links.