現在の資産価格情報を取得・表示するためのモデルコンテキストプロトコルサーバー。このサーバーは、様々な資産（貴金属や暗号通貨を含む）のリアルタイム価格情報を取得するためのツールを提供し、大規模な言語モデルによるデータへのアクセスと表示を容易にします。
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.
