This server retrieves real-time price information for precious metals (gold, silver) and cryptocurrencies (Bitcoin, Ethereum, etc.) using the Model Context Protocol (MCP).
Key capabilities:
Retrieve current asset prices by symbol (e.g., XAU for gold, BTC for Bitcoin)
Query prices in different currencies (default: USD)
List all supported assets available for price queries
Access multiple data sources including Gold API and CoinGecko with smart routing
Benefit from automatic caching for improved performance and rate limit compliance
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Asset Price MCP Server get current gold price in USD"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol server for retrieving and displaying current asset price information. This server provides tools to fetch real-time price information for various asset (including precious metals and cryptocurrencies), making it easy for large language models to access and display this data.
Retrieve prices for precious metals (Gold, Silver, etc.) via Gold API
Retrieve prices for cryptocurrencies via CoinGecko and Gold API
Smart routing to available data sources
Automatic caching for better performance and rate limit compliance
Please note that asset-price-mcp is currently in development.
Related MCP server: Bybit MCP Server
get_asset_priceRetrieves current pricing information for specific assets.
Arguments:
symbol (optional): The asset symbol to query (e.g., "XAU", "BTC", "ETH"). If omitted, returns a default list of major assets.
currency (optional): The currency to express the price in (default: "USD").
list_assetsLists all supported assets available for price queries.
Many code editors and other AI clients use configuration files to manage MCP servers.
You can configure the asset-price-mcp server by adding the following to your configuration file.
To install asset-price-mcp for Claude Desktop automatically via Smithery:
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 buildThis MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
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.
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.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Unlock the power of real-time cryptocurrency data with our Crypto Price Insights MCP server.
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.
The Octagon MCP server provides specialized AI-powered financial research and analysis by integrating with the Octagon Market Intelligence API. It enables users to analyze public market data (SEC filings, earnings transcripts, financial metrics, and stock data for 8000+ companies), private market data (3M+ companies, 500k+ funding rounds, 2M+ M&A/IPO transactions), and conduct deep research including web scraping capabilities. The server also features autonomous research agents that search hundreds of sources and return fully cited reports in approximately one minute.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mk965/asset-price-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
