Transfer Entropy Api Sdk

io.github.nexus-mcp-infraPublished by GitHub account nexus-mcp-infrav1.0.0Updated Oct 24, 2026

Detect causal dependencies in time series

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant detect causal dependencies in time series data.

What you can do
  • Detects causal dependencies in time series, per the registry description.
  • No tools, parameters, or output formats are documented, so the exact operations an assistant can call are unknown.
  • No instructions or README are provided, so usage details must be confirmed with the provider.
When to use it
Consider it when you want an assistant to analyze time series for causal relationships between variables, such as directional influence between measured signals. Because the interface is undocumented, verify its behavior before relying on it.
Requirements
A remote streamable HTTP endpoint at the provider's host; no packages, environment variables, headers, or authentication are declared. Network access to that endpoint is required.
Before you install
The endpoint is hosted at a test address, so availability and stability are not guaranteed. No authentication is declared, so avoid sending sensitive or proprietary time series data. The tool set and data handling practices are undocumented.

Installation

In SourceWeft

  1. Open Transfer Entropy Api Sdk in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.nexus-mcp-infra%2Ftransfer-entropy-api-sdk/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "transfer-entropy-api-sdk": {
      "type": "http",
      "url": "https://test.railway.app/"
    }
  }
}

README

API

Source: README.md at commit 7ecc14b

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.