# crypto_market_signal

Paid (x402, $0.005 USDC on Base). For each CoinGecko id return price, market cap, 24h change, 24h volume, plus a derived momentum score (-100..100), a bullish/neutral/bearish signal, and a volatility flag — enriched data an agent ingests in a trading/research loop.

Agent View of the PolicyLayer registry record for `crypto_market_signal`. HTML page: https://policylayer.com/tools/dev-charliemorrison-agent-web-reader/crypto-market-signal

## Facts

- Tool: `crypto_market_signal`
- Server: Agent Web Reader (`https://x402.charliemorrison.dev/mcp`) — https://policylayer.com/tools/dev-charliemorrison-agent-web-reader.md
- Homepage: https://github.com/charlie-morrison/x402-agent-data
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `ids` | string | yes | Comma-separated CoinGecko ids (e.g. 'bitcoin,ethereum,solana'), max 25 |
| `x402_payment` | string | no | Base64 X-PAYMENT header from your x402 wallet (omit to get the payment challenge) |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "crypto_market_signal",
    "arguments": {
      "ids": "<ids>"
    }
  }
}
```

## Why crypto_market_signal is rated Low

The tool fetches and enriches cryptocurrency market data (price, volume, momentum, signals) for ingestion in a trading/research loop. It does not itself execute trades or move funds.

From the tool's own definition: "'return price, market cap, 24h change, 24h volume, plus a derived momentum score, a bullish/neutral/bearish signal' — retrieves and enriches market data; no trade execution described"

## Use case

AI agents call crypto_market_signal to retrieve information from Agent Web Reader without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Agent Web Reader:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "crypto_market_signal": {}
  }
}
```

## Other tools on Agent Web Reader (2)

- `agent_web_reader` — Read — https://policylayer.com/tools/dev-charliemorrison-agent-web-reader/agent-web-reader.md
- `github_repo_seo_audit` — Read — https://policylayer.com/tools/dev-charliemorrison-agent-web-reader/github-repo-seo-audit.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-charliemorrison-agent-web-reader · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-charliemorrison-agent-web-reader