Home / MCP registry index / io.github.BuilderIO/agent-native-dispatch

Agent-Native Dispatch

io.github.BuilderIO/agent-native-dispatch in the official MCP registry. Endpoint https://dispatch.agent-native.com/mcp. Source: github.com/BuilderIO/agent-native.

The registry describes it as: Central Slack/Telegram router with jobs, memory, approvals, and A2A delegation

Not read yet. The index re-reads every listed server about once a week, and this one is in the queue. You can check it yourself right now.

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-builderio-agent-native-dispatch/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-builderio-agent-native-dispatch)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Slack MCP servers · Memory and knowledge MCP servers

getwowlink
com.getwowlink/mcp
6 tools, nothing matched
2026-10-22
Tenpace Review Router
io.github.tenpace-app/review-router
5 tools, nothing matched
2026-10-22
ai.backengine/backengine-mcp
ai.backengine/backengine-mcp
needs credentials to list tools
2026-10-21
Stumpy
ai.stumpy/agents
needs credentials to list tools
2026-10-21
ai.waystation/mcp
ai.waystation/mcp
not reachable
2026-10-22
ai.waystation/slack
ai.waystation/slack
not reachable
2026-10-22