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 URLhttps://dev.nostrolo.gy/mcp claude mcp add --transport http nostrology https://dev.nostrolo.gy/mcpApplies 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/mcpEdit ~/.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: 300One-off alternative: goose session --with-streamable-http-extension <the endpoint URL above>
gemini mcp add --transport http nostrology https://dev.nostrolo.gy/mcpEdit config.yaml
mcpServers:
- name: Nostrology
type: streamable-http
url: https://dev.nostrolo.gy/mcpHarness 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.