Developer · Remote MCP server
super-log Cloud
Read your team's hosted journal from an AI agent: every machine's streams, in hub order.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.super-log/super-log-cloud- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-19
- Updated
- 2026-09-19
- Publisher
- com.super-log · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain super-log.com · how
- Website
- super-log.com
- Repository
- github.com/saxonnicholls/super-log
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.super-log.com/mcp | Authorization (required, 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; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect super-log Cloud
super-log Cloud is a remote MCP server: there is nothing to install. Its endpoint is https://api.super-log.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 (required, 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
More from com.super-log
| Server | Runs |
|---|---|
| Super LogQuery your local -log bench from an AI agent - read-only log tools over the hub. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| Sunstone Weave: Local Semantic Code SearchSemantic search over local folders of code and docs, with a code-search encoder running on your CPU. | Local · stdio |
| SupabaseConnect to your Supabase database to query data and schemas. | Remote · HTTP, SSELive check: ✗ no handshake |
| SupabaseYour Supabase account in natural language: run SQL, apply migrations, manage tables, storage, edge f. | Remote · HTTPLive check: ✓ handshake |
| SuperagntAI agent toolkit: live social media data, lead enrichment + email finder, Postgres DB, webhooks. | Remote · HTTPLive check: sign-in required |
| SuperCompressCompress coding-agent context ~64%. Hosted Neural Keep MCP for Cursor/Claude/Codex. | Remote & Local · HTTP, stdioLive check: sign-in required |
| SuperheroSuperhero MCP - wraps akabab.github.io/superhero-api (free, no auth) | Remote · HTTPLive check: ✓ handshake |
| SupericonsMultilingual semantic SVG icon search with previews for AI coding agents. 20,000+ icons. | Remote & Local · HTTP, stdioLive check: ✓ handshake |