MCP Mesh Network + Decentralized Tool Discovery — TensorGate becomes the first MCP “exchange” where AI agents discover and call each other’s tools. Any MCP server can register its tools in a public, searchable registry. Agents find tools by capability (“I need a tool that sends emails”) and call them through a single connection, with trust scoring, health monitoring, and community voting to ensure quality.
New MCP Tools (4)
tgate_discover — Search the decentralized tool registry. Find tools by capability, keyword, or category. Returns matching tools with server info, trust scores, call counts, and average latency. FTS5 full-text search on the hub.
tgate_mesh_call — Call a tool on any remote MCP server through the TensorGate mesh. Proxied via the hub with latency tracking and trust scoring. Supports any tool on any registered server with a StreamableHTTP endpoint.
tgate_mesh_ask — Natural language tool routing. Describe what you need in plain English (“send an email to bob@test.com saying hello”) and TensorGate discovers the best tool, extracts arguments from your intent using heuristic pattern matching, and calls it automatically. Like DNS for AI tools.
tgate_registry_publish — Register your MCP server and its tools in the decentralized registry. Makes your tools discoverable by any AI agent worldwide. Supports both StreamableHTTP and stdio transports.
Hub — Registry API (11 endpoints)
GET /api/v1/registry/stats — Registry-wide statistics: total servers, tools, mesh calls, healthy servers.
GET /api/v1/registry/servers — List registered servers (paginated, filterable by health status and author, sorted by trust score).
GET /api/v1/registry/servers/:id — Server detail with all its registered tools.
POST /api/v1/registry/servers — Register or update a server and its tools (requires tg_ API key). Supports upsert by name+author.
DELETE /api/v1/registry/servers/:id — Remove a server and all its tools (cascading delete).
GET /api/v1/registry/tools — Search tools using FTS5 full-text search with LIKE fallback. Supports q (query), category filter, pagination.
GET /api/v1/registry/tools/:id — Tool detail with server info and parsed input schema.
POST /api/v1/registry/servers/:id/vote — Community voting (1-5 stars). IP-fingerprinted to prevent duplicate votes.
GET /api/v1/registry/categories — List tool categories with counts.
POST /api/v1/registry/discover — Intent-based tool discovery. Excludes servers marked as “down”.
Hub — Mesh Proxy
POST /api/v1/mesh/call — Proxy tool calls to remote MCP servers. Looks up the server in the registry, sends a JSON-RPC tools/call request to its StreamableHTTP endpoint, logs the call for analytics, and updates call counts + rolling average latency on both tool and server records. 30-second timeout. Rejects calls to servers without endpoints or marked as “down”.
Hub — Background Services
- Health Checker (5-minute interval) — Probes every registered server with an
endpoint_url by sending a tools/list JSON-RPC request. Response <5s = healthy, 5-15s = degraded, timeout/error = down. Updates health_status and last_health_check.
- Trust Scorer (15-minute interval) — Computes a weighted trust score for each server: health (30%), reliability from last 100 mesh calls (30%), latency normalized 500ms-10s (20%), community vote average (20%). Scores range 0-1.
- Auto-Publish (on startup) — Seeds the registry with TensorGate’s own 19 tools across 5 categories (bittensor, crypto, mining, defi, mesh). Sets
is_verified=1 and initial trust score of 0.9.
Hub — New Database Tables (5)
registry_servers — MCP server registry with trust score, health status, call stats, verification flag.
registry_tools — Tools per server with input schema, tags, category, call counts, latency stats.
registry_tools_fts — FTS5 virtual table for full-text search across tool name, description, tags, and category.
registry_votes — Community voting (1-5) per server, deduplicated by IP fingerprint.
mesh_calls — Call log for analytics and trust scoring: server, tool, latency, success/error.
MCP Server — New Modules
src/mesh/registry.ts — Hub registry API client: search tools, discover by intent, mesh call proxy, publish servers, get stats.
src/mesh/client.ts — MCP StreamableHTTP client wrapper using JSON-RPC. Connection pooling with 5-minute TTL.
src/mesh/argument-mapper.ts — Heuristic intent-to-argument extraction. Extracts emails, URLs, subjects, body text, numbers, booleans, token symbols from natural language. Also provides tool-match scoring for ranking discovery results.
Changed
- Tool count increased from 15 to 19.
- MCP server version bumped to 2.0.0, hub version bumped to 2.0.0.
- Published to npm as
tensorgate@2.0.0.
Architecture
- User’s AI agent connects to TensorGate MCP server (stdio) →
tgate_discover searches registry → tgate_mesh_call proxies through hub → hub calls remote server via StreamableHTTP → result returned to agent.
tgate_mesh_ask chains the full flow: discover → rank by trust+relevance → extract arguments → call → return result. One-shot natural language tool invocation.