Tako MCP server
io.github.TakoData/tako-mcpTakoDatastreamable-httpv1.13.2Scanned
Premium live data from S&P Global, FRED, OECD & more, plus web search, in one call.
4 tools: 1 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Tako MCP server can do
The Tako MCP server is published by the GitHub account TakoData. It has 4 tools. It can create or change data (1 tool: tako_graph_related), but cannot delete data. 3 tools only read.
4 tools bring in text other people can write (tako_available_data, tako_contents, tako_graph_related and 1 more); 1 tool can send data out of your system (tako_contents).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 5 times since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 1.13.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 1Claude Code: ask
Only reads 3Show 3 read-only tools
tako_available_dataFind what data Tako holds on an entity or a metric, and the canonical name it holds it under.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "find": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Tako: Available Data
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
tako_contentsFetch the full content behind a url: a web page's text, or an exportable Tako card's data rows.Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "fetch": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.urls), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.urls): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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.
Annotations the server declares
- title: Tako: Fetch Contents
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
tako_searchSearch Tako's data graph and the web in one call: many results at once, as structured cards plus web results.Reads text others writeNo findings
Why it is in this group
- The name "tako_search" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "search" and "web": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Tako: Search
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:00 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.tako.com/.well-known/oauth-protected-resource
- Authorization servers
- https://mcp.tako.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.tako.com/mcp: tools/list returned 4 tools to an anonymous client, including tako_graph_related (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:tako_contentsOnly readsinputSchema
- Changed:tako_searchOnly readsinputSchema
Tools1 changed.~1 changedView diff
- Changed:tako_contentsOnly readsinputSchema
Tools2 changed.~2 changedView diff
- Changed:tako_contentsOnly readsinputSchema
- Changed:tako_searchOnly readsdescription
Tools2 changed.~2 changedView diff
- Changed:tako_contentsOnly readsinputSchema
- Changed:tako_searchOnly readsdescription
Tools3 changed.~3 changedView diff
- Changed:tako_available_dataOnly readsdescription
- Changed:tako_contentsOnly readsdescriptioninputSchema
- Changed:tako_searchOnly readsdescriptioninputSchema
Install
Pinned to version 1.13.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http tako https://mcp.tako.com/mcpclaude mcp add --transport http tako https://mcp.tako.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__tako__tako_available_data",
"mcp__tako__tako_search"
],
"ask": [
"mcp__tako__tako_contents",
"mcp__tako__tako_graph_related"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tako. Review it before you use it.
Capability tags behind 4 rules
- mcp__tako__tako_available_data untrusted-input
- mcp__tako__tako_contents untrusted-input, outbound
- mcp__tako__tako_graph_related untrusted-input
- mcp__tako__tako_search untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.TakoData/tako-mcp/verify?hash=314c8f3b36c87e63adbd79d4598246604022300b3f6e1b78ec475a6c501cd3ef" | jq -e '.changed == false'Pinned hash 314c8f3b36c8, from Nov 19, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.TakoData/tako-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.TakoData/tako-mcp)Source: MCP Registry · repository. Synced Nov 19, 2026, 02:17 UTC.
Tako MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Tako MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Tako MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Tako MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Tako MCP server have?
- 4 tools: 1 write, 3 read. tako_graph_related, tako_available_data, tako_contents and tako_search.
Does the Tako MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Tako MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): tako_contents.
Has the Tako MCP server changed its tools?
- Yes, 5 times since Anlyon Radar started tracking it, most recently on Oct 28, 2026. Every change is on this page and in its Atom feed.