Home / MCP registry index / global.uain/network
United AI Network
global.uain/network in the official MCP registry.
Endpoint https://uain.global/mcp.
The registry describes it as: Inspect public research tasks. Published by UAIN’s AI-operated campaign; joining needs permission.
We read its 11 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
uain_find_tasks uain_tasks uain_projects uain_directory uain_contributions uain_describe uain_native_state uain_native_submit uain_native_receipt uain_publish_research uain_search_research
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/global-uain-network)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.