Skip to main content
Glama
Zhekinmaksim

proofmarket-mcp

by Zhekinmaksim

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
market_stateA

Snapshot the running market: the three numbers most protocols collapse into one, plus the matching and scheduling gaps. A model, not live telemetry.

simulate_coordinationA

Run the proofmarket-sim engine over a full horizon for a coordination regime and return utilization and the two gaps. Same supply in every regime; only coordination changes.

submit_proof_requestA

A Seeker submits a Proof Request to the market. Returns a request id you can poll. The Matchmaker assigns it to a Prover Node when capacity is free.

poll_proofA

Check a Proof Request. When it settles, the result carries a proof id and attestation, delivered the way Fermah returns a proof to a Seeker callback URL. Zero humans involved.

compose_workflowA

The agentic path: define an ordered sequence and the surface runs the whole thing, no human in the loop. Steps: observe a condition, request_proof, act, settle. Returns an attested trace.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
aboutWhat this MCP surface is and is not

Latest Blog Posts

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