Other · Remote MCP server
Ottasia
Where to watch X in Y? 30 Asian and Middle Eastern streaming markets, via Claude.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.AIweather-Anurag/ottasia- Version
- 0.1.3
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-05-23
- Updated
- 2026-05-23
- Publisher
- AIweather-Anurag (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/AIweather-Anurag) · how
- Repository
- github.com/AIweather-Anurag/ottasia-mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://ottasia.com/api/mcp/sse | None |
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 200)
- Handshake
- ottasia 0.2.0 · protocol 2025-06-18
- Tools discovered
- 3:
where_to_watch,whats_new_on,search_titles - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @ottasia/mcp-server | 0.1.3 | stdio |
How to connect Ottasia
Ottasia is a remote MCP server: there is nothing to install. Its endpoint is https://ottasia.com/api/mcp/sse, 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.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @ottasia/mcp-server version 0.1.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @ottasia/mcp-server@0.1.3.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"ottasia": {
"command": "npx",
"args": [
"-y",
"@ottasia/mcp-server@0.1.3"
]
}
}
}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
More other servers
| Server | Runs |
|---|---|
| OtakitInspect, upload, release, monitor, and revert OtaKit Capacitor OTA updates. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Otp MCPGenerate and verify time based one time passwords locally. No network and no key. | Local · stdio |
| Otp MCP ServerPublic MCP for OTP (orgtp.com). Query cross-org best practices, learnings, publishers, patterns. | Local · stdio |
| Otr ProtocolMerchant trust verification for AI agents. One call = trust score, badge, and purchase safety. | Local · stdio |
| OttoCreate, edit, schedule, and publish social posts in your own voice with your Otto account. | Remote · HTTPLive check: sign-in required |
| Otx MCPMCP server for AlienVault OTX: pulses, indicators. Free key. | Local · stdio |
| OuroborosPins an acceptance spec; the verify command and expected output never enter the success contract. | Local · stdio |
| Ourpr MCP ServerRead your own ourpr running history in an AI agent, and put a plan on the week ahead. | Local · stdio |