Tako
REMOTE · MCP.TAKO.COM
Premium live data from S&P Global, FRED, OECD & more, plus web search, in one call.
Available components
Last scanned (1 hour ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2036 tokens (~339/item across 6 items; 4 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 0
- Server version: 1.8.3 → 1.9.0 functional
- 2 Nov 26 0
- Server version: 1.8.2 → 1.8.3 functional
- 30 Oct 26 0
- Server version: 1.8.1 → 1.8.2 functional
- 29 Oct 26 0
- Server version: 1.8.0 → 1.8.1 functional
- 28 Oct 26 −3
- Schema quality: 100% → 50% ▼ functional
- Schema quality: 402 → 339 ▲ functional
- First check of Capabilities: pass functional
- New resource “open_chart_ui_widget” functional
- Server version: 1.7.0 → 1.8.0 functional
- Server version: 1.6.2 → 1.7.0 functional
- “tako_contents” reworded the description of “premium” cosmetic
- “tako_search” reworded the description of “sources” cosmetic
- 27 Oct 26 +3
- Tool “tako_search” rewrote its description, which is the text the model reads security
- Schema quality: 457 → 402 ▲ functional
- Schema quality: 457 → 403 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- The server now declares the “resources” capability functional
- New resource “tako-search” functional
- Server version: 1.6.1 → 1.6.2 functional
- Server version: 1.6.0 → 1.6.1 functional
- Server version: 1.5.0 → 1.6.0 functional
- “tako_contents” added an optional parameter “offset” cosmetic
- “tako_contents” added an optional parameter “premium” cosmetic
- “tako_contents” reworded the description of “format” cosmetic
- “tako_contents” reworded the description of “offset” cosmetic
- “tako_contents” reworded the description of “premium” cosmetic
- 24 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “tako_available_data” rewrote its description, which is the text the model reads security
- Tool “tako_contents” rewrote its description, which is the text the model reads security
- Tool “tako_search” rewrote its description, which is the text the model reads security
- Server version: 1.4.5 → 1.5.0 functional
- “tako_contents” added an optional parameter “delivery” cosmetic
- “tako_contents” added an optional parameter “format” cosmetic
- “tako_contents” reworded the description of “max_rows” cosmetic
- “tako_contents” reworded the description of “urls” cosmetic
- “tako_search” reworded the description of “sources” cosmetic
- 21 Oct 26 0
- Server version: 1.4.4 → 1.4.5 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.tako.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tako.com | CN=WE1,O=Google Trust Services,C=US | 21 Oct 2026 | 19 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 76c8bcbe747c57c41393e1e9ae384384 |
| SANs: tako.com, mcp.tako.com, *.mcp.tako.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.tako.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tako.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.tako.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.tako.com/mcp | HTTPS enforced | 301 | https://mcp.tako.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
tako_available_data Tako: Available Data ~390
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.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | 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`. |
| limit | integer | – | 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. |
| metric | string | – | 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. |
| q | string | yes | The entity or metric to look up by name — "Carnival", "United States", "Nvidia". Put the measure in `metric`, not here. |
| types | string | – | Narrow resolution to one kind, an entity or a metric. Omit to resolve both. |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | yes | The other nodes `q` resolved to, best first. |
| entity | – | – | Lookup path: the resolved entity. |
| entity_candidates | array | – | Runners-up. |
| found | boolean | yes | Whether Tako holds matching data; `verified` says on what evidence. |
| guidance | string | – | The verdict, and the one next action. |
| matches | array | yes | The nodes whose coverage was drilled, best first. |
| metric | – | – | Lookup path: the resolved metric. |
| metric_candidates | array | – | Runners-up. |
| next_call | – | yes | A follow-up search in canonical names. Null when no target is unambiguous. |
| verified | string | – | What was checked. `pair`: the metric is on the entity's own list. `coverage`: a list was drilled. `unlinked`: the list was checked, the metric is absent. `resolution`: names resolved only. |
No examples provided.
tako_contents Tako: Fetch Contents ~578
Fetch the full content behind a url: a web page's text, or an exportable Tako card's data rows. Batch up to 10 urls in one call — each fails on its own. Fetch only cards that `tako_search` marked `exportable: true`. Set `max_rows` when the recent rows are enough. If a page is long, such as a filing or an annual report, set `query` to a question to get back only the passages that answer it. Best for: reading one source in full — a page you need to quote, or the rows behind a card you need to compute over.
| Name | Type | Req | Description |
|---|---|---|---|
| delivery | string | – | Tako cards only. `inline` returns the data in the result. `link` returns a download link: a CSV file, or a JSON file with `format: "card"`. It expires in 5 minutes. Use `link` when you can run shell… |
| format | string | – | Tako cards only. `rows` returns the card's data as one table. `card` returns the card's own structure, such as a company card's tabs or a game's box score. |
| max_chars | integer | – | Web pages only: character cap on the extracted text. Inline fetches default to 100,000 per url, less across a batch. Raise it for a long document; `truncated` reports a cut. With `query`, it caps the… |
| max_rows | integer | – | Tako cards only: how many rows to return. Omit it to get up to 2,000 rows. With `delivery: "link"`, you can raise it to 100,000. Charges scale with rows returned, so lower it when the recent rows are… |
| offset | integer | – | Tako list cards only: rows to skip. With `max_rows: 1`, it fetches a single row. |
| premium | boolean | – | Tako cards only: `true` returns premium cells, shown as 🔒. Charges scale with the rows that hold one, so set it only when the user asks. For one row, pass its own Tako link with `max_rows: 1`. Other… |
| query | string | – | Web pages only: a question the passages should answer. The result holds those passages instead of the page. Omit it to get the whole page. |
| urls | array | yes | The urls to fetch: a Tako card url or a web result url. One call for 8 urls saves 7 round trips. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | One per requested url, in order. |
| usage | object | yes | What this request cost. |
No examples provided.
tako_graph_related Tako: Graph Related ~397
Explore what a graph node connects to — its metrics, the entities a metric covers, competitors, industry, index membership, and sources. Two modes. Pass `node_id` alone for the map: every relation group with its key, label, total, and its first 3 names. Pass `relation` to page one group, where each item comes back with the id that explores it. Read a key off the map rather than guessing — an unknown key returns an empty group, not an error. Best for: expanding a node you already resolved. Resolve a name to a node id with `tako_available_data` first. A metric listed here means the graph tracks it, not that a card exists — `tako_search` is the final check.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Page handle from a previous drilled relation. Omit it for the first page. |
| infer_label | boolean | – | Detect labels from `q`. Omit it and the server infers them whenever `q` is set. |
| label | string | – | NER label to prefer among the related nodes — a boost, not a filter. |
| limit | integer | – | Page size for a drilled relation. Omit it and the server serves 50. Ignored on the map, where every group returns its first 3 names whatever you pass. |
| node_id | string | yes | Public id of the node to explore, as returned by `tako_available_data` or on a `tako_search` card. |
| q | string | – | Case-insensitive substring filter on names and aliases, one string per call: "revenue" matches `Total Revenue` and misses `Sales`. Call once per name variant. |
| relation | string | – | Relation key to page, taken from the map: metrics, entities, siblings, part_of, members, or a named edge like rel:competes_with. Omit for the map. |
| Name | Type | Req | Description |
|---|---|---|---|
| node | object | yes | – |
| relation | – | – | The one group you drilled. |
| relations | array | – | Every group, previewed. The map. |
No examples provided.
tako_search Tako: Search ~430
Search Tako's data graph and the web in one call: many results at once, as structured cards plus web results. The first card's chart renders inline; some hosts also show every other card's chart, in search's order. It finds results; `tako_contents` fetches what's behind them. Each card carries a headline value, node ids, and a url — pass the url to `tako_contents` for rows (`exportable: true` cards) or a web result's full page text. When `exportable` is false the rows are locked — read the headline value from the card's `description`. Best for: breadth — fan out several narrow queries in parallel. Each query answers one question — one metric for one entity, a comparison set ("Apple revenue", "Nvidia vs AMD gross margin"), one news or web lookup ("EU AI Act timeline"), or one list of companies, or of business professionals by role and place, for prospecting or recruiting ("fintechs in London", "CFOs in Austin"); several metrics or topics in one query retrieve poorly.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | – | ISO 3166-1 alpha-2 country code for localized results. Omit it and the server uses US. Set it to localize for the user. |
| locale | string | – | BCP-47 locale tag for language and formatting. Omit it and the server uses en-US. Set it to localize for the user. |
| query | string | yes | Natural-language search query (e.g. "US GDP growth", "Intel vs Nvidia revenue"). Double-quote a multi-word name to keep it one entity ("tesla motors" club revenue); an unpaired quote disables quoting… |
| sources | array | – | Which corpora to search; default is both. `data` is Tako's data graph, curated from authoritative data sources; `web` is the open web. Keep both unless the user asks for one. |
| Name | Type | Req | Description |
|---|---|---|---|
| cards | array | yes | The data cards. Fetch an exportable card's rows with tako_contents on its url. |
| guidance | string | – | How to unlock a placeholder card or a card's premium cells. |
| metric_definitions | object | – | What each metric means (unit, basis, caveats), keyed by metric name, deduped across cards. |
| source_notes | object | – | What each source is and how it builds its data, keyed by source name. |
| usage | – | yes | Cost-plus usage for this request (null when not metered). |
| web_results | array | yes | Web results. |
No examples provided.
How do I install the Tako MCP server?
Tako is a hosted endpoint at https://mcp.tako.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.tako.com
claude mcp add --transport http takodata-tako-mcp 'https://mcp.tako.com/mcp'
What is the Tako MCP server?
Tako is an MCP server listed in the public MCP registry as io.github.TakoData/tako-mcp. Premium live data from S&P Global, FRED, OECD & more, plus web search, in one call. This page covers its hosted endpoint (https://mcp.tako.com/mcp).
Is the Tako MCP server safe to use?
Tako scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Tako MCP server expose?
Tako exposes 4 tools: tako_available_data, tako_contents, tako_graph_related, tako_search. Their descriptions and schemas cost roughly 1,795 tokens of context every time the server is loaded.
Does the Tako MCP server require authentication?
No. We connected to Tako without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Tako MCP server still maintained?
Tako is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.