SolForge

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

Solidity smart contract generator implementing safe coding defaults.

VerifiedSSEWeb executableDeveloper Tools

Overview

AI-generated overview

SolForge is a remote MCP server that generates Solidity smart contracts using safe coding defaults.

What you can do
Generates Solidity smart contract code with safe coding defaults built in, per the registry description. No tool list is published, so the exact operations available to an assistant are not documented. Premium settlement is mentioned in the header description, implying some features are paid.
When to use it
When an assistant needs to draft Solidity smart contracts and you want safe coding defaults applied rather than writing contract code from scratch.
Requirements
A remote SSE endpoint; nothing to install locally. A payment-signature header is described as required for premium settlement, so paid features need a Base64-encoded EIP-3009 TransferWithAuthorization signature.
Before you install
The server asks for a payment-signature header carrying a signed payment authorization; treat it as a spending credential and only send it if you accept the charge. Generated contract code should be reviewed and audited before deployment, since safe defaults are not a guarantee of correctness.

Installation

In SourceWeft

  1. Open SolForge in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Evozim%2Fsol-forge/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "solforge": {
      "type": "sse",
      "url": "https://sol-forge-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.