Data · Local MCP server
Taranis AI
Search stories and discover OSINT sources in Taranis AI.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.taranis-ai/taranis-mcp-server- Version
- 0.1.1
- Status
- Active
- Category
- data
- Transport
- stdio (local process)
- Package
- PyPI, OCI image (Docker)
- Published
- 2026-08-06
- Updated
- 2026-08-06
- Publisher
- taranis-ai (GitHub)
- Repository
- github.com/taranis-ai/taranis-mcp-server
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | taranis-mcp-server | 0.1.1 | stdio |
| OCI image (Docker) | ghcr.io/taranis-ai/taranis-mcp-server:0.1.1 | — | stdio |
How to connect Taranis AI
Taranis AI runs locally from a Python package published to PyPI: taranis-mcp-server version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx taranis-mcp-server. It reads these environment variables: MCP_TRANSPORT, TARANIS_API_URL (required), TARANIS_ACCESS_TOKEN (secret), TARANIS_USERNAME and TARANIS_PASSWORD (secret); set them in the client's configuration for this server.
Taranis AI runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/taranis-ai/taranis-mcp-server:0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm -e MCP_TRANSPORT -e TARANIS_API_URL -e TARANIS_ACCESS_TOKEN -e TARANIS_USERNAME -e TARANIS_PASSWORD ghcr.io/taranis-ai/taranis-mcp-server:0.1.1. It reads these environment variables: MCP_TRANSPORT, TARANIS_API_URL (required), TARANIS_ACCESS_TOKEN (secret), TARANIS_USERNAME and TARANIS_PASSWORD (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"taranis-mcp-server": {
"command": "uvx",
"args": [
"taranis-mcp-server"
],
"env": {
"MCP_TRANSPORT": "<value>",
"TARANIS_API_URL": "<value>",
"TARANIS_ACCESS_TOKEN": "<secret>",
"TARANIS_USERNAME": "<value>",
"TARANIS_PASSWORD": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More data servers
| Server | Runs |
|---|---|
| Talmud ScrollerTalmud a few lines a day, explained, with today's Daf Yomi, search and tractates in English. | Remote · HTTP |
| TalvalValue-investing research: fair values, valuation verdicts, quality scores and 13F portfolios. | Remote · HTTP |
| TapcartTapcart analytics, App Studio blocks and components, and push campaigns for your mobile app. | Remote · HTTP |
| Tape — Hyperliquid AnalyticsLive Hyperliquid perps analytics for agents: funding, OI, whale prints, leaderboard, wallet risk. | Remote · HTTP |
| Tariff DataUS import tariff rates and landed-cost data for AI agents and ecommerce. | Remote · HTTP |
| Tariff ResolverUS import duty research: HTS codes, Chapter 99 duties, MPF/HMF fees, landed cost. USITC data. | Local · stdio |
| tariff.watchSource-linked US tariff and trade-action changes: legal status, effective dates, dated archive. | Remote · HTTP |
| Tariffmonitor MCPUS import tariff estimates: HTS lookup and stacked rate (MFN + Section 301 + 232). No API key. | Local · stdio |