用于检索和显示当前资产价格信息的模型上下文协议服务器。该服务器提供获取各种资产（包括贵金属和加密货币）实时价格信息的工具，方便大型语言模型访问和显示这些数据。
请注意，asset-price-mcp 目前处于早期开发阶段。随着我们不断开发和改进服务器，其功能和可用工具可能会发生变化和扩展。
Related MCP server: Bybit MCP Server
许多代码编辑器和其他 AI 客户端使用配置文件来管理 MCP 服务器。
您可以通过将以下内容添加到配置文件来配置asset-price-mcp服务器。
通过Smithery自动为 Claude Desktop 安装 asset-price-mcp ：
npx -y @smithery/cli install @mk965/asset-price-mcp --client claude{
"mcpServers": {
"Asset Price MCP": {
"command": "npx",
"args": ["-y", "asset-price-mcp"]
}
}
}{
"mcpServers": {
"Asset Price MCP": {
"command": "cmd",
"args": ["/c", "npx", "-y", "asset-price-mcp"]
}
}
}npm run buildnpm test此 MCP 服务器采用 MIT 许可证。这意味着您可以自由使用、修改和分发该软件，但须遵守 MIT 许可证的条款和条件。更多详情，请参阅项目仓库中的 LICENSE 文件。
Retrieves current pricing information for various assets including precious metals and cryptocurrencies
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states it 'retrieves current pricing information,' implying a read-only operation, but doesn't disclose behavioral traits like rate limits, data freshness, error handling, or authentication needs. This leaves gaps in understanding how the tool behaves.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the purpose ('retrieves current pricing information') and adds useful detail ('including precious metals and cryptocurrencies'). There's no wasted text, and it's appropriately sized for the tool's simplicity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has no parameters, no annotations, and no output schema, the description is adequate but minimal. It covers the basic purpose but lacks details on output format, data sources, or limitations. For a simple tool, it's passable but could be more complete to aid the agent fully.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, which is fine here. Baseline is 4 for 0 parameters, as it doesn't need to compensate for any gaps.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb ('retrieves') and resource ('current pricing information for various assets'), specifying asset types like precious metals and cryptocurrencies. It distinguishes the tool's purpose well, though without sibling tools, differentiation isn't needed. It's not a tautology and is specific enough for understanding.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or context. It mentions asset types but doesn't specify scenarios or limitations. Without siblings, this is less critical, but still lacks usage instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0get_asset_priceScored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get_asset_price' has a clearly defined purpose that cannot be confused with any other tool in this set.
The single tool name follows a clear verb_noun pattern ('get_asset_price'), and with only one tool, there is perfect consistency. There are no other tools to create naming conflicts or inconsistencies.
A single tool is too few for a server named 'Asset Price MCP Server', which suggests a broader scope for asset price operations. While the tool covers current pricing, the server lacks tools for historical data, price comparisons, or other related functions, making it feel thin and under-scoped.
The server is severely incomplete for an asset price domain. It only provides current pricing with no tools for historical prices, price alerts, asset lists, or market data analysis. This creates significant gaps that will limit agent functionality and cause failures in more complex tasks.
Unlock the power of real-time cryptocurrency data with our Crypto Price Insights MCP server.
Live crypto prices, conversion, gas tracker, portfolio tools, and calculators for AI agents.
Precious metals AI analyst with 12 tools — prices, portfolio, chat, receipts, and more.
The Dappier MCP server connects LLMs and AI agents to real-time, rights-cleared, proprietary data from trusted sources across various domains. It provides specialized knowledge through real-time web search, financial stock market and crypto data access, AI-powered content recommendations from premium publishers, and structured outputs with sub-300ms response times, enabling AI systems to respond to current events and trends.
