CryptoPulse Data API
REMOTE · CRYPTOPULSE.SAASCLOUD.AI · SCANNED SEP 20
Pay-per-call crypto market intelligence for AI agents. USDC on Base via x402.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1068 tokens (~97/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the CryptoPulse Data API MCP server?
CryptoPulse Data API is a hosted endpoint at https://cryptopulse.saascloud.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · cryptopulse.saascloud.ai
claude mcp add --transport http ai-saascloud-cryptopulse 'https://cryptopulse.saascloud.ai/mcp'
{
"mcpServers": {
"ai-saascloud-cryptopulse": {
"url": "https://cryptopulse.saascloud.ai/mcp"
}
}
} {
"servers": {
"ai-saascloud-cryptopulse": {
"type": "http",
"url": "https://cryptopulse.saascloud.ai/mcp"
}
}
} [mcp_servers.ai-saascloud-cryptopulse] url = "https://cryptopulse.saascloud.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-saascloud-cryptopulse": {
"type": "remote",
"url": "https://cryptopulse.saascloud.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-saascloud-cryptopulse --url 'https://cryptopulse.saascloud.ai/mcp' --transport streamable-http
mcp_servers:
ai-saascloud-cryptopulse:
url: "https://cryptopulse.saascloud.ai/mcp" {
"McpServers": {
"ai-saascloud-cryptopulse": {
"Transport": "http",
"Url": "https://cryptopulse.saascloud.ai/mcp"
}
}
} assistant mcp add ai-saascloud-cryptopulse -t streamable-http -u 'https://cryptopulse.saascloud.ai/mcp'
{
"mcpServers": {
"ai-saascloud-cryptopulse": {
"type": "http",
"url": "https://cryptopulse.saascloud.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Sept 26 0
- Stability: 0.97 → pass security
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://cryptopulse.saascloud.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=saascloud.ai | CN=WE1,O=Google Trust Services,C=US | 8 Sept 2026 | 8 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 316ab15cc7ed70460e77cab63462bb38 |
| SANs: saascloud.ai, cryptopulse.saascloud.ai, *.cryptopulse.saascloud.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of cryptopulse.saascloud.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| saascloud.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cryptopulse.saascloud.ai/mcp | Verified | 200 | |
| http (plaintext) | http://cryptopulse.saascloud.ai/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fear_greed ~38
[$0.002 USDC per call via x402] Current Crypto Fear & Greed Index value and classification, plus previous day for trend.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gas ~51
[$0.002 USDC per call via x402] Live gas price (wei and gwei) for Base or Ethereum mainnet from public RPC.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | base (default) or ethereum |
No output schema declared.
No examples provided.
market_summary ~59
[$0.01 USDC per call via x402] One-call market brief: BTC/ETH/SOL prices with 24h change, Fear & Greed index, and top-5 trending coins. Ideal for agents that need a single snapshot.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ohlc ~111
[$0.005 USDC per call via x402] OHLC candlestick data for any CoinGecko coin id (1, 7, 14, 30, 90, 180, 365 days).
| Name | Type | Req | Description |
|---|---|---|---|
| days | string | – | 1 | 7 | 14 | 30 | 90 | 180 | 365 |
| id | string | yes | CoinGecko coin id, e.g. bitcoin |
| vs | string | – | Quote currency (default usd) |
No output schema declared.
No examples provided.
price ~88
[$0.002 USDC per call via x402] Spot prices for one or more cryptocurrencies in any fiat/crypto quote currency. Comma-separated CoinGecko ids.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | string | yes | Comma-separated CoinGecko coin ids, e.g. bitcoin,ethereum,solana |
| vs | string | – | Quote currency (default usd), e.g. usd, eur, btc |
No output schema declared.
No examples provided.
screener ~190
[$0.10 USDC per call via x402] Token screener: trending or newly-launched pools on a chain, filtered by minimum liquidity and 24h volume, with optional on-chain safety screening (drops honeypots and balance-modifiable tokens). Returns ranked opportunities with price, liquidity, volume, buys/sells and safety flags.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | Max results (default 10, max 20) |
| min_liquidity | string | – | Minimum pool liquidity USD (default 50000) |
| min_volume | string | – | Minimum 24h volume USD (default 10000) |
| mode | string | – | trending (default) or new |
| network | string | – | GeckoTerminal network id, e.g. base, eth, solana (default base) |
| safe_only | string | – | true = run security screen on Base tokens and drop dangerous ones |
No output schema declared.
No examples provided.
token_pairs ~72
[$0.01 USDC per call via x402] DEX trading data for a token: pairs, price, liquidity, volume, 24h txns/change across DEXes. Search by symbol, name, or contract address.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | Token symbol, name, or contract address |
No output schema declared.
No examples provided.
token_risk ~97
[$0.02 USDC per call via x402] Token security / rug-pull risk check for any ERC-20 (honeypot, mintable, owner privileges, tax, LP holders). Essential pre-trade safety check for trading agents.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | ERC-20 token contract address (0x...) |
| chain | string | – | base | ethereum | bsc | polygon | arbitrum (default base) |
No output schema declared.
No examples provided.
token_score ~122
[$0.05 USDC per call via x402] Composite 0-100 buy-safety score for any token: combines contract security analysis (honeypot, taxes, ownership risks) with live market depth (liquidity, volume, activity) into a single verdict: avoid | high-risk | caution | ok | strong. One call answers 'should my agent touch this token?'
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token contract address (0x...) |
| chain | string | – | base | ethereum | bsc | polygon | arbitrum (default base) |
No output schema declared.
No examples provided.
trending ~40
[$0.002 USDC per call via x402] Top trending cryptocurrencies right now (most-searched coins, with rank, price and 24h change).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
yields ~138
[$0.02 USDC per call via x402] Top DeFi yield opportunities: highest-APY pools filtered by chain and minimum TVL, with project, symbol, APY breakdown and stablecoin flag. Data from DefiLlama.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Chain name, e.g. Base, Ethereum, Solana, Arbitrum (default Base) |
| limit | string | – | Max pools to return (default 10, max 50) |
| min_tvl | string | – | Minimum pool TVL in USD (default 1000000) |
| stable_only | string | – | true = only stablecoin pools |
No output schema declared.
No examples provided.
What is the CryptoPulse Data API MCP server?
CryptoPulse Data API is an MCP server listed in the public MCP registry as ai.saascloud/cryptopulse. Pay-per-call crypto market intelligence for AI agents. USDC on Base via x402. This page covers its hosted endpoint (https://cryptopulse.saascloud.ai/mcp).
Is the CryptoPulse Data API MCP server safe to use?
CryptoPulse Data API scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CryptoPulse Data API MCP server expose?
CryptoPulse Data API exposes 11 tools: price, trending, fear_greed, gas, ohlc, and 6 more. Their descriptions and schemas cost roughly 1,006 tokens of context every time the server is loaded.
Does the CryptoPulse Data API MCP server require authentication?
No. We connected to CryptoPulse Data API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CryptoPulse Data API MCP server still maintained?
CryptoPulse Data API is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.