Kraken
io.github.pipeworx-io/kraken · v0.1.0 · MCP 2025-03-26
Kraken keyless public market: time, status, assets, pairs, ticker, OHLC, depth, trades.
Reachability
reachable
checked 2026-07-14 03:38 UTC
Registry status active
Tools pinned 39
2039f35e9c02
Tools last changed
unchanged since first capture 2026-07-14
Provenance
Registry namespace io.github.pipeworx-io
(GitHub-account verified by the official registry)
Repository
github.com/pipeworx-io/mcp-kraken
Website
https://pipeworx.io/packs/kraken
Remote endpoints
https://gateway.pipeworx.io/kraken/mcp (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-07-14 03:38 | first capture | 39 tools pinned |
Pinned tool definitions (39)
| Tool | Description |
|---|---|
| ask_pipeworx | PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto,... |
| ask_pipeworx_grounded | Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 4,876 across 1278 sources, fills arguments, fetches the data — then EXTRACTS the answer using ONLY what the tool result... |
| search_within | Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores.... |
| deep_research | ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across... |
| discover_tools | Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS... |
| resolve_entity | "What's the ticker for…" / "find the CIK for…" / "what's the RxCUI for…" / "look up the ID for…" / "what is X's official identifier" — resolve a user-spoken NAME to the canonical/official identifier other tools require as input. Use... |
| compare_entities | "Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over... |
| subscribe | Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching... |
| unsubscribe | Cancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts. |
| list_subscriptions | List the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel. |
| recent_alerts | Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type... |
| entity_profile | "Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company... |
| recent_changes | "What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE... |
| validate_claim | "Is it true that…" / "fact check" / "verify the claim that…" / "did X really…" / "was Y actually…" / "confirm or refute" / "true or false" — natural-language claim verification against authoritative sources. Use whenever the agent needs... |
| scan_dependency | Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use... |
| bet_research | Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug ("will-bitcoin-hit-150k-by-june-30-2026"), a polymarket.com URL, or a question text. The tool resolves the market, classifies the... |
| polymarket_arbitrage | Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a `trending_scan` of the top ~200 markets by weekly volume; pass `event` for the strongest per-event partition_check,... |
| polymarket_edges | Scan top Polymarket markets and return opportunities where Pipeworx data disagrees with market price. Built for "what should I bet on today" — agents discover opportunities without paging hundreds of markets. FIVE MODEL FAMILIES grouped... |
| polymarket_kalshi_spread | Cross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because their participant pools differ — when the bet shapes are equivalent that delta is a... |
| polymarket_fill_risk | Realizable-vs-theoretical edge check against live CLOB order-book depth. REQUIRES one of `market` (single-market mode) or `event` (basket/partition mode). SINGLE-MARKET: pass a market slug/URL + side (buy_yes|sell_yes|buy_no|sell_no,... |
| polymarket_edge_tracker | Edge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers "how long has this edge existed and is it shrinking?" — a fresh wide edge and a 3-week-old wide edge are different trades (the latter is wide for... |
| pipeworx_trending | What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2)... |
| suggest_questions | What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what... |
| generate_llms_txt | Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format.... |
| ai_visibility_check | Probe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model. Default model is Workers AI Llama-3.3-70b (free); pass `_apiKey` to also probe Anthropic (BYO key — you pay... |
| scan_competitor_ai_presence | Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits:... |
| pipeworx_feedback | Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well... |
| remember | Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't... |
| recall | Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from... |
| forget | Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall. |
| server_time | Return the Kraken exchange server time as Unix timestamp and RFC 1123 string. Use to synchronize request timestamps. |
| system_status | Return the current Kraken exchange operational status (online, cancel_only, post_only, limit_only, maintenance) and timestamp. |
| assets | Kraken crypto exchange asset info: precision, status, alt-name, conversion factor for crypto assets (BTC, ETH, USDT, etc.) and fiat. |
| asset_pairs | Kraken crypto exchange tradable pair info: base/quote, lot decimals, fee schedule, leverage limits, ordermin. Use as a directory before depth/ticker/ohlc calls. |
| ticker | Kraken crypto exchange live ticker for a pair (e.g. "XBTUSD"). Returns bid/ask, last trade, 24h volume + VWAP, open price. |
| ohlc | Kraken crypto exchange OHLC candles for a pair. Intervals 1, 5, 15, 30, 60, 240, 1440, 10080, 21600 minutes. Use for charting Kraken pairs. |
| depth | Kraken crypto exchange order book — bids + asks for a crypto pair. Returns price/volume/timestamp per level. Use for live depth-of-book on Kraken-listed pairs. |
| trades | Kraken crypto exchange recent trade tape for a pair. Returns price, volume, timestamp, buy/sell, market/limit. Use for tick-level execution analysis. |
| spread | Kraken crypto exchange recent bid/ask spread history for a pair. Returns timestamped best-bid + best-ask. Use for liquidity studies. |
Status badge
[](https://toolpin.dev/servers/io.github.pipeworx-io/kraken)
Maintain this server? Add the badge to your README — it links your users to this live status page.