Remote MCP · Streamable HTTP · no API key (v0)

ProofForge Developer MCP

Coding-agent surface for ProofForge product docs, chain catalog, and CLI guidance — Streamable HTTP remote MCP for agents (docs · catalog · PF Solana/EVM/Aleo guidance).

Live endpoint

POST https://<this-host>/mcp
Transport: Streamable HTTP

Connect

# Codex
codex mcp add proof-forge-mcp --url https://<this-host>/mcp

# Claude Code
claude mcp add --transport http proof-forge-mcp https://<this-host>/mcp

# Cursor / generic (mcp-remote proxy)
npx -y mcp-remote https://<this-host>/mcp

Tools

Tool	Purpose
`pf_health`	Capability probe + live demo links
`pf_list_docs` / `pf_get_doc` / `pf_search_docs`	Product docs
`pf_chain_catalog` / `pf_target_info`	Target metadata
`pf_agent_instructions`	How agents should use PF
`pf_cli_cheatsheet`	Local `pf` commands
`pf_aleo_live_demo`	Published Aleo Testnet evidence
`pf_solana_scaffold`	Solana PF ladder + frontend template
`pf_solana_ix_codec`	PF ix-data (body-only disc / CPI handlerId)
`pf_solana_artifacts`	build outputs → UI vs CLI
`pf_psy_scaffold`	Psy DPN ladder + official hand-off
`pf_psy_artifacts`	`*.dpn.json` package shape
`pf_psy_ecosystem`	app / wallet / explorer / IDE / SDK

Solana (ProofForge path)

Contracts: ProgramV1 + pf build --target solana (not Anchor). Frontend: templates/solana-dapp-ui. Tools: pf_solana_scaffold, pf_solana_ix_codec, pf_solana_artifacts.

Psy (DPN hand-off)

Contracts: ProgramV1 + pf build --target psy → *.dpn.json (deployable=false). Deploy/wallet/SDK: official app · wallet · WebIDE · explorer · psyup/dargo. Tools: pf_psy_scaffold, pf_psy_artifacts, pf_psy_ecosystem.

Boundaries

Edge MCP is guidance-only (no Lean/CLI spawn, no keys, no broadcast).
Compile / deploy: local pf or monorepo stdio MCP tools/mcp.
Not formal / hermetic / mainnet.

Live Aleo demo

Recording: asciinema.org/a/1262697
Program: pfdemo336641.aleo

/health · /mcp