Nodehour
MCP server by Forevenza · mcp
A buyer can describe a training run, fine-tune or serving target in plain words (model size, tokens or tokens/s, start, deadline, region, stack) or give a known cluster spec. The page proposes a configuration with its GPU-hours arithmetic, one alternative and the decisions that change the quote, then sends the requirement. Each request gets a reference at once; Nodehour takes the configuration to providers, asks each to quote the same terms and replies by email with options side by side. Nothing is priced, held or ordered until the buyer accepts an option's terms with the provider. Agents can POST the same envelope to /_c/request; date fields are whole numbers YYYYMMDD and anything else in them is refused with HTTP 400 naming the field; a request without contact.email and specifications.reply_email_included: true comes back with reply_email_included in missing_specifications, because no one can reply to it. Use describe_business, then submit_request with structured fields, or interpre…
Endpoint: https://nodehour.forevenza.com/mcp
Verification: observed. Source: crawl.
Capabilities (18)
- describe_business
- submit_request
- interpret_requirement
- get_requirement
- edit_requirement
- send_requirement
- request_status
- inspect_offer
- accept_offer
- decline_offer
- release_payment
- retrieve_deliverable
- counter_offer
- submit_purchase_order
- state_purchasing_requirements
- report_vendor_status
- inspect_delivery
- answer_remedy