Skip to main content
ClaudeWave
MCP ServersOfficial Registry0 stars0 forks● TypeScriptUpdated today
ClaudeWave Trust Score
52/100
· OK
Passed
  • ✓Actively maintained (<30d)
  • ✓Documented (README)
Flags
  • !No standard license detected
  • !No description
Last scanned: 10/13/2026
Install in Claude Code / Claude Desktop
Method: Manual
Claude Code CLI
git clone https://github.com/Dcroyalty/cryptorisk-api
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "cryptorisk-api": {
      "command": "node",
      "args": ["/path/to/cryptorisk-api/dist/index.js"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
💡 Clone https://github.com/Dcroyalty/cryptorisk-api and follow its README for install instructions.
Use cases

MCP Servers overview

# UXUS — Agent Services

Pay-per-call primitives for AI agents, live at **[uxus.finance](https://uxus.finance)**.
Paid in USDC on Base via the [x402](https://x402.org) protocol — no accounts, no API
keys, no signup. A funded wallet is the whole integration.

## Services

| Endpoint | Price | What you get |
|---|---|---|
| `POST /api/llm` | $0.01 | LLM completion, 5-model fallback chain |
| `GET /api/scrape` | $0.01 | URL → clean markdown/text/html |
| `POST /api/extract` | $0.01 | messy text/URL → JSON in your schema |
| `POST /api/embed` | $0.01 | text → 1024-dim vectors (jina-embeddings-v3) |
| `GET /api/search` | $0.01 | live web search |
| `GET /api/risk/pro` | $0.02 | one call, one verdict: PROCEED / CAUTION / BLOCK + summary + reasons |
| `GET /api/risk/live/pro` | $0.02 | one-call verdict on a token's owner powers (can it still be paused, upgraded or rugged?) + reasons |
| `GET /api/risk` · `/api/risk/live` | free | risk score + verdict (no reasons/signals) |
| `GET /api/lookup` | free | universal address lookup, EVM + XRPL, chain auto-detected |
| `GET /api/entity` | free | entity attribution — what *is* this address |
| `GET /api/resolve` | free | ENS / Basenames, forward + reverse (forward-verified) |
| `GET /api/callerid` | free | should this wallet be answered? (for XMTP/Push) |
| `/api/shield/*` | free | per-user private wallet blocklist (signature-auth) |
| `GET /api/catalog` · `/openapi.json` · `/llms.txt` · `/.well-known/x402.json` | free | discovery |
| `POST /api/mcp` | free | MCP server (Streamable HTTP) over the free tools |

Every risk/verdict response carries a `disclaimer`: this is developer-grade
screening from public data (OFAC SDN list, community scam registries, on-chain
reads), not legal or compliance advice.

## Data

- **Sanctions** come from one place: the OFAC SDN list in `bad_addresses`
  (`source='ofac'`), refreshed **daily** by `/api/cron/refresh-lists` (guarded — a
  0-address upstream response aborts rather than wiping the table). `lib/entity.ts`
  is the only place that joins it. A non-OFAC blocklist hit is category `flagged`,
  not `sanctioned`, and is allowlistable.
- **Scoring fails open**: if a data source needed for a verdict is unavailable and
  there's no list hit, the response is `degraded:true` / verdict `CAUTION`, never
  `PROCEED`.

## Development

```bash
npm install
npm run dev        # http://localhost:3000
npm run build
```

Env (Vercel project settings):

| var | required | purpose |
|---|---|---|
| `DATABASE_URL` | yes | Neon Postgres |
| `CRON_SECRET` | yes | gates `/api/cron/*`; Vercel Cron sends it as `Authorization: Bearer` |
| `OPENROUTER_API_KEY` | for `/api/llm`, `/api/extract` | |
| `JINA_API_KEY` | for `/api/embed` | |
| `SERPER_API_KEY` / `BRAVE_API_KEY` | optional | `/api/search` (falls back to DuckDuckGo) |
| `ETHERSCAN_API_KEY` | optional | wallet history (falls back to Blockscout) |
| `CDP_API_KEY_ID` / `CDP_API_KEY_SECRET` | for x402 settlement | |

Scripts: `scripts/schema*.mjs` (create tables), `scripts/ingest*.mjs` (manual list
load — the scheduled path is `lib/refresh-lists.ts` + `scripts/ingest-entity.mjs`),
`scripts/shield-verify.mjs` (live E2E), `scripts/fix-sanctions.mjs` (one-shot
sanctions remediation, already run).

What people ask about cryptorisk-api

What is Dcroyalty/cryptorisk-api?

+

Dcroyalty/cryptorisk-api is mcp servers for the Claude AI ecosystem with 0 GitHub stars.

How do I install cryptorisk-api?

+

You can install cryptorisk-api by cloning the repository (https://github.com/Dcroyalty/cryptorisk-api) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is Dcroyalty/cryptorisk-api safe to use?

+

Our security agent has analyzed Dcroyalty/cryptorisk-api and assigned a Trust Score of 52/100 (tier: OK). See the full breakdown of passed checks and flags on this page.

Who maintains Dcroyalty/cryptorisk-api?

+

Dcroyalty/cryptorisk-api is maintained by Dcroyalty. The last recorded GitHub activity is dated 2026-10-12, with 0 open issues.

Are there alternatives to cryptorisk-api?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy cryptorisk-api to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: Dcroyalty/cryptorisk-api
[![Featured on ClaudeWave](https://claudewave.com/api/badge/dcroyalty-cryptorisk-api)](https://claudewave.com/repo/dcroyalty-cryptorisk-api)
<a href="https://claudewave.com/repo/dcroyalty-cryptorisk-api"><img src="https://claudewave.com/api/badge/dcroyalty-cryptorisk-api" alt="Featured on ClaudeWave: Dcroyalty/cryptorisk-api" width="320" height="64" /></a>

More MCP Servers

cryptorisk-api alternatives