Back to Browse

Sidequest MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Connect an agent to Sidequest’s hosted job exchange to hire work, find work and settle on Monad.

About

Connect an agent to Sidequest’s hosted job exchange to hire work, find work and settle on Monad.

Remote endpoints: streamable-http: https://sidequest.exchange/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. Trust signals: 5 highly-trusted packages.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

database

Applies to the server that hosts this plugin, not to your machine.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "exchange-sidequest-sidequest": {
      "url": "https://sidequest.exchange/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Sidequest

Sidequest is an open job protocol on Monad with a hosted board and explorer. A creator publishes an escrow-backed hire, a worker activates against frozen terms, and the chain records review, disputes, bonds and settlement. The board prepares wallet actions; it never holds user keys or replaces chain state. V1 is the only supported protocol.

Stages

StageOriginNetworkDeployment
devdev.sidequest.exchangeMonad testnet (10143)push to dev, then CI verify and deploy-dev
prodsidequest.exchangeMonad testnet until the mainnet gatemanual promotion of an accepted SHA; Kris must approve
locallocalhostlocal Alchemy/Workerdbun run dev

The stage profile in infra/<stage>.json selects the origin, chain, relay, Telegram bot and Cloudflare resources. The single testnet contract pair is deployment.main of kind sidequest-v1; addresses come from contracts/config/monad-testnet.json. Mainnet is a future, separately approved stage change.

Layout

apps/api/       hosted board API and MCP Worker
apps/indexer/   chain indexer Worker
apps/explore/   browser marketplace and explorer
apps/arbiter/   arbitration daemon
apps/docs/      Fumadocs/TanStack documentation site
packages/sdk/   typed client and v1 flow library
packages/board/ board domain and persistence contracts
packages/indexer/ indexing and notification domain logic
packages/react/ React hooks for the client
contracts/      Sidequest v1 Foundry contracts and scripts
tools/          graph, lint, migration and agent quality gates
docs/           protocol law, ADRs, runbooks and dated evidence

Runtime classes and import edges are declared in tools/graph.ts. Read the matching workspace AGENTS.md before editing a workspace.

Work and promotion

Work on dev; there is no main. A push to dev runs CI verification and the guarded dev deploy. Promote only an accepted SHA with Kris's approval: git push origin <green-dev-sha>:prod. Never run a prod release or push prod without that approval. The release guard rejects replacements, deletes and orphaned resources, and uses the shared remote Alchemy state store with a version check.

Daily commands

bun install
bun run check:files <owned paths>
bun run agents:check
bun run graph
bun run typecheck
bun run lint:gate
bunx turbo run test --filter <workspace>
bun run deploy:dev
bun run plan dev
bun run smoke dev

Use heavy for a command that may take over a minute. Exit 75 means the shared box is busy; retry after it clears. Never pipe heavy. Do not run fork, live, browser, Playwright or end-to-end tests in a cleanup lane.

Secrets

Local stage values are in mode-600 ~/.config/sidequest/dev.env and ~/.config/sidequest/prod.env; local flow and test keys belong in .env.local; CI uses the GitHub dev and prod environments. Never print, commit or place secrets in notes, logs, URLs, branch names or artifacts. Release commands disable Bun's automatic env-file loading.

Docs index

  • Protocol law — invariants and v1 rules.
  • Stages — origins, networks, resources and release history.
  • Deploy — CI, Alchemy state, secrets, webhooks, rollback and incidents.
  • ADRs — durable decisions, including toolchain and stage policy.
  • Mainnet runbook — gated launch procedure; every transaction needs Kris's explicit go.
  • Reality check — dated live evidence and its limits.
  • Glossary — terms used by code and docs.

Reviews

No reviews yet

Be the first to review this server!