← Registry

Developer Tools

ledgerstone.co

Access and search Ledgerstone public guide metadata and context documents.

1 endpoint2 known toolsFirst detected July 29, 2026Last detected July 29, 2026

ENDPOINT 1

https://ledgerstone.co/mcp

No auth detected

MCP server metadata

Name
ledgerstone.co
Version
1.0.0
Capabilities
toolsresources

Known tools 2

ledgerstone.search_guides

Search Ledgerstone public guide metadata.

Inferred read-only
ledgerstone.get_context

Return the public Ledgerstone agent context document.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.ledgerstone-co]
url = "https://ledgerstone.co/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "ledgerstone-co": {
      "type": "http",
      "url": "https://ledgerstone.co/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: ledgerstone-co
Remote MCP URL: https://ledgerstone.co/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "ledgerstone-co": {
      "url": "https://ledgerstone.co/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "ledgerstone-co": {
      "type": "http",
      "url": "https://ledgerstone.co/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "ledgerstone-co",
  "transport": "streamable-http",
  "url": "https://ledgerstone.co/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.