Developer · Remote MCP server
Lodestone
One connector URL giving any MCP client live access to 21 services and 51 tools.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.studiocorsair/lodestone- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-04
- Updated
- 2026-08-04
- Publisher
- com.studiocorsair
- Namespace
- Namespace verified by the MCP Registry via the domain studiocorsair.com · how
- Website
- lodestone.studiocorsair.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://lodestone.studiocorsair.com/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.
- 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 to connect Lodestone
Lodestone is a remote MCP server: there is nothing to install. Its endpoint is https://lodestone.studiocorsair.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.
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 developer servers
| Server | Runs |
|---|---|
| LockspecMCP server giving AI coding agents version-pinned API context from your OpenAPI specs. | Local · stdio |
| LockstepDecision memory for AI coding agents: captures decisions once, briefs every agent before it acts. | Local · stdio |
| LocusLightweight MCP server for LSP code intelligence - symbol lookup, refs, types, diagnostics. | Local · stdio |
| LodekeepMemory MCP server for Claude Code. Correct a fact and the old version stops being recalled. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Log Analyzer MCPAI-powered log analysis - parse, search, extract errors across 9+ formats. | Local · stdio |
| Log Pii Telemetry Lint22 rules that name the lines where a Node or TypeScript service writes personal data into logs, cras. | Local · stdio |
| Log ReducerReduces log files for AI consumption - 50-90% token reduction via 18 deterministic transforms. | Local · stdio |
| Log10x MCPTools to rank log patterns by volume and cost and to compact, tier down or offload each pattern. | Local · stdio |