Tanod MCP Server (Deprecated)

by dev.tanod

Overview Discussions Admin

This connector has been deprecated

The correct URL is https://tanod.dev/mcp and NOT https://tanod.dev/mcp/ (CORRECT: NO TRAILING SLASH)

Correct Glama listing: https://glama.ai/mcp/connectors/dev.tanod/tanod

WRONG Glama listing: https://glama.ai/mcp/connectors/dev.tanod/tanod-mcp-server/

utilpeek: kimchi and USDT premium (BTC, ETH, USDT on local exchanges vs the global price)

get_local_crypto_premiums

Read-onlyIdempotent

utilpeek: Use when an agent needs to gauge local demand for crypto: the kimchi or USDT premium on local exchanges vs the global price. For global sentiment use get_crypto_fear_greed_index. Returns BTC, ETH and USDT on large local exchanges in KR, JP, ID, PH, TR, BR, MX and AR in USD, with each venue's premium to the global price and the FX source and date. Input: optional asset and country; both default to all. Last trades from public tickers, cached 30 s; references are Chainlink (BTC, ETH) and 1.0 (USDT); FX is the ECB daily fixing (BCRA for ARS), so under about 0.5 % is noise. Venue terms are unclear and each is credited. A failed venue is listed in errors; nothing priced is a 503 (not charged). Informational only, not investment advice. Typically under 0.5 s from cache; up to about 10 s when the venues are fetched. Price: USD 0.002. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/kimchi-premium-api.html

Input Schema

Name	Required	Description	Default
`asset`	No	BTC, ETH or USDT (default: all three)
`country`	No	ISO 3166-1 alpha-2: KR, JP, ID, PH, TR, BR, MX or AR (default: all)

Output Schema

Name	Required	Description
`asset`	No
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`notes`	No
`errors`	No
`quotes`	No
`country`	No
`credits`	No
`reference`	No	global USD price per asset
`disclaimer`	No
`retrieved_at`	No
`cache_seconds`	No
`stale_dropped`	No
`max_quote_age_s`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026
- addedOutput schema / properties / reference / additionalProperties / properties / age_seconds
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```
First observedOct 22, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds substantial context beyond them: public ticker source, 30s cache, Chainlink/ECB/BCRA reference and FX conventions, partial-failure behavior via `errors`, 503 when nothing is priced and not charged, and latency from 0.5s to ~10s.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and the disambiguation sibling before any detail, and nearly every sentence carries actionable information (caching, FX source, failure modes, pricing, rate limit). It is dense and long, and pricing/latency/legal lines could be tightened, but nothing is pure filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and rich annotations, the description still covers the operational details an agent needs: data provenance, freshness, partial-failure semantics, error status, and cost/quota. Nothing material for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% — the schema already documents the allowed values for `asset` and `country` plus their defaults. The description only restates 'optional `asset` and `country`; both default to all', adding no format or semantics beyond the schema, which is the baseline-3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb-and-resource pair ('gauge local demand for crypto: the kimchi or USDT premium on local exchanges vs the global price') and enumerates exactly what is returned (BTC, ETH, USDT across KR/JP/ID/PH/TR/BR/MX/AR). It also names the sibling get_crypto_fear_greed_index as the contrasting tool, so an agent can distinguish it without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use trigger ('Use when an agent needs to gauge local demand') and an explicit routing rule away from it ('For global sentiment use get_crypto_fear_greed_index'). The optional-filter defaults and the 'under about 0.5% is noise' threshold further tell the agent how to read results correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Tanod MCP Server (Deprecated) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?