"Host Tracker MCP server endpoint" matching MCP servers:

Connects AI agents to any standard A2A endpoint, with built-in Agent Card validation.

Connects any MCP host to the Haven Agent Gateway, enabling session creation, agent discovery, collaboration, handoff, and work operations through MCP tools over stdio or Streamable HTTP.

A Python code execution sandbox based on IPython and Docker. Stateful code execution, file transfer between host and container, configurable network access.

A secure, containerized workspace for LLMs to autonomously code, test, and debug projects without risking the host machine.

Use a fmsg address for a fmsg host. Tools for inbox, threads, send and reply, reactions, attachments, delivery status and wait-for-message over the host's WebSocket so agents can hold conversations with people or other agents. Runs over stdio locally or as a Streamable HTTP endpoint where each user authenticates with their own fmsg API key.

Enables any MCP host to drive durable, always-on agents that run server-side on the Highway Workflow Engine via three tools: run_goal, get_status, and approve.

A host-agnostic model council that routes tasks across multiple AI workers (MCP, CLI, API) and returns one unified answer.

A Windows-native MCP gateway that lets any MCP-capable host orchestrate local coding-agent CLIs as external workers.

An MCP server that gives Claude (or any MCP-compatible AI host) read access to industrial sensor data and safety-gated control over motors and actuators.

A self-hosted MCP server that lets Claude (or any MCP client) drive Autodesk Fusion 360 on your own machine.

Lets one Codex instance send a task to another Codex instance on a different computer, enabling symmetric host-to-host collaboration including projectless tasks and local environment dependent work.

MCP server for the Baton task tracker, enabling AI agents to manage tasks, process inbox events, and collaborate with humans via natural language. Wraps the Baton REST API with 12 tools over stdio.

A task management system for LLM-based agents that stores all tasks in a single tree, available immediately after the server starts.

A server that uses the Model Context Protocol (MCP) to allow AI agents to safely execute shell commands on a host system.

Enables coordinating multiple AI coding sessions by tracking features, decisions, and approval gates in a per-project Postgres database, with atomic IDs and commit-stamped append-only history.

A TypeScript-based REST API that integrates project and task management with MCP (Model Context Protocol), allowing users to manage projects and tasks through natural language interactions.

One deterministic reasoning stack behind a single MCP endpoint, chaining scenario simulation, decision analysis, and precision computation with 40-digit decimal math.

An MCP bridge that lets Codex and Claude Code interact with OpenLinker agents, and allows the host to serve as a callable agent in the OpenLinker network.

Enables AI agents to control a persistent Chrome browser through a local daemon, with Jev performing routine actions and the host agent handling reasoning, text, and verification.

Enables any MCP host to pose typed yes/no, choice, and score questions and receive calibrated probabilistic judgments instead of prose, over stdio and offline by default.