SiteCheck Crypto & Finance

CryptoRank top crypto projects by rank: name, symbol, type

finance_cryptorank_projects

Read-only

CryptoRank top crypto projects by rank: name, symbol, type, price, market cap, fully diluted valuation, 24h volume, 24h high/low, supply and all-time high, from CryptoRank's API v2. Up to the top 100. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "finance_cryptorank_projects"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many projects, 1 to 100 (default 10)

Output Schema

Name	Required	Description	Default
`count`	No
`source`	No
`projects`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish read-only and open-world behavior, and the description adds important operational context: API v2, a 100-project cap, x402 payment networks, per-success pricing, and no charge for failed calls. It does not cover rate limits or any additional authentication requirements beyond payment, so it is strong but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the resource and ranking scope, then lists the returned data fields, and finally gives the important billing constraints. Every sentence carries useful selection or invocation information, with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity, single-optional-parameter listing tool with full schema coverage, annotations, and an output schema, the description supplies everything an agent needs: source, ranking basis, data coverage, cap, and payment behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the single limit parameter is already fully documented in the schema. The description only reinforces the top-100 cap and does not add syntax or behavioral semantics beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that this tool returns CryptoRank's top crypto projects by rank, including the specific data fields and source API. It does not explicitly distinguish itself from sibling crypto-market tools such as finance_coinmarketcap or finance_coingecko, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by saying it returns top projects by rank, but it provides no explicit guidance on when to choose this tool over the many sibling crypto-market APIs. There are no exclusions or alternative-tool routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SiteCheck Crypto & Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?