@blurt-blockchain/blurt-mcp-server 0.4.0

package/docs/deployment.md

@@ -0,0 +1,102 @@
+# Deployment guide
+
+This guide covers deployment concerns that belong around the official Blurt MCP server, not inside it.
+The application stays a small neutral MCP component: it exposes `/mcp`, `/healthz`, and `/readyz`; TLS,
+public rate limiting, bot protection, and global abuse controls should normally live in infrastructure.
+
+## HTTP surface
+
+| Path | Method | Purpose |
+| --- | --- | --- |
+| `/mcp` | `POST` | Streamable HTTP MCP endpoint. Stateless; no session id. |
+| `/mcp` | `GET`, `DELETE` | Returns `405`; not supported in stateless mode. |
+| `/healthz` | `GET` | Cheap process liveness check. Does not touch upstream RPC. |
+| `/readyz` | `GET` | Cheap readiness check with non-sensitive RPC configuration/readiness counters. |
+
+The app has a `256kb` JSON request-body limit. MCP requests are small; large data is returned in
+responses, not posted by clients.
+
+## Recommended topology
+
+```text
+Internet / client
+  -> reverse proxy / ingress / CDN
+  -> blurt-mcp-server HTTP process
+  -> Blurt RPC nodes, Nexus/Bridge API, price feed
+```
+
+The public hosted endpoint should stay anonymous and read-only. Do not configure `BLURT_POSTING_KEY` on
+a public HTTP deployment. HTTP signing is available only through the deliberately unsafe trusted-deployment
+override documented in [write operations](./write-operations.md#advanced-unsafe-http-signing-for-trusted-deployments).
+
+## Caddy example
+
+```caddyfile
+mcp.example.org {
+  encode zstd gzip
+
+  @mcp method POST
+  @mcp path /mcp
+  reverse_proxy @mcp 127.0.0.1:3000
+
+  @health path /healthz /readyz
+  reverse_proxy @health 127.0.0.1:3000
+
+  # Keep request bodies small; MCP JSON-RPC requests are tiny.
+  request_body {
+    max_size 256KB
+  }
+
+  # Caddy rate limits require a plugin/module. If unavailable, apply rate limits
+  # at your CDN, load balancer, firewall, or hosting platform instead.
+}
+```
+
+## nginx example
+
+```nginx
+limit_req_zone $binary_remote_addr zone=blurt_mcp:10m rate=60r/m;
+
+server {
+  listen 443 ssl http2;
+  server_name mcp.example.org;
+
+  client_max_body_size 256k;
+
+  location = /mcp {
+    limit_req zone=blurt_mcp burst=30 nodelay;
+    proxy_pass http://127.0.0.1:3000;
+    proxy_http_version 1.1;
+    proxy_set_header Host $host;
+    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+    proxy_set_header X-Forwarded-Proto $scheme;
+  }
+
+  location = /healthz {
+    proxy_pass http://127.0.0.1:3000;
+  }
+
+  location = /readyz {
+    proxy_pass http://127.0.0.1:3000;
+  }
+}
+```
+
+Tune the rate-limit numbers for your own traffic and abuse profile. The example is intentionally coarse;
+production limits should be validated against real usage.
+
+## Production environment checklist
+
+- `NODE_ENV=production` for JSON logs.
+- `LOG_LEVEL=info` unless actively debugging.
+- Multiple `BLURT_RPC_URLS` so the node checker can avoid unhealthy nodes.
+- Reverse proxy terminates TLS and applies public rate limits.
+- `/healthz` and `/readyz` are routed to monitoring.
+- No posting key on public HTTP deployments.
+- Secrets for stdio/private deployments are kept outside the repository.
+
+## What is intentionally deferred
+
+The app does not ship a full OpenTelemetry stack, built-in distributed rate limiter, WAF, dashboard,
+alerting setup, or generic response cache. Those belong to deployment infrastructure until concrete
+hosting requirements justify pulling a small part into the server itself.

package/docs/development.md

@@ -0,0 +1,51 @@
+# Development
+
+See [CONTRIBUTING.md](../CONTRIBUTING.md) for how to propose changes, and
+[architecture.md](./architecture.md) for the design and project layout.
+
+## Testing
+
+Tests use the built-in Node test runner (`node:test`) executed through `tsx`.
+
+```bash
+npm test          # offline: URI/search routing, RPC resilience, write gating, operational endpoints
+npm run test:live # live (in-memory): every tool against a real Blurt RPC node
+npm run test:http # live (HTTP E2E): every tool over the real Streamable HTTP transport
+npm run smoke:http # optional deployment smoke against MCP_URL or localhost:3000/mcp
+npm run smoke:package # optional npm package/tarball smoke after build
+npm run pack:check # build + npm pack --dry-run
+npm run test:all  # everything
+```
+
+Three layers, by design:
+
+- **Offline** (`test/uri`, `test/search`, `test/resilience`, `test/write`, `test/ops`) — deterministic, no
+  external network. Includes a resilience test that points the client at an unresponsive local mock to
+  assert the RPC transport degrades gracefully (guards against the dblurt transport regression),
+  write-gating tests (no write tools without a write context, capability profile resolution, default HTTP
+  read-only behavior and the explicit unsafe HTTP override), and operational endpoint tests (`/healthz`,
+  `/readyz`, request logging), and package-readiness assertions (scoped name, license, bins, files). Runs in CI on every push.
+- **Live, in-memory** (`test/live`) — connects an in-memory MCP client to the server and calls every
+  tool against `BLURT_RPC_URLS`. Validates tool logic and `@beblurt/dblurt` integration.
+- **Live, HTTP E2E** (`test/http`) — boots the real Express app on an ephemeral port and drives it
+  through the actual Streamable HTTP transport + shared client. This is the path the in-memory client
+  does not exercise, where transport/client bugs surface. Run after dependency or transport changes.
+
+## Releasing
+
+Versioning follows [Semantic Versioning](https://semver.org) and the changelog is generated from
+[Conventional Commits](https://www.conventionalcommits.org) using
+[`commit-and-tag-version`](https://github.com/absolute-version/commit-and-tag-version).
+
+```bash
+npm run release:dry     # preview the bump + changelog without writing anything
+npm run release         # auto-bump from commits, update CHANGELOG.md, create an annotated tag
+npm run release:minor   # or force a specific bump
+npm run release:major
+
+git push --follow-tags origin main
+```
+
+`feat:` bumps the minor, `fix:`/`perf:` bump the patch, and a `BREAKING CHANGE:` footer bumps the major.
+The package is prepared for npm as `@blurt-blockchain/blurt-mcp-server`, but publication remains a
+separate maintainer-authorized action. See [release/provenance notes](./release-provenance.md).

package/docs/install-snippets.md

@@ -0,0 +1,236 @@
+# Install snippets
+
+Copy-paste examples for the official Blurt MCP package and hosted endpoint.
+
+The hosted endpoint is anonymous and read-only:
+
+```text
+https://mcp.blurt-blockchain.com/mcp
+```
+
+The npm package identity is:
+
+```text
+@blurt-blockchain/blurt-mcp-server
+```
+
+## Hosted remote HTTP
+
+Use this when your client supports remote MCP / Streamable HTTP:
+
+```text
+https://mcp.blurt-blockchain.com/mcp
+```
+
+No private key is required and no write tools are exposed by the public hosted endpoint.
+
+## Local stdio via npm package
+
+Use this when your client launches a local MCP server process:
+
+```bash
+npx -y -p @blurt-blockchain/blurt-mcp-server blurt-mcp-stdio
+```
+
+If your client expects command/args separately, use:
+
+```json
+{
+  "command": "npx",
+  "args": ["-y", "-p", "@blurt-blockchain/blurt-mcp-server", "blurt-mcp-stdio"]
+}
+```
+
+## Local HTTP via npm package
+
+Use this when you want to self-host the HTTP endpoint:
+
+```bash
+PORT=3000 npx -y -p @blurt-blockchain/blurt-mcp-server blurt-mcp-server
+```
+
+Then point remote-capable clients at:
+
+```text
+http://localhost:3000/mcp
+```
+
+For production HTTP deployments, see [deployment.md](./deployment.md).
+
+## Bridge stdio-only clients to hosted HTTP
+
+If a desktop client only supports stdio but you want the hosted read-only endpoint, bridge with
+`mcp-remote`:
+
+```json
+{
+  "command": "npx",
+  "args": ["-y", "mcp-remote", "https://mcp.blurt-blockchain.com/mcp"]
+}
+```
+
+## Tier-1 client snippets
+
+### Claude Desktop
+
+Hosted endpoint through `mcp-remote`:
+
+```json
+{
+  "mcpServers": {
+    "blurt": {
+      "command": "npx",
+      "args": ["-y", "mcp-remote", "https://mcp.blurt-blockchain.com/mcp"]
+    }
+  }
+}
+```
+
+Fully local stdio package:
+
+```json
+{
+  "mcpServers": {
+    "blurt": {
+      "command": "npx",
+      "args": ["-y", "-p", "@blurt-blockchain/blurt-mcp-server", "blurt-mcp-stdio"]
+    }
+  }
+}
+```
+
+### Claude Code
+
+Remote HTTP:
+
+```bash
+claude mcp add --transport http blurt https://mcp.blurt-blockchain.com/mcp
+```
+
+Local stdio:
+
+```bash
+claude mcp add blurt -- npx -y -p @blurt-blockchain/blurt-mcp-server blurt-mcp-stdio
+```
+
+### OpenAI Codex
+
+Remote HTTP in `~/.codex/config.toml`:
+
+```toml
+[mcp_servers.blurt]
+url = "https://mcp.blurt-blockchain.com/mcp"
+```
+
+Local stdio:
+
+```toml
+[mcp_servers.blurt]
+command = "npx"
+args = ["-y", "-p", "@blurt-blockchain/blurt-mcp-server", "blurt-mcp-stdio"]
+```
+
+### VS Code / GitHub Copilot agent
+
+`.vscode/mcp.json` using hosted HTTP:
+
+```json
+{
+  "servers": {
+    "blurt": {
+      "type": "http",
+      "url": "https://mcp.blurt-blockchain.com/mcp"
+    }
+  }
+}
+```
+
+Local stdio:
+
+```json
+{
+  "servers": {
+    "blurt": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "-p", "@blurt-blockchain/blurt-mcp-server", "blurt-mcp-stdio"]
+    }
+  }
+}
+```
+
+### Cursor
+
+`.cursor/mcp.json` using hosted HTTP:
+
+```json
+{
+  "mcpServers": {
+    "blurt": {
+      "url": "https://mcp.blurt-blockchain.com/mcp"
+    }
+  }
+}
+```
+
+Local stdio:
+
+```json
+{
+  "mcpServers": {
+    "blurt": {
+      "command": "npx",
+      "args": ["-y", "-p", "@blurt-blockchain/blurt-mcp-server", "blurt-mcp-stdio"]
+    }
+  }
+}
+```
+
+### Gemini CLI
+
+Hosted HTTP:
+
+```bash
+gemini mcp add blurt https://mcp.blurt-blockchain.com/mcp
+```
+
+Local stdio:
+
+```bash
+gemini mcp add blurt -- npx -y -p @blurt-blockchain/blurt-mcp-server blurt-mcp-stdio
+```
+
+### Hermes Agent
+
+`~/.hermes/config.yaml` example for hosted HTTP:
+
+```yaml
+mcp_servers:
+  blurt:
+    url: https://mcp.blurt-blockchain.com/mcp
+```
+
+Local stdio:
+
+```yaml
+mcp_servers:
+  blurt:
+    command: npx
+    args: ["-y", "-p", "@blurt-blockchain/blurt-mcp-server", "blurt-mcp-stdio"]
+```
+
+### Open WebUI / LibreChat
+
+Use the hosted Streamable HTTP endpoint where the admin UI/config accepts remote MCP servers:
+
+```text
+https://mcp.blurt-blockchain.com/mcp
+```
+
+For LibreChat-style YAML configurations, the exact schema depends on the deployed version; prefer the
+client's current MCP documentation and use the hosted URL above or a self-hosted `/mcp` URL.
+
+## Write tools
+
+Write tools are not exposed by the public hosted endpoint. For local signing, configure the stdio package
+entrypoint and follow [write operations](./write-operations.md). Use a posting key only.

package/docs/load-testing.md

@@ -0,0 +1,51 @@
+# HTTP smoke and lightweight load checks
+
+The repository includes a small HTTP smoke script for deployment validation. It is intentionally light:
+it checks MCP connectivity and repeated `tools/list` calls without turning normal CI into a public-load
+test against upstream Blurt services.
+
+## Run against a local server
+
+Start the server:
+
+```bash
+npm run build
+npm start
+```
+
+In another shell:
+
+```bash
+npm run smoke:http
+```
+
+By default this targets `http://localhost:3000/mcp` and runs five `tools/list` iterations.
+
+## Run against a hosted endpoint
+
+```bash
+MCP_URL=https://mcp.example.org/mcp MCP_SMOKE_ITERATIONS=10 npm run smoke:http
+```
+
+## Include one representative read
+
+```bash
+MCP_URL=https://mcp.example.org/mcp MCP_SMOKE_READ=1 npm run smoke:http
+```
+
+This calls `get-chain-status` once after the `tools/list` loop. Use it sparingly on public endpoints;
+it may touch upstream RPC/price dependencies.
+
+## Output
+
+The script emits JSON lines, for example:
+
+```json
+{"event":"tools_list","iteration":1,"tool_count":25,"duration_ms":42}
+{"event":"done","url":"http://localhost:3000/mcp","iterations":5,"include_read":false,"total_duration_ms":260}
+```
+
+## What this is not
+
+This is not a full benchmark, distributed load test, or SLO proof. Heavy load testing should be run from
+a controlled staging environment with permission and with upstream RPC impact in mind.

package/docs/operations.md

@@ -0,0 +1,56 @@
+# Public endpoint operations notes
+
+These notes describe how to operate a public read-only Blurt MCP endpoint. They are not a hard SLO or an
+on-call contract; those should be finalized only when hosting ownership, alerting, and maintenance
+responsibilities are explicit.
+
+## Service posture
+
+The public endpoint is a best-effort, anonymous, read-only MCP service for public Blurt data. It should
+not hold private keys and should not expose write tools. Write/signing deployments are private operator
+responsibility.
+
+## Dependencies
+
+| Dependency | Used for | Degradation behavior |
+| --- | --- | --- |
+| Blurt Layer 1 RPC nodes | accounts, balances, history, witnesses, votes, broadcasts in private write mode | Read tools depending on L1 may fail or become slow. Node checker keeps the client on healthy configured nodes when possible. |
+| Nexus / Bridge API | ranked posts, account posts, communities, discussions and social L2 views | Nexus-backed tools may fail while L1 tools continue. |
+| Price feed (`BLURT_PRICE_URL`) | BLURT/USD and BTC values | Price fields are best-effort; on-chain fields should still be returned where possible. |
+| Reverse proxy / ingress | TLS, public rate limiting, body-size enforcement, host/origin filtering | Misconfiguration can expose the app directly or amplify abuse. |
+
+## Health checks
+
+- `/healthz`: process liveness. Use for container/process checks.
+- `/readyz`: cheap readiness. Use for load balancers and monitoring. It reports non-sensitive RPC
+  counters and does not perform a heavy live RPC call on every request.
+
+## Logging
+
+In production (`NODE_ENV=production`) logs are JSON lines on `stderr`. The HTTP app logs method, path,
+status and duration for requests, without request bodies or secrets. Collect logs at the process manager,
+container runtime, or platform layer.
+
+## Incident examples
+
+| Symptom | Likely area | First checks |
+| --- | --- | --- |
+| `/healthz` fails | process/container | process manager, container status, recent deploy logs |
+| `/healthz` passes but `/readyz` fails | app readiness/config | env vars, configured RPC URL count, startup logs |
+| MCP read tools slow/failing | upstream RPC or Nexus | node checker logs, configured RPC nodes, Nexus status |
+| Price fields null | price feed | `BLURT_PRICE_URL`, external feed availability |
+| High 4xx/429 at proxy | client misuse/abuse | reverse-proxy logs and rate-limit settings |
+| High 5xx from app | app/runtime/upstream errors | app logs, recent commits, dependency status |
+
+## Rollback and maintenance
+
+- Keep deployments reproducible from a Git commit and package lockfile.
+- Prefer blue/green or rolling deployment where the platform supports it.
+- Validate `/healthz`, `/readyz`, and `npm run smoke:http` after deployment.
+- Roll back to the previous known-good commit if the MCP transport or core read tools regress.
+
+## SLO candidate, not a guarantee
+
+A future official production service may define uptime and latency SLOs. Until monitoring, alerting,
+incident ownership, and hosting budget are formalized, treat this document as operational guidance rather
+than a public availability guarantee.

package/docs/release-provenance.md

@@ -0,0 +1,63 @@
+# Release and provenance notes
+
+This project can be prepared for npm publication from the repository, but publication remains a separate
+maintainer-authorized action. Do not publish, tag, or bump versions as part of ordinary feature work unless
+the maintainer explicitly requests a release.
+
+## Package identity
+
+Official npm package name:
+
+```text
+@blurt-blockchain/blurt-mcp-server
+```
+
+Runtime bins after installation:
+
+```text
+blurt-mcp-server
+blurt-mcp-stdio
+```
+
+## Pre-publish checks
+
+Run the normal validation suite first:
+
+```bash
+npm run check:secrets
+npm run docs:check
+npm run typecheck
+npm test
+npm run build
+npm run test:http
+npm run test:live
+```
+
+Then verify package contents and bin metadata:
+
+```bash
+npm run pack:check
+npm run smoke:package
+```
+
+`pack:check` is dry-run only. `smoke:package` creates a temporary tarball, verifies expected runtime/docs
+files and bin shebangs, then removes the tarball.
+
+## Publication
+
+Publication is intentionally not automated in package scripts. When a maintainer approves a release, decide
+first:
+
+- version bump and changelog impact;
+- Git tag timing;
+- npm account / organization access;
+- OTP requirements;
+- whether npm provenance is supported by the chosen CI path.
+
+Then publish from a clean, validated commit using the selected release process.
+
+## Provenance / signing
+
+npm provenance or signing should be enabled only when the real release pipeline supports it end-to-end.
+The repository currently prepares package metadata and pack validation, but does not pretend to produce a
+provenance attestation. This avoids false security claims.

package/docs/tools.generated.md

@@ -0,0 +1,89 @@
+<!-- Generated from src/contracts/toolRegistry.ts. Do not edit by hand. Run npm run docs:tools. -->
+
+# Generated tool contract reference
+
+This file is generated from the Blurt MCP tool registry. It is the contract index for v1-candidate tool metadata: tool name, safety class, data source, cache hint, stability and short description.
+
+Every tool result follows the standard structured-content envelope:
+
+```ts
+{
+  data: unknown,
+  meta: {
+    contract: "blurt-mcp.tool-result.v1",
+    tool: string,
+    sources: Array<"layer1" | "nexus" | "external" | "mixed" | "mcp">,
+    retrieved_at: string,
+    freshness: { cache: "none" | "short" | "medium" | "external", ttl_seconds: number | null },
+    confidence: "high" | "medium" | "low",
+    caveats: string[]
+  }
+}
+```
+
+Tool-specific `data` schemas remain intentionally broad during the P1 foundation step and will be tightened as the v1 contract matures.
+
+| Tool | Title | Safety | Source | Cache | Stability | Description |
+| --- | --- | --- | --- | --- | --- | --- |
+| `blurt-claim-rewards` | Claim rewards locally | write-local | layer1 | none | v1-candidate | Claim pending rewards using the configured local posting key. |
+| `blurt-comment` | Comment locally | write-local | layer1 | none | v1-candidate | Broadcast a local posting-key comment/reply operation. |
+| `blurt-follow` | Follow locally | write-local | layer1 | none | v1-candidate | Broadcast a local posting-key follow/unfollow custom_json. |
+| `blurt-mute` | Mute locally | write-local | layer1 | none | v1-candidate | Broadcast a local posting-key mute/unmute custom_json. |
+| `blurt-post` | Post locally | write-local | layer1 | none | v1-candidate | Broadcast a local posting-key top-level post operation. |
+| `blurt-read-notifications` | Mark notifications read locally | write-local | layer1 | none | v1-candidate | Broadcast a local posting-key notification read marker. |
+| `blurt-reblog` | Reblog locally | write-local | layer1 | none | v1-candidate | Broadcast a local posting-key reblog/undo custom_json. |
+| `blurt-subscribe-community` | Subscribe to community locally | write-local | layer1 | none | v1-candidate | Broadcast a local posting-key community subscription custom_json. |
+| `blurt-upvote` | Upvote locally | write-local | layer1 | none | v1-candidate | Broadcast a local posting-key vote operation. |
+| `compare-accounts` | Compare accounts | read | mixed | short | v1-candidate | Side-by-side account metrics for stake, reach, output and rewards. |
+| `fetch` | Fetch Blurt resource | read | mixed | short | v1-candidate | Resolve a blurt:// URI or shorthand id to raw JSON. |
+| `get-account` | Get account profile and wallet summary | read | mixed | short | v1-candidate | Structured account identity, wallet, stake, witness vote count and rewards summary. |
+| `get-account-history` | Get raw account operation history | read | layer1 | none | v1-candidate | Recent Layer 1 operations for an account, optionally filtered by operation type. |
+| `get-account-notifications` | Get notifications | read | nexus | short | v1-candidate | Nexus notifications and unread count for an account. |
+| `get-account-posts` | Get account-related posts | read | nexus | short | v1-candidate | Nexus account posts, blog, comments, replies, feed or payout items. |
+| `get-account-relationships` | Get social relationship counts | read | layer1 | short | v1-candidate | Follower/following counts and samples for an account. |
+| `get-account-subscriptions` | Get community subscriptions | read | nexus | medium | v1-candidate | Communities an account is subscribed to and its role in them. |
+| `get-account-witness-votes` | Get account witness votes | read | layer1 | short | v1-candidate | Witnesses supported by an account and any witness proxy. |
+| `get-blurt-price` | Get BLURT market price | read | external | external | v1-candidate | Current BLURT USD/BTC price from the configured public price feed. |
+| `get-chain-status` | Get chain and market status | read | mixed | short | v1-candidate | Network, supply, reward and market dashboard for Blurt. |
+| `get-community` | Get community details | read | nexus | medium | v1-candidate | Nexus details for a single Blurt community. |
+| `get-delegations` | Get outgoing delegations | read | layer1 | short | v1-candidate | Outgoing Blurt Power delegations for an account. |
+| `get-pending-rewards` | Get unclaimed rewards | read | mixed | short | v1-candidate | Pending reward balances currently claimable by an account. |
+| `get-post` | Get post or discussion | read | nexus | short | v1-candidate | Nexus post summary or full discussion tree for an author/permlink. |
+| `get-post-reblogs` | Get post reblogs | read | layer1 | short | v1-candidate | Accounts that reblogged a post. |
+| `get-post-votes` | Get post votes | read | layer1 | short | v1-candidate | Layer 1 active votes on a post/comment ranked by rshares. |
+| `get-publications` | Get ranked publications | read | nexus | short | v1-candidate | Nexus ranked posts for discovery by sort/tag. |
+| `get-referrals` | Get referred accounts | read | nexus | medium | v1-candidate | beBlurt referral accounts and total count for a referrer. |
+| `get-vote-value` | Estimate account vote value | read | mixed | short | v1-candidate | Estimated current upvote value for an account at a given weight. |
+| `get-witness` | Get witness health | read | layer1 | short | v1-candidate | Layer 1 witness details and health summary for one account. |
+| `list-communities` | List communities | read | nexus | medium | v1-candidate | Nexus community discovery by rank, newness or subscribers. |
+| `list-witnesses` | List witnesses | read | layer1 | short | v1-candidate | Layer 1 witness ranking and production metadata. |
+| `lookup-accounts` | Lookup account names | read | layer1 | medium | v1-candidate | Alphabetical account-name autocomplete by prefix. |
+| `search` | Search Blurt resources | read | mcp | none | v1-candidate | Map a free-form query to blurt:// resource links. |
+
+## Read-tool example prompts
+
+- `compare-accounts`: Compare @nalexadre, @megadrive and @beblurt.
+- `fetch`: Fetch blurt://account/nalexadre.
+- `get-account`: Show me @nalexadre's Blurt account and wallet.
+- `get-account-history`: Show the latest 10 transfer operations for @beblurt.
+- `get-account-notifications`: Do I have recent Blurt notifications?
+- `get-account-posts`: Show @nalexadre's latest posts.
+- `get-account-relationships`: Who follows @nalexadre?
+- `get-account-subscriptions`: Which communities does @nalexadre belong to?
+- `get-account-witness-votes`: Which witnesses does @nalexadre vote for?
+- `get-blurt-price`: What is the current BLURT price?
+- `get-chain-status`: Give me a Blurt network health snapshot.
+- `get-community`: Show details for community blurt-101010.
+- `get-delegations`: Who does @beblurt delegate to?
+- `get-pending-rewards`: How much can @nalexadre claim right now?
+- `get-post`: Open nalexadre/how-ai-can-help-curation-on-blurt-1759501073717.
+- `get-post-reblogs`: Who reblogged this post?
+- `get-post-votes`: Who were the biggest voters on this post?
+- `get-publications`: What is trending under #blurt?
+- `get-referrals`: How many accounts did @beblurt refer?
+- `get-vote-value`: How much is a 100% vote from @nalexadre worth?
+- `get-witness`: Is @nalexadre's witness healthy?
+- `list-communities`: What are the most popular Blurt communities?
+- `list-witnesses`: List the top 10 Blurt witnesses.
+- `lookup-accounts`: Find accounts starting with nale.
+- `search`: Search for @nalexadre or posts:blurt.