Repository navigation
AgentTCDH v0.1.0
npm registry notice (2026-10-28):
agent-tcdh@0.1.0was withdrawn during account migration and cannot be republished at the same version. This GitHub tarball remains available. See v0.1.1 for the replacement package and its npm publication status.
AgentTCDH v0.1.0
Register MCP servers and A2A agents in one shared registry. Consumers discover capabilities and connection details through MCP, A2A, or HTTP, then call their selected targets directly.
This first release includes persistent registration management, CLI administration, remote metadata import/refresh/check, search and pagination, separate read/admin tokens, conditional updates, JSON backups, OpenAPI documentation, and a local three-target demo.
Install
Requires Node.js 24 or newer. The release includes a built, installable npm tarball; GitHub's automatic source archives require a build.
npm install --global https://github.com/jiind/agent-tcdh/releases/download/v0.1.0/agent-tcdh-0.1.0.tgz
agent-tcdh --help
agent-tcdh serveAfter the npm package is published, the equivalent registry commands are:
npx --yes agent-tcdh@0.1.0 --help
npx --yes agent-tcdh@0.1.0 serveThe default listener is http://127.0.0.1:3000; the default SQLite database is ~/.agent-tcdh/registry.sqlite. Configure shell environment variables for authentication and deployment as described in the reference.
Verification and assets
- Native regression and isolated production-package installation checks cover Linux x64, macOS ARM64/x64, and Windows x64. Linux container checks cover non-root execution, health, protocols, and persistence.
- Release automation reruns those checks for the tag, then installs and exercises the exact downloadable tarball.
SHA256SUMScovers the tarball andrelease.json. The manifest records version, tag, full source commit, and package SHA-256. Download all three assets and runsha256sum --check SHA256SUMSon Linux,shasum -a 256 --check SHA256SUMSon macOS, or compareGet-FileHash -Algorithm SHA256output on PowerShell.- Public MCP calls, actual agent selection, and Gemini/Jev adapter calls are recorded separately in the verification reports. They remain opt-in and are not run by release CI.
Scope
The hub discovers targets and returns metadata. Consumers own selection, MCP/A2A clients, credentials, and execution permissions. Dynamic native tool mounting depends on the client. This release does not proxy target calls or run an AI planner. Protocol compatibility does not guarantee support in every commercial agent.
The SQLite schema is version 2 and portable snapshot format is version 1. This is an initial 0.x release; future versions may change APIs. Export registrations before upgrading.