Read the surface
Discover the tools exposed by the server before making a request.
CONNECT / MODEL CONTEXT PROTOCOL
Bring the system into the tools you already use.
OmniRoids is designed to be reached through an MCP-compatible client. The public endpoint is the front door; the actual tools and permissions remain intentionally explicit.
PUBLIC ENDPOINT
MCP server address
Use this address in an MCP client that supports remote HTTP servers. Authentication, rate limits, and available tools may change during the beta.
https://omniroids.com/mcpKeep a human in the loop
Consequential actions should stay reviewable and approval-gated.
Beta means moving ground
Follow CodeOnRoids for changes, experiments, and access updates.
02 / WHAT A CALL LOOKS LIKE
From your client to a recorded outcome.
01
Client connects
Any MCP client that speaks remote HTTP points at the endpoint.
02
Tools discovered
The server lists what is exposed. Nothing is implicit.
03
Human gate
Consequential calls wait for an approval before they run.
04
Result with a trail
The answer comes back with the evidence behind it.
03 / EARLY SIGNAL
Soon: beta testing for the people who follow along.
Rule three above is the short version. This is the long one: we are shaping the first public beta in the open, and the endpoint will keep changing while we do. Follow CodeOnRoids for experiments, agent drops, and the moment the doors open.