proofmarket-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@proofmarket-mcpcheck the current proof market state"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
proofmarket-mcp
An MCP server that exposes a machine-callable proof-market surface. An agent connects over the Model Context Protocol, submits Proof Requests, reads the market's supply / allocated / utilized, and composes multi-step workflows that run with no human in the loop.
It is the surface Fermah keeps describing: the primary user of a protocol is no longer a human clicking a dashboard, it is an agent calling an execution surface directly. This repo is a small, runnable answer to "what does that surface look like."
This is a reference model, not Fermah's production Kernel and not live network data. The coordination mechanics come from proofmarket-sim; the same engine settles every number. Vocabulary follows Fermah: Seekers submit Proof Requests, the Matchmaker assigns them to Prover Nodes.
Tools
market_state - snapshot supply, allocated, utilized, and the matching and scheduling gaps of the running market.
simulate_coordination - run the coordination model over a full horizon for a regime (today / no-operator / coordinated). Same supply in every regime; only coordination changes.
submit_proof_request - a Seeker submits a Proof Request; returns an id to poll.
poll_proof - check a request; on settle it carries a proof id and attestation, delivered the way a proof returns to a Seeker callback. Zero humans.
compose_workflow - define an ordered sequence (observe, request_proof, act, settle) and the surface runs the whole thing, returning an attested trace with humans in the loop = 0.
There is also an proofmarket://about resource describing what the surface is and is not.
Related MCP server: Servicialo
Run it
npm install
npm test # in-memory MCP client lists tools, drives the surface
npm run demo # an agent drives the surface end to end, no human in the loop
npm start # start the MCP server on stdioConnect it to an agent
Claude Desktop (claude_desktop_config.json), Cursor, or any MCP client over stdio:
{
"mcpServers": {
"proofmarket-surface": {
"command": "node",
"args": ["/absolute/path/to/proofmarket-mcp/src/server.js"]
}
}
}Then ask the agent to check the market, compare coordination regimes, and compose a proof workflow. It will call the tools directly, with no human in the loop.
Why this exists
A protocol without a machine-callable surface is invisible to agents no matter how capable its onchain logic is. The point of this repo is not to reimplement Fermah. It is to make the surface concrete, runnable, and honest: an agent can drive a proof market end to end, and you can read every line of how it works.
License
MIT. Built by ZERTH MAXX (@0maxxdev). Not affiliated with or endorsed by Fermah.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceAn agent-to-agent marketplace where AI agents discover, hire, and pay each other in USDC on Base. Agents list services, post jobs, submit proposals, and invoke each other's capabilities — all through API, MCP, or A2A protocol.MIT
- AlicenseAqualityAmaintenanceOpen protocol for AI-agent coordination of professional services. Scheduling, identity, delivery verification, and financial settlement across any vertical.103131Apache 2.0
- Alicense-qualityCmaintenanceCryptographically signed market state verification for autonomous financial agents. Ed25519 receipts, fail-closed safety, 28 global exchanges (equities, derivatives, 24/7 crypto). MCP-native, x402-payable, SMA Protocol conformant.MIT
- Flicense-qualityDmaintenanceAn agent-native marketplace API where any agent can publish allocatable resources, search for what they need, negotiate structured offers, and exchange contact details after mutual acceptance. The protocol is flexible — it works for GPU hours traded between agents, physical courier services, time-bounded API keys, dataset access, or resource types that don't exist yet.1
Related MCP Connectors
Signed agent discovery, security attestations, paid work, and verified settlement reputation.
Agent-native crypto market-data over MCP+REST: order flow, whales, liquidations, calibrated scores
52 paid x402 API endpoints for AI agents — crypto, data, DeFi, market intelligence.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Zhekinmaksim/proofmarket-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server