Site

uk.co.grainstoragecostsPublished by grainstoragecosts.co.ukOfficial publisherv1.0.1Updated Nov 8, 2026

Grain Storage Costs: the site's own MCP server — enquiry (enquiry = a human handoff, not a...

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Grain Storage Costs site server that lets an assistant describe, fill in and submit a grain storage enquiry to human providers.

What you can do
  • Read what submitting an enquiry does, who receives the details and the consent wording
  • List every enquiry field with its key, label, type, required flag, help text and allowed options
  • Submit an enquiry keyed by field key with consent, returning a summary, consent line and confirmation token
When to use it
Use when someone wants to be put in touch with grain storage providers and needs to fill in the site's enquiry form through an assistant, including seeing the fields and consent terms first.
Requirements
Remote streamable HTTP endpoint at the provider's site; no packages, environment variables or headers declared. The person must give their answers and explicit consent before submission.
Before you install
Submitting sends the person's details to human providers, so confirm the summary and consent wording with them first. It is not a purchase or a guaranteed quote, and the submission is a two-step flow using a confirmation token.

Installation

In SourceWeft

  1. Open Site in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/uk.co.grainstoragecosts%2Fsite/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "site": {
      "type": "http",
      "url": "https://grainstoragecosts.co.uk/mcp"
    }
  }
}

README

This repository has no README.

Tools

3

enquiry_describe

What you get: an ENQUIRY with a human (not a purchase, not a guaranteed quote)

Read first. States plainly what submit_enquiry does on Grain Storage Costs: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.

Takes no parameters.

enquiry_fields

The questions the enquiry asks

Every field of the Grain Storage Costs enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.

Takes no parameters.

submit_enquiry

Submit an ENQUIRY to human providers (two steps; not a purchase)

Submits an enquiry to Grain Storage Costs — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Send my contact details to up to three agricultural building and grain store firms, chosen by Grain Storage Costs, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."

Parametersanswersrequiredconsentrequiredconfirmation

Version history

2
  1. v1.0.1LatestOct 3, 2026
  2. v1.0.0Sep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.