Tako
v1.8.2Premium live data from S&P Global, FRED, OECD & more, plus web search, in one call.
Endpoint health
online- Last checked
- 11/20/2026, 4:17:54 AM
- Latency
- 177 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:io.github.TakoData%2Ftako-mcp
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"io.github.TakoData/tako-mcp": {
"url": "https://mcp.tako.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
4 shown · authentication unknown
Tako: Available Data
tako_available_data
Find what data Tako holds on an entity or a metric, and the canonical name it holds it under. Best for: questions about what Tako covers. Put a company, person, or place in `q` to list the metrics tracked on it; put a metric in `q` to list the entities it covers. Add `metric` when you know the measure — you get the resolved pair and a ready-to-run `next_call`. Search on the canonical names it returns, not your own phrasing — `tako_search` matches the graph's names, not yours. A name here means the graph tracks it, not that a card exists. If the follow-up search comes back empty, say Tako has no card for it rather than rephrasing the query. Hand a node id to `tako_graph_related` to see what else connects to it.
Schema valid · SHA-256 38e6c92c2216…
View input schema
{ "type": "object", "properties": { "q": { "type": "string", "minLength": 2, "description": "The entity or metric to look up by name — \"Carnival\", \"United States\", \"Nvidia\". Put the measure in `metric`, not here." }, "metric": { "description": "The measure, when you already know it — \"gross margin\", \"capex\". Supplying it resolves the entity+metric pair directly; omit it to browse everything the entity has.", "type": "string", "minLength": 2 }, "types": { "description": "Narrow resolution to one kind, an entity or a metric. Omit to resolve both.", "type": "string", "enum": [ "entity", "metric" ] }, "label": { "description": "NER label to prefer for `q` — a boost, not a filter. Set it when you can categorize the term: company → ORG, place → GPE, person → PERSON. It never applies to `metric`.", "type": "string", "enum": [ "PERSON", "ORG", "GPE", "LOC", "PRODUCT", "EVENT", "LANGUAGE", "MONEY", "METRIC", "STOCK_TICKER", "WEBSITE" ] }, "limit": { "description": "How many candidates to resolve for each of `q` and `metric`. Raising it widens what the tool considers, not just what it shows: a deeper metric can become the one `next_call` names.", "type": "integer", "minimum": 1, "maximum": 20 } }, "required": [ "q" ], "$schema": "http://json-schema.org/draft-07/schema#" }
Connections
streamable-http
https://mcp.tako.com/mcp