MCP.so
登录

Goldsky MCP Server已验证已精选

@Goldsky

基本信息

传输方式

Streamable HTTP

认证方式

无需认证

分类

数据与分析

作者

Goldsky

提交者

Elliott Charbonneau

关于 Goldsky MCP Server

Search and read Goldsky docs from your AI tool: Feeds wallet balance and transfer APIs, prebuilt onchain datasets, Turbo pipelines, Subgraphs, and Edge RPC across 150+ chains.

连接信息

https://docs.goldsky.com/mcp

接入方式

claude mcp add goldsky --transport http https://docs.goldsky.com/mcp

Goldsky MCP Server 工具

3

Search across the Goldsky knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Goldsky, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`).

Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Goldsky documentation pages. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call. Examples (replace the placeholder paths with real ones from `tree` or search): - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /some-directory/` — show matches with 3 lines of context around each hit - `head -80 /some/page.mdx` — read the top 80 lines of a specific page - `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call - `cat /some/page.mdx` — read a full page when you need everything Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.

Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.

概览

What is Goldsky?

Goldsky provides onchain data for apps and finance teams. This MCP server lets AI tools search and read the Goldsky documentation.

Products

  • Feeds: REST APIs for wallet balances and transfers, with USD values, on 8 EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Robinhood Chain, Arc). $0.35 per 1,000 requests.
  • Datasets: prebuilt onchain datasets, browsable at https://app.goldsky.com/explore: blocks, logs, traces, ERC-20/721/1155 transfers, balances, Solana DEX trades, stablecoin and RWA transfers, and Hyperliquid fills.
  • Turbo pipelines: stream any dataset into your database, queue, or webhook.
  • Subgraphs: managed subgraph hosting, compatible with The Graph.
  • Edge RPC: managed RPC.

Goldsky supports 150+ chains.

Tools

  • search_goldsky: search the docs. Returns snippets with titles and links.
  • query_docs_filesystem_goldsky: read full doc pages.
  • submit_feedback: report a problem with a docs page.

Connect

URL: https://docs.goldsky.com/mcp (streamable HTTP, no authentication).

常见问题

1

Goldsky 远程 MCP 服务器是什么?

Goldsky 的远程 MCP 服务器是一个托管的 Model Context Protocol 端点,地址是 https://docs.goldsky.com/mcp,AI 助手无需在本地安装或运行任何东西即可连接。

2

怎么连接 Goldsky 的 MCP 服务器?

把端点 https://docs.goldsky.com/mcp 添加到任意支持 MCP 的客户端,比如 Claude Code、Cursor 或 VS Code。本页的接入代码块可以一步配置好每个客户端。

3

Goldsky 的 MCP 服务器需要认证吗?

不需要。Goldsky 的 MCP 服务器不需要认证——直接用端点地址连接即可。

4

Goldsky 的 MCP 服务器用的是哪种传输方式?

Goldsky 暴露的是 Streamable HTTP 端点,这是远程 MCP 服务器普遍使用、主流客户端都支持的传输方式。

评论