Developer · Remote MCP server

Oriora Router

AI model routing on your own vendor keys: pick model per prompt, or route and run it.

Visit Oriora Router's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
com.orioralabs/router
Version
0.1.1
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-07-16
Updated
2026-07-16
Publisher
com.orioralabs
Namespace
Namespace verified by the MCP Registry via the domain orioralabs.com · how
Website
orioralabs.com/managed-api-byok
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://api.orioralabs.com/mcpAuthorization (secret)

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
Checked on
2026-10-05

How the live check works

How to connect Oriora Router

Oriora Router is a remote MCP server: there is nothing to install. Its endpoint is https://api.orioralabs.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

Site checks

The website's own root, orioralabs.com, was checked for the files that tell AI systems about a site.

FileResult
/llms.txtReal file, HTTP 200 · 2026-10-04
/.well-known/mcp.jsonNo real file found
/.well-known/ai-plugin.jsonNo real file found
/agents.jsonNo real file found

More developer servers

All 5,152 →
ServerRunsEndpoint or package
OrchexAutopilot AI orchestration - auto-plan, parallelize, self-heal, and route across 6 LLMs.Local · stdionpm: @wundam/orchex
Ori MemoryPersistent memory infrastructure for AI agents. Identity, knowledge graph, and search.Local · stdionpm: ori-memory
Orionbelt AnalyticsOntology-based MCP server for database schema analysis and RDF/OWL ontology generation.Local · stdioPyPI: orionbelt-analytics
Orionbelt Semantic LayerAPI-first semantic layer MCP server compiling YAML models into dialect-specific SQL.Local · stdioPyPI: orionbelt-semantic-layer
Orm MCPMCP server for @mostajs/orm: generate, lint (24 rules) & migrate EntitySchemas.Local · stdionpm: @mostajs/orm-mcp
orm-preflightChecks TypeORM migrations for data loss, table locks, and deploy problems before they run.Local · stdionpm: orm-preflight
Orq.aiBuild and monitor LLM apps on Orq.ai: AI gateway, agents, prompts, evals, traces.Remote · HTTPLive check: sign-in requiredmy.orq.ai
OrquestaRead a project's prompts, logs and agents, and send new work to the agent on your own machines.Remote · HTTPLive check: sign-in requiredgetorquesta.com