ToolTrust
A2/100
Smithery

axel-belfort-crypto-news

mcpsmithery

@Smithery

Real-time crypto news aggregator API for AI agents. Multi-source news feed with AI sentiment scores (bullish/bearish/neutral), token mentions, and trading signal relevance. Essential for news-driven trading strategies. Tools: crypto_get_latest_news. Use this for market sentiment analysis, news-based trading signals, event monitoring, or building crypto news dashboards. IMPORTANT: For fact-checking specific claims, use research_check_fact instead. Returns: {articles[], sentiment, tokenMentions[]}. No API key required — x402 micropayment $0.002/call on Base L2.

By Smithery | 4 findings | Scanned 7/18/2026 | tooltrust-scanner/v0.3.19

1 Low3 Info

Risk Summary

Safe With Normal Controls

Excessive Permissions is the main signal, but overall risk remains within an acceptable range.

Potential impact: The agent may gain overly broad access to files, network, databases, or execution capabilities.

Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.

Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.

Security Findings (4)

  • LowAS-011

    ℹ️Missing Rate-Limit / Timeout

    crypto_get_latest_news:tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration

    Fix: Declare explicit rate-limit, timeout, and retry configuration for all network and execution tools. Implement exponential back-off and surface resource state to the calling agent.

  • InfoAS-002

    ⚠️Excessive Permissions

    crypto_get_latest_news:declared capabilities: network access

    Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.

  • InfoAS-010

    🔑Insecure Secret Handling

    crypto_get_latest_news:input parameter "token" accepts a credential (informational; not evidence of insecure handling)

    Fix: Avoid accepting raw credentials as input parameters. Use secret managers (e.g. 1Password CLI, AWS Secrets Manager) and ensure credentials are never logged or stored in agent traces.

  • InfoAS-014

    ℹ️Dependency Inventory Unavailable

    crypto_get_latest_news:Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.

    Fix: Review and remediate the identified issue.

Scan this tool yourself

Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.

Install once, then scan any MCP server:

$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash
$ tooltrust-scanner scan --server "npx -y axel-belfort-crypto-news"

Adjust the package name if your npm registry name differs from the tool ID. View source

Add badge to your README

Copy this Markdown to show your ToolTrust grade on GitHub.

[![ToolTrust Grade A](https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-directory/main/docs/badges/grade-a.svg)](https://github.com/AgentSafe-AI/tooltrust-directory)