A trusted directory for business AI connections.
The registry is being built. Tell us if you want to be among the first businesses listed.
Why it's needed
AI assistants are starting to do real work: checking a supplier's stock, booking a delivery, asking a landlord whether a flat is free. To do this, they connect to businesses through a standard called the Model Context Protocol, or MCP. A business's MCP server is its AI doorway.
Doorways need trust. Who runs this one? Is it safe? Who is allowed in, and what may they do?
How it works, in three parts
-
Each company runs its own MCP server
Its own doorway, with its own information and tools. ZuriDev can build it, or the company's own developers can.
-
The registry validates it
We check each MCP server before it's listed: who owns it, that it works as described, and that it meets our security rules.
-
The registry authorizes connections
It records which companies may connect to which, and what each may do. A company approves who connects to it, and can withdraw that permission at any time.
So the registry is what connects companies to other companies: not by copying their data into one place, but by vouching for each company's own doorway and holding the list of who may use it.
An example Planned
Zuri Properties (zuri.properties), ZuriDev's planned real estate platform, will connect to the companies on it through their MCP servers and the registry.
Coming next Planned
- Removing a listing that stops meeting the rules.
- Public search of the registry.
- Plans and fees.
For developers
- The registry lists MCP servers with their owner, endpoints, the tools they expose and their validation status.
- Validation covers ownership of the domain, transport security, the declared tools, and a review against our security checklist.
- Authorization between businesses uses OAuth 2.1, as the MCP specification describes, with scopes per tool and short-lived tokens for each pair of companies.
- Early access: write to info@zuridev.online.