Other · Remote MCP server
Seminara
Digital Teammate (Aura) hosting live interactive presentations, demos, and audience Q&A 24/7.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.shivamselam/seminara- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, SSE (HTTP + Server-Sent Events)
- Published
- 2026-09-05
- Updated
- 2026-09-05
- Publisher
- shivamselam (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/shivamselam) · how
- Repository
- github.com/shivamselam/seminara-agentic-suite
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://seminara.online/api/v1/mcp | None |
| SSE (HTTP + Server-Sent Events) | https://seminara.online/api/v1/mcp | 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.
- Endpoint
https://seminara.online/api/v1/mcp(HTTP)- Reachable
- Yes (HTTP 400)
- Handshake
- HTTP 400
- Checked on
- 2026-10-05
- Endpoint
https://seminara.online/api/v1/mcp(SSE)- Reachable
- Yes (HTTP 200)
- SSE stream
- Opened and named its message endpoint (not used further)
- Checked on
- 2026-10-05
How to connect Seminara
Seminara is a remote MCP server: there is nothing to install. Its endpoint is https://seminara.online/api/v1/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.
It also lists an endpoint on the older SSE transport https://seminara.online/api/v1/mcp. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
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.
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 |
|---|---|
| SelfpingText your own phone when a run finishes or needs you. A key can only message its own number. | Remote · HTTPLive check: ✓ handshake |
| SellbaseOpen source commerce in your own Supabase: catalog, checkout, orders and bookings, run by your AI. | Local · stdio |
| Seller AssistantConnect AI clients to Seller Assistant workflows for Amazon wholesale operations. | Remote · HTTPLive check: sign-in required |
| SemahashContent-addressed semantics: fail-closed handshakes over 457 cognitive patterns. | Local · stdio |
| SemioticVerified React chart generation: select, validate, repair, render, and inspect charts through MCP. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| SEMIPRO Cycling IntelligenceAnalyse cycling-event GPX routes and build bounded, practical ride-fuelling carry plans. | Remote · HTTPLive check: ✓ handshake |
| Semrush AppcenterManage subscriptions, users, and send event notifications for Semrush apps. | Local · stdio |
| Semver MCPParse, compare, and sort semantic version numbers locally. No network and no key. | Local · stdio |