# sol-forge-mcp

> sol-forge-mcp is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.03/call, status unknown (last checked 2026-10-10).

Processes Solana-focused forge/smart-contract operations via a managed MCP endpoint

## Facts

- Endpoint: POST https://api.m2mcent.com/sol-forge-mcp/api/process?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sol-forge-mcp-ee0d264b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_t_JpB0B7di5QJU4QXtKuq

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability sol-forge-mcp-ee0d264b -d '<json body>'
```

Example prompt: Run a sol-forge processing job with my Solana contract build payload and return the result.

## When to prefer this

Choose this endpoint when you need to programmatically submit Solana forge or smart contract processing jobs through a managed MCP interface and are willing to pay per call in USDC via the x402 protocol. Best suited for agentic workflows that need on-demand Solana program compilation or deployment without managing infrastructure.

## Known failure modes

- Invalid or malformed data string returns a 400-level error
- Payment not included or insufficient USDC triggers a 402 Payment Required response
- Solana network errors or forge pipeline failures return a 500-level error
- Empty data field causes processing rejection
- Unsupported instruction format leads to an unprocessable entity error

## How this service works

The premier global index of 1,069 monetized MCP nodes across 205 specialized subdomains. Gasless USDC runtime settlements via x402 V2 Spec on Base L2. Save 95% token context.

## Output

Returns processed output from the sol-forge MCP pipeline, which may include compiled artifacts, transaction results, deployment confirmations, or error details depending on the submitted data payload.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sol-forge-mcp-ee0d264b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.m2mcent.com](https://www.zero.xyz/host/api.m2mcent.com/llms.txt)