General Tools

saascloud.ai

Provides general-purpose tools through the Model Context Protocol.

x402 supported1 endpoint11 known toolsFirst detected August 4, 2026Last detected August 4, 2026

ENDPOINT 1

https://cryptopulse.saascloud.ai/mcp

No auth detected

MCP server metadata

Name: cryptopulse
Version: 1.0.0

Capabilities

tools

Server instructions

CryptoPulse crypto market intelligence. Every tool is pay-per-call in USDC on Base via the x402 protocol: an unpaid tools/call returns HTTP 402 with a PAYMENT-REQUIRED header; retry the identical POST with a PAYMENT-SIGNATURE header. Prices are in each tool description.

Known tools 11

price

[$0.

Inferred read-only

trending

[$0.

Inferred read-only

fear_greed

[$0.

Inferred read-only

gas

[$0.

Inferred read-only

ohlc

[$0.

Inferred read-only

token_pairs

[$0.

Inferred read-only

token_risk

[$0.

Inferred read-only

yields

[$0.

Inferred read-only

token_score

[$0.

Inferred read-only

screener

[$0.

Inferred read-only

market_summary

[$0.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.cryptopulse]
url = "https://cryptopulse.saascloud.ai/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "cryptopulse": {
      "type": "http",
      "url": "https://cryptopulse.saascloud.ai/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: cryptopulse
Remote MCP URL: https://cryptopulse.saascloud.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "cryptopulse": {
      "url": "https://cryptopulse.saascloud.ai/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "cryptopulse": {
      "type": "http",
      "url": "https://cryptopulse.saascloud.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "cryptopulse",
  "transport": "streamable-http",
  "url": "https://cryptopulse.saascloud.ai/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.