Nostr Ecosystem Metrics over MCP

Curated, methodology-documented metrics over Nostr ecosystem data - starting with the Zapstore app store - queryable by AI agents over the Model Context Protocol. Free at present, no authentication.

Connect your agent

MCP server URL

https://dev.nostrolo.gy/mcp

claude mcp add --transport http nostrology https://dev.nostrolo.gy/mcp

Applies to new sessions. An agent with shell access can run this itself.

Edit ~/.codex/config.toml

[mcp_servers.nostrology]
url = "https://dev.nostrolo.gy/mcp"

Edit ~/.hermes config.yaml (or: hermes mcp)

mcp_servers:
  nostrology:
    url: "https://dev.nostrolo.gy/mcp"

MCP support ships with the standard install; /reload-mcp applies config edits.

Edit opencode.json

{
  "mcp": {
    "nostrology": {
      "type": "remote",
      "url": "https://dev.nostrolo.gy/mcp",
      "enabled": true
    }
  }
}

Settings -> Connectors -> Add custom connector -> URL: https://dev.nostrolo.gy/mcp

Edit ~/.cursor/mcp.json (or .cursor/mcp.json per-project)

{
  "mcpServers": {
    "nostrology": {
      "url": "https://dev.nostrolo.gy/mcp"
    }
  }
}

Edit .vscode/mcp.json (or MCP: Add Server)

{
  "servers": {
    "nostrology": {
      "type": "http",
      "url": "https://dev.nostrolo.gy/mcp"
    }
  }
}

Edit cline_mcp_settings.json

{
  "mcpServers": {
    "nostrology": {
      "type": "streamableHttp",
      "url": "https://dev.nostrolo.gy/mcp"
    }
  }
}

type streamableHttp matters: omitting it falls back to legacy SSE.

Edit mcp_config.json

{
  "mcpServers": {
    "nostrology": {
      "serverUrl": "https://dev.nostrolo.gy/mcp"
    }
  }
}

Edit settings.json (Settings -> AI -> MCP Servers -> Add Remote Server)

{
  "context_servers": {
    "nostrology": {
      "url": "https://dev.nostrolo.gy/mcp"
    }
  }
}

Edit ~/.config/goose/config.yaml

extensions:
  nostrology:
    type: streamable_http
    enabled: true
    name: nostrology
    uri: https://dev.nostrolo.gy/mcp
    timeout: 300

One-off alternative: goose session --with-streamable-http-extension <the endpoint URL above>

gemini mcp add --transport http nostrology https://dev.nostrolo.gy/mcp

Edit config.yaml

mcpServers:
  - name: Nostrology
    type: streamable-http
    url: https://dev.nostrolo.gy/mcp

Harness has no remote-MCP support?

Bridge the endpoint into a local stdio server with mcp-remote:

npx mcp-remote https://dev.nostrolo.gy/mcp

Catalog

Three tools. nostrology_query_metric serves the free quantitative metrics, routed by the metric parameter; nostrology_query_reference serves the free reference records (qualitative entity data - catalog entries, publisher profiles, release history), routed by the record parameter; and nostrology_query_nutzaps serves the nutzaps metrics, paid per call in Cashu ecash - its card states the price (pick the Nutzaps pill), and calling it without a token returns the payment terms for free. Every response carries its own envelope: scope, window, freshness, column contract, and the methodology caveats stating what is and is not counted. Pick a domain below; more arrive as their data is exposed.

zapstore routstr nutzaps

zapstore metrics

app_stack_count stacks / current - entities

Counts, per app, the DISTINCT public kind-30267 (zapstore-app-stacks) stacks whose a-tags reference it - the CURRENT state, one row per referenced app; apps in no public stack are absent. This is a snapshot, not a time series: there is no day axis and the counts must NOT be summed across calls.

app_zaps zaps+msats / day, total

Per-app Zapstore zap totals: each row is one app - identified by (publisher_pubkey, app_id) - carrying the COUNT of kind-9735 (zap-receipts) receipts (zap_count) and the SUM of their amounts in MILLI-satoshis (zapped_msats; divide by 1000 for sats) over the requested window. grain=total: one row per app over the whole window; grain=day: one row per (UTC day, app), sparse - (day, app) pairs with zero receipts are omitted.

native_release_count releases / day - sparse

Counts kind-30063 (zapstore-app-releases) release rows in the NATIVE partition per UTC day - releases, not distinct apps: a developer who ships 30 patch versions contributes 30 rows, and one app recurs across many days.

new_native_app_count apps / day - sparse

Counts DISTINCT apps (pubkey, app_d_tag) whose first-ever kind-30063 (zapstore-app-releases) release event falls on that UTC day - apps, not release events.

new_republished_app_count apps / day - sparse

Counts DISTINCT apps (pubkey, app_d_tag) whose first-ever kind-30063 (zapstore-app-releases) release event falls on that UTC day - apps, not release events.

publisher_app_count apps / current - entities

Counts, per publisher key, the DISTINCT Nostr-native apps in the kind-32267 (zapstore-app-catalog) universe - the CURRENT state, one row per publisher with at least one native entry. This is a snapshot, not a time series: no day axis, and counts must NOT be summed across calls.

republished_release_count releases / day - sparse

Counts kind-30063 (zapstore-app-releases) release rows in the REPUBLISHED partition per UTC day - releases, not distinct apps: an app that ships 30 patch versions contributes 30 rows, and one app can appear on many days.

zap_count zaps / day - sparse

Counts kind-9735 (zap-receipts) zap receipts attributed to a Zapstore app per UTC day - receipts, not distinct zappers, recipients or apps: one zapper funding ten apps contributes ten rows, and one app recurs across many days.

zapped_msats msats / day - sparse

Sums the amount of kind-9735 (zap-receipts) zap receipts attributed to a Zapstore app per UTC day, in MILLI-satoshis (msats) - divide by 1000 for sats. Counts amounts, not zaps: for the number of receipts behind these amounts use zapstore.zap_count over the same population.

zapstore reference data

app_catalog reference - current state

The CURRENT kind-32267 (zapstore-app-catalog) entry per app - name, tagline, website/repository links, native flag - scoped to one publisher (publisher_pubkey, required) or one app (add app_id, which also adds the full description text). Reference data, not a metric: no measures, no time axis, rows ordered by app_id.

app_releases reference - event listing

Every kind-30063 (zapstore-app-releases) release event for one publisher (publisher_pubkey, required) or one app (add app_id, which also adds the markdown release_notes column) - version, channel, links, commit, timestamp - newest first. An event LISTING, not an aggregate: count rows for release counts (the store-wide daily counts live in zapstore.native_release_count / republished_release_count). from/to (inclusive UTC calendar days over released_at) window the listing.

publisher_profile reference - current state

The CURRENT kind-0 (profile-metadata) profile per Zapstore publisher - publisher_name, about, nip05 - one row per publisher key present in the kind-32267 (zapstore-app-catalog) catalog. publisher_pubkey is optional: omit it for the full publisher directory (277 rows), pass it for one publisher. Reference data, not a metric.

Nostr Ecosystem Metrics over MCP

Connect your agent

Catalog

Domains

zapstore metrics

zapstore reference data