MCP server for advanced web search using Tavily
Tako is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Premium live data from S&P Global, FRED, OECD & more, plus web search, in one call.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http takodata-tako-mcp-2 https://mcp.tako.com/mcp
# 2 — ask your agent for something these tools do
# tako_available_data, tako_contents, tako_graph_related and 1 more
Tako costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Its publisher asks you to sign in with OAuth: run /mcp in Claude Code and pick this server, and it opens a browser for that once.
claude mcp add --scope user --transport http takodata-tako-mcp-2 https://mcp.tako.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take Authorization header (Tako API token as a Bearer credential, e.g. `Bearer <token>` (CLI/desktop hosts such as Claude Code, Cursor, Windsurf). Get one at tako.com -> account settings -> API tokens. Web hosts (Claude.ai, ChatGPT) use the server's OAuth flow instead, so this header is optional.) if you want to set it.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Find what data Tako holds on an entity or a metric, and the canonical name it holds it under. Best for: coverage questions themselves, or a metric's canonical name before a priced search. 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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | yes | The entity or metric to look up by name — "Carnival", "United States", "Nvidia". Put the measure in metric, not here. |
| metric | string | no | 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. |
| types | string | no | Narrow resolution to one kind, an entity or a metric. Omit to resolve both. |
| label | string | no | 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 | no | 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. |
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 one is billed and fails on its own. Fetch only cards that tako_search marked exportable: true. Rows bill per 1,000 delivered, so set max_rows when the recent rows are enough. A website-traffic or SEO card also bills a per-unit data minimum that max_rows do
| Parameter | Type | Required | Notes |
|---|---|---|---|
| urls | array | yes | The urls to fetch: a Tako card url or a web result url. One call for 8 urls costs the same as 8 separate calls and saves 7 round trips. |
| max_rows | integer | no | Tako cards only: how many rows to return. Omit it for the whole card, up to 2,000 rows. Every row delivered is billed, so lower it when the recent rows are enough. |
| max_chars | integer | no | 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 |
| query | string | no | 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. |
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 unkn
| Parameter | Type | Required | Notes |
|---|---|---|---|
| node_id | string | yes | Public id of the node to explore, as returned by tako_available_data or on a tako_search card. |
| relation | string | no | 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. |
| q | string | no | Case-insensitive substring filter on names and aliases, one string per call: "revenue" matches Total Revenue and misses Sales. Call once per name variant. |
| label | string | no | NER label to prefer among the related nodes — a boost, not a filter. |
| infer_label | boolean | no | Detect labels from q. Omit it and the server infers them whenever q is set. |
| cursor | string | no | Page handle from a previous drilled relation. Omit it for the first page. |
| limit | integer | no | 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. |
Search Tako's data graph and the live web in one call: many results at once, as structured cards plus web results, with the top card rendered inline as a chart. It finds data; tako_contents fetches it. 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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 | no | Which corpora to search; default is both. Narrow to ["data"] once tako_available_data confirms coverage; narrow to ["web"] only for news or page text — website traffic is in the data graph. |
| country_code | string | no | 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 | no | BCP-47 locale tag for language and formatting. Omit it and the server uses en-US. Set it to localize for the user. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Tako or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| tako_available_data | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| tako_contents | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| tako_graph_related | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| tako_search | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.9.2.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Tako can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.