Developer Tools
tarx.com
Provides tools to check, monitor, and install the TARX local daemon and mesh network.
ENDPOINT 1
https://mcp.tarx.com/mcp
Known tools 44
tarx_install_guideGet step-by-step TARX installation instructions for a specific platform.
Inferred read-onlytarx_initScan a GitHub repo to auto-detect framework, suggest key files, and generate a ~/.tarx/project.json config.
Inferred read-onlymesh_node_listList active mesh nodes with capabilities, reputation scores, and latency.
Inferred read-onlymesh_credits_balanceGet current mesh credits balance — earned by contributing compute, spent by consuming it.
Inferred read-onlytarx_context_snapshotRequest a compressed context brief from the cognitive engine.
Inferred read-onlytarx_model_statusGet currently loaded Soul and Mind models, their versions, fine-tune dates, and inference health status.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.tarx-com]
url = "https://mcp.tarx.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"tarx-com": {
"type": "http",
"url": "https://mcp.tarx.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: tarx-com
Remote MCP URL: https://mcp.tarx.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"tarx-com": {
"url": "https://mcp.tarx.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"tarx-com": {
"type": "http",
"url": "https://mcp.tarx.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "tarx-com",
"transport": "streamable-http",
"url": "https://mcp.tarx.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.