pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for SODAX Builders MCP

Pod holds 19 of 22 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to SODAX Builders MCP.

Most discussed

Migrate Coolify environments (marketing → tech team)

Context

This project is currently deployed on the marketing team's Coolify instance (https://coolify-david.iconblockchain.xyz/), which was set up so the marketing team could manage their own projects. As the first step of handing the Builders MCP over to the tech team, we need to migrate the deployment to the tech team's Coolify instance (https://clf.sodax.com).

Tasks

Migration

  • Deploy on the tech team Coolify environment (clf.sodax.com)
  • Migrate environment variables /

Read the thread · 2026-04-22 · closed · 3 comments

sodax_get_solver_quote: misleading token guidance — chainId-146 oracle lists non-quotable tokens, causing opaque 400s

Summary

The sodax_get_solver_quote MCP tool and its companion sodax_get_solver_oracle give callers (humans and LLMs driving the tool) misleading guidance about which token addresses are quotable. The tool tells you to use any chainId=146 oracle address, but roughly half of the 233 chainId-146 oracle entries are rejected by the quote service with an opaque error that names neither the offending token nor the reason. This sends callers into a dead end on a fully healthy product

Read the thread · 2026-06-15 · closed · 2 comments

docs: refresh glama.ai listing (still shows removed staging URL)

Problem

https://glama.ai/mcp/servers/gosodax/builders-sodax-mcp-server is rendering an older README snapshot. Specifically it still shows the staging deployment URL test-builders-mcp.coolify.iconblockchain.xyz, which was removed from the README in commit cf00bc1 ("fix: remove URLs", merged 2026-05-20 via #36).

Action

Glama.ai is a third-party scraper. glama.json only sets maintainers — it doesn't control resc

Read the thread · 2026-05-21 · closed · 2 comments

Add drift-check workflow + runtime Discord notifier

Context

pnpm check:drift already exists (PR #10) and runs at server boot, printing a summary to stderr. That's a quiet signal — nobody reads container logs proactively. Two related gaps:

  1. CI doesn't run the drift check. Spec can drift between PRs and silently land red-on-deploy. Needs a GitHub Actions workflow that runs on PR/push + a daily cron (so upstream-only drift surfaces even when no one opens a PR).
  2. Prod has no runtime alert. When drift does land on a running server,

Read the thread · 2026-04-24 · closed · 2 comments

Replace axios with native fetch

Context

The MCP server currently ships axios as a runtime dependency and uses it for every outbound HTTP call. Node 18+ has fetch built in (and the project already requires "engines": { "node": ">=18" } in package.json), so axios is adding a ~50 kB dependency and a second HTTP-client mental model for no unique capability we depend on.

Removing it gives us one runtime HTTP shape, fewer dependencies to audit (axios has historically been a common CVE target), and no behavioral loss — we

Read the thread · 2026-04-23 · closed · 2 comments

Create development/staging Coolify environment tracking development branch

Context

We now have a single deployment on the tech-team Coolify (clf.sodax.com) serving builders.sodax.com. To support safe iteration we want to split this into two environments:

  • Production — tracks master, serves builders.sodax.com (the current deployment keeps this role).
  • Staging / development — tracks development, serves a separate subdomain. Used for pre-merge validation and for exercising new changes against real upstream APIs before they go to prod.

Currently `

Read the thread · 2026-04-22 · closed · 2 comments

ci: add docker build step to catch prod-install regressions

Problem

Today's outage (#53) showed that a regression can pass GitHub CI green but break Coolify at deploy time. Root cause was the Dockerfile prod stage using a different install command (`pnpm install --prod --frozen-lockfile`) than CI does (`pnpm install --frozen-lockfile`), and CI never builds the Dockerfile itself.

We don't want to discover Docker-image breakage at deploy time.

Proposed change

Add a `docker-build` job to `.github/workflows/ci.yml` that runs on the same tri

Read the thread · 2026-05-21 · closed · 1 comment

fix: Coolify deploy broken — pnpm install --prod fails on husky prepare script

Symptom

Coolify staging deploy from `development` is failing at the Dockerfile prod stage:

``` Dockerfile:53 RUN pnpm install --prod --frozen-lockfile

builders-sodax-mcp-server@1.3.0 prepare husky sh: 1: husky: not found ELIFECYCLE Command failed. exit code: 1 ```

Root cause

The `prepare` script in `package.json` runs `husky` (for git hook setup). When `--prod` skips devDependencies, husky isn't installed, so the lifecycle hook errors and pnpm aborts the install.

Read the thread · 2026-05-21 · closed · 1 comment

Most recent

docs: refresh mcp.so/server/sodax-builders-mcp listing

Problem

https://mcp.so/server/sodax-builders-mcp/gosodax shows "updated 3 months ago" and reflects an old snapshot of the repo (pre-v1.2 versions, possibly stale README).

Action

mcp.so is a third-party MCP directory; they scrape on their own cadence. Need to:

  1. Check mcp.so for a "request refresh" / "resubmit" affordance.
  2. If none, contact mcp.so (Discord / X / their feedback channel) and request a manual rescan.
  3. As a fallback, pushing a meaningful repo update sometimes nudge

Read the thread · 2026-05-21 · open · 1 comment

chore: sync runtime version from package.json (single source of truth)

Problem

Release-please bumps package.json and CHANGELOG.md on every release, but several other version strings are hardcoded and don't get updated. As of package.json@1.2.0:

  • src/index.ts:39 — new McpServer({ version: "1.1.0" }) — version advertised to MCP clients
  • src/index.ts:164 — /health JSON version field
  • src/index.ts:234 — /api JSON version field
  • server.json:6 — version: "1.1.0" — what mcp-publisher submits to registry.modelcontextprotocol.io

Sym

Read the thread · 2026-05-21 · closed · 1 comment

Integrate discord logging

Add discord webhook integration for the status of server and any significant errors.

Read the thread · 2026-05-19 · open · 0 comments

Integrate Solver and Relay endpoints to the MCP

Currently, MCP only integrates the Gitbook and Backend APIs.

This ticket is intended for solver and relay endpoint integration as well.

Integrate these endpoints for solver:

https://api.sodax.com/v1/intent/oracle

&

curl -sS 'https://api.sodax.com/v1/intent/quote' \
--header 'Content-Type: application/json' \
--data '{
    "token_src": "0xeb0393893b5bf98a50073d6740738b08e575058b",
    "token_dst": "0xaeafa26e43f46cd83efe89b1e57c858eb5685a24",
    "amount": "99800",
    "quote_type":

[Read the thread](https://github.com/gosodax/builders-sodax-mcp-server/issues/37) · 2026-05-19 · closed · 1 comment

### Follow-ups from axios→fetch port (PR #30)

## Context

PR #30 ports the Builders MCP off axios onto native `fetch` via a new `src/services/http.ts` helper. The port is mechanical and merging as-is, but the review surfaced a handful of small follow-ups worth tracking.

## Items

1. **Add unit tests for `src/services/http.ts`.** Cases worth covering:
   - `fetchJson` throws on 4xx/5xx.
   - `fetchJsonOrNull` returns `null` on 404 but throws on other non-2xx.
   - Abort fires when the timeout elapses (and the timer is cleared on success — n

[Read the thread](https://github.com/gosodax/builders-sodax-mcp-server/issues/31) · 2026-05-11 · closed · 1 comment

### Validation report (2026-04-25): Stacks missing from supported_chains (with strengthened evidence) — Builders MCP

---
date: 2026-04-25
status: open
target-repo: gosodax/builders-sodax-mcp-server
cc:
  - "@FezBox"
  - "@fidelVe"
generated-by: pnpm check + targeted MCP probes (test-builders-mcp internal validation workspace)
---

# SODAX Builders MCP — validation report (2026-04-25)

cc: @FezBox @fidelVe — flagging for visibility / triage.

## TL;DR

- **1 high-severity drift to fix**: Stacks is missing from `sodax_get_supported_chains` (and its sibling chain-listing tools) despite having mainnet deployments,

[Read the thread](https://github.com/gosodax/builders-sodax-mcp-server/issues/29) · 2026-04-25 · open · 1 comment

### Sync workflow: 403 on push because actions/checkout extraheader overrides App-token URL

## Context

The first run of the `sync master to development` workflow (after PR #24 merged into master) failed at the **Fast-forward development to master** step:

\`\`\`
remote: Permission to gosodax/builders-sodax-mcp-server.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/gosodax/builders-sodax-mcp-server.git/': The requested URL returned error: 403
\`\`\`

Failed run: https://github.com/gosodax/builders-sodax-mcp-server/actions/runs/24938979693

## Root cause

[Read the thread](https://github.com/gosodax/builders-sodax-mcp-server/issues/26) · 2026-04-25 · closed · 1 comment

### Release automation: migrate from PAT to GitHub App auth

## Context

The release automation introduced in #20 (PR #21) authenticates via a fine-grained PAT (`SYNC_TOKEN`). PATs are tied to a specific user account, which means the workflows break if that user leaves the org or rotates their account, and the audit trail attributes every automated push and PR to a human.

This issue migrates both workflows (`release-please` and `sync-to-development`) to authenticate via a **GitHub App** owned by the `gosodax` org. The App mints a short-lived (~1h) instal

[Read the thread](https://github.com/gosodax/builders-sodax-mcp-server/issues/23) · 2026-04-25 · closed · 1 comment

### Security: triage 5 high + 14 medium Dependabot alerts

## Context

GitHub's Dependabot reports 21 open vulnerabilities on `development`: 5 high, 14 medium, 2 low. Most importantly, one of the high alerts is in a **direct** dependency that affects a security-critical feature (rate limiting on `/mcp`). The others are transitive but worth addressing alongside in one sweep since we'll be touching the lockfile either way.

See: https://github.com/gosodax/builders-sodax-mcp-server/security/dependabot

## High-severity alerts (known)

| Package | Advisory 

[Read the thread](https://github.com/gosodax/builders-sodax-mcp-server/issues/19) · 2026-04-24 · closed · 1 comment

### Security: scrub internal Coolify URLs from public docs + guardrail .claude/

## Context

The repo is public. A security scan surfaced internal infrastructure identifiers in `README.md` that weren't meant for public indexing:

- `README.md:172` names `clf.sodax.com` — the internal Coolify host.
- `README.md:177` exposes the full staging URL: `https://test-builders-mcp.coolify.iconblockchain.xyz`. This reveals the DNS pattern (`*.iconblockchain.xyz`) and the Coolify tenant structure.
- `README.md:199` — "Railway/Coolify" section heading (minor — just names the tooling).

I

[Read the thread](https://github.com/gosodax/builders-sodax-mcp-server/issues/18) · 2026-04-24 · closed · 1 comment

### Add minimal test harness (vitest) to replace CI test placeholder

## Context

The CI standards compliance issue lands a `pnpm test` script as a placeholder (`echo … && exit 0`) so that CI goes green while the rest of the baseline is in place. That placeholder doesn't actually gate anything. This issue replaces it with a minimal real test harness, prioritizing unit coverage of the drift-check logic since that's the part most likely to rot silently.

## Scope

- Add `vitest` and `@vitest/coverage-v8` as dev deps.
- `vitest.config.ts` (minimal): node environment,

[Read the thread](https://github.com/gosodax/builders-sodax-mcp-server/issues/17) · 2026-04-24 · closed · 1 comment

The remaining reports are on [the project's issue tracker](https://github.com/gosodax/builders-sodax-mcp-server/issues).