NestDaddy

Nodehour: GPU capacity sized from your run and quoted by providers

com.forevenza.services/nodehour · v1.1.1

GPU cluster sourcing: describe the run, get a sized requirement, quotes compared by email

Connect Remote server

Terminal
claude mcp add --transport http nodehour https://nodehour.forevenza.com/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "nodehour": {
      "url": "https://nodehour.forevenza.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "nodehour": {
      "type": "http",
      "url": "https://nodehour.forevenza.com/mcp"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://nodehour.forevenza.com/mcp

Tools 18 found in our last check

  • describe_business

    What Nodehour does (GPU capacity sized from your run and quoted by providers: Describe the training run or serving fleet. Nodehour sizes the cluster, takes one requirement to providers that can run it, and returns options side by side to choose from.), what happens to a request,…

  • submit_request

    Send Nodehour a requirement (GPU capacity sized from your run and quoted by providers). You get a reference number at once, and we keep exactly what you sent: your words, the proposed configuration, the terms to quote and the open questions. If sizing or an open question changes…

  • interpret_requirement

    Give Nodehour the buyer's requirement, or a correction or addition to it, in their own words: it is read into a structured requirement (each value says which words it came from), conflicting or unclear facts come back as one question, and words not yet read are kept as written.…

  • get_requirement

    A Nodehour requirement as it stands: each value with where it came from, what it replaced, the open question, words not yet read, whether it was sent and any offer on it.

  • edit_requirement

    Set fields by name ({"op":"set","values":{...}}, an empty value clears) or change the list ({"op":"add"|"update"|"remove"|"replace", ...}), exactly as given: no reading. Use it to answer the open question when the answer is a value.

  • send_requirement

    Send the requirement to Nodehour once the buyer says to: the first send records the request (its receipt token is the requirement's token, for request_status and offers); a later send of a changed requirement records a revision of the same request. Name the revision the buyer sa…

  • request_status

    Resume a requirement using the receipt credentials. Read the recorded requirement, any replies the business has published on it (messages: where it answers a buyer with no email, it answers here) and any linked offers. Answer a reply by sending a continuation. Contact details ar…

  • inspect_offer

    Read the exact authorized terms, terms hash, order state and processor payment links, and the thread the business published on the offer: its answers to counteroffers (thread.counteroffers), the purchasing requirements, vendor status and purchase order matches it holds (thread.p…

  • accept_offer

    Place an order on terms you have inspected and the buyer has authorized you to accept. Requires the exact terms hash and explicit acceptance. Follow inspect_offer later for payment links and verified payment state.

  • decline_offer

    Decline an issued offer on its inspected terms.

  • release_payment

    Confirm a payment condition only where the inspected order allows the customer to release it. This records approval; it does not pay the processor.

  • retrieve_deliverable

    Retrieve what a paid order delivers, where the business produces it itself (a report): the exact text, its SHA-256, version, sources and any shortfall. Before payment is confirmed it says it is not yet available. Use the offer link or linked request credentials.

  • counter_offer

    Propose a change to an issued offer on its inspected terms: other quantities (by item index in terms.items), another list of companies (where the items price companies), a delivery date, a total price for the whole, a payment plan, or a note. It is a proposal, not a change: the…

  • submit_purchase_order

    Send the buyer's purchase order for an issued offer or a placed order: number, revision, lines, total, currency and payment terms. It is matched against the accepted terms; differences are recorded and shown in inspect_offer thread.purchasing as exceptions, never silently accept…

  • state_purchasing_requirements

    Tell the business how the buyer's purchasing works for this offer: whether the seller must be an approved vendor, whether a purchase order is required, which documents are needed, the seller's vendor id with the buyer, where orders and invoices go, and the payment terms. Recorde…

  • report_vendor_status

    Report the seller's vendor standing with the buyer's organization (APPROVED, DOCUMENTS_REQUESTED or REJECTED) with the buyer's approval or case reference and any documents requested. Recorded as the buyer's own statement; the business answers it in inspect_offer thread.purchasin…

  • inspect_delivery

    Record the buyer's inspection of a placed order: for each item (its index in terms.items) the quantity accepted and the quantity rejected, with a reason for a rejection, optionally for one portion of the order. Whether it was accepted is computed: only when nothing is rejected.…

  • answer_remedy

    Accept or decline a remedy the business proposed on a placed order (inspect_offer thread.fulfilment.remedies with state PROPOSED). Recorded for the business, which applies it and shows the result there. Accepting a credit or refund here moves no money; the business records it wh…

Details

Endpointhttps://nodehour.forevenza.com/mcp (Streamable HTTP)
First published6 Nov 2026
Last updated6 Nov 2026
Registry namecom.forevenza.services/nodehour

More communication servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.