General Tools

steledger.com

Provides general-purpose tools through the Model Context Protocol.

1 endpoint5 known toolsFirst detected September 23, 2026Last detected September 23, 2026

ENDPOINT 1

https://api.steledger.com/mcp

No auth detected

MCP server metadata

Name: steledger
Version: 1.30.0

Capabilities

experimentalpromptsresourcestools

Server instructions

Give an AI agent a durable identity and a place to anchor what it knows, as records on a public blockchain that no single vendor owns or can switch off. Read tools (node_status, read_record, whoami) are open to everyone — no sign-in. Write tools (register_identity, store_memory) require a GitHub sign-in via OAuth, which your MCP client performs, from a GitHub account at least 30 days old; on the FREE tier writes are limited per minute and per day. Typical flow: whoami → register_identity(address) → store_memory(hash) → read_record(name). A write reads back as `pending` and becomes `confirmed` after the next block (about 8 minutes on average lately). The substrate is Emercoin, running since 2013 — named so that any record here can also be checked independently in a public block explorer, without trusting this service.

Known tools 5

node_status

Check that the chain node behind this service is healthy and fully synced: its version, block height, header height, peer connections and sync state.

Inferred read-only

read_record

Read one on-chain record by its full name — an agent's identity (`ai:gh:<github_id>`) or a memory (`ai:gh:<github_id>:mem:<hash>`) written by `register_identity` / `store_memory`.

Inferred read-only

whoami

Report the current session's identity.

Inferred read-only

register_identity

Create or rotate your on-chain identity record `ai:gh:<github_id>`, binding an Emercoin address to your GitHub identity.

Potential side effects

store_memory

Anchor a memory/artifact on-chain as the NVS record `ai:gh:<github_id>:mem:<content_hash>` — a tamper-evident fingerprint others can verify later.

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.steledger]
url = "https://api.steledger.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "steledger": {
      "type": "http",
      "url": "https://api.steledger.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: steledger
Remote MCP URL: https://api.steledger.com/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": {
    "steledger": {
      "url": "https://api.steledger.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "steledger": {
      "type": "http",
      "url": "https://api.steledger.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "steledger",
  "transport": "streamable-http",
  "url": "https://api.steledger.com/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.