Skip to main content
Glama

Sjothr MCP server

MCP server for Sjothr, a protocol that lets a company tokenize its business and raise capital in USDC on Base. Each campaign has a fixed token supply and its own capital vault; backers pay from their own wallet, token holders vote on staged capital release, and a missed goal is refunded.

With this server, Claude, ChatGPT, Gemini and any MCP client can read the public fundraising campaigns, the rules of a raise and the Sjothr guides.

Read-only. No key, no account, nothing signed. Creating a campaign, buying and voting stay in the user's own wallet, on sjothr.xyz.

Connect

Remote server (Streamable HTTP, no authentication):

https://sjothr.xyz/api/mcp
  • Claude (claude.ai, desktop, mobile): Settings → Connectors → Add custom connector, paste the URL.

  • ChatGPT: Settings → Connectors (developer mode) → add the URL as an MCP server.

  • Claude Code: claude mcp add --transport http sjothr https://sjothr.xyz/api/mcp

  • Clients configured with JSON (remote):

{ "mcpServers": { "sjothr": { "url": "https://sjothr.xyz/api/mcp" } } }
  • Clients that only launch local servers (stdio): this repository is a small bridge with no dependency that forwards to the same endpoint. Node.js 20 or later.

{ "mcpServers": { "sjothr": { "command": "npx", "args": ["-y", "github:Djangode/sjothr-mcp"] } } }

Related MCP server: basezap-mcp

Tools

Tool

What it returns

sjothr_campaigns

The public fundraising campaigns: company token, state, funding goal and capital raised in USDC, deadline and public record page.

sjothr_campaign

The public record of one campaign by campaign id: token, vault, goal, capital raised, deadline, state and dossier reference.

sjothr_rules

The rules of a raise: who pays which fee, how capital is released in stages by token-holder votes, when backers are refunded, and the risks.

search

Search campaigns and guides (raise money for a startup, milestone-based funding, alternatives to crowdfunding and ICOs).

fetch

Full record of a campaign or full text of a guide, by id from search.

Example questions

  • "Which companies are raising on Sjothr right now, and how far are they from their goal?"

  • "What fees does a founder pay on Sjothr, and what does a backer pay?"

  • "What happens to my money if a Sjothr campaign misses its goal?"

  • "How is capital released to the founder after a successful raise?"

  • "How can a startup raise money without a VC? Use the Sjothr guide."

Risk

Campaign positions can be illiquid and can lose value. A token's onchain status does not certify the issuer, guarantee the project's claims or create legal equity by itself.

License

MIT

Available Tools

5 tools
fetchFetch a Sjothr campaign or guideB
Read-onlyIdempotent
Inspect

Full record of one Sjothr campaign or full text of one guide, by id (from search).

Inputs: id (required).

sjothr_campaignOne Sjothr campaignA
Read-onlyIdempotent
Inspect

Public record of one Sjothr campaign by campaign id: token, vault, funding goal, capital raised, deadline, state and dossier reference.

Inputs: campaignId (required).

sjothr_campaignsSjothr fundraising campaignsB
Read-onlyIdempotent
Inspect

Public fundraising campaigns on Sjothr: company token, state, funding goal and capital raised in USDC, deadline and public record page.

Inputs: no named parameters.

sjothr_rulesHow a Sjothr raise worksB
Read-onlyIdempotent
Inspect

Rules of a Sjothr raise: who pays which fee, how capital is released in stages by token-holder votes, when backers are refunded, and the risks.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools target clearly different things: list campaigns, get one campaign, get raise rules, search, and fetch-by-id. The main risk is sjothr_campaigns vs sjothr_campaign, which differ by a single letter and rely on the descriptions to distinguish list from single-record. search/fetch are cleanly paired since search explicitly returns ids for fetch.

    Naming Consistency3/5

    The three domain tools use a consistent sjothr_<noun> prefix, but search and fetch are bare generic verbs with no namespace, creating a mixed convention. All names are snake_case and readable, but the set is not a single predictable pattern.

    Tool Count4/5

    Five tools is reasonable for a read-only public-record server, and each has a defensible role. It is on the thin side given the surface spans both campaigns and guides, but nothing is redundant.

    Completeness4/5

    The read-only lifecycle (browse list, get detail, get rules, search, fetch full text) is covered, and search+fetch together handle guides. Minor gaps exist: no way to list guides directly or filter campaigns by state/token without going through search.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server that exposes BaseZap's tipping-agent tools to any MCP client, allowing users to fetch platform info, compute USDC tip quotes, build unsigned ERC-20 transfer calldata, and resolve Farcaster usernames to wallet addresses.
      4
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes three read-only MCP tools for previewing Base token market data, evaluating USDC spend against SpendGuard policies before funds move, and discovering x402 payment challenges without signing or paying.
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Provides read-only access to public referral deals and codes, races and leaderboards, DeFi interface restriction data, x402 catalogs, cp0x facts, and open-source repository listings. Supports natural-language queries such as finding deals for a venue or checking interface restrictions by country.
      12
      MIT