Server definition

Hash: sha256:089e20516a2cd82417b3872fc17f927ccc8476aee45fc95a40b4ce29189f6b46
What it is: What a remote MCP server returned when asked what it offers: 1 tools

The blob, as servednamed by its sha256

{
  "instructions": "Use submit_component_rfq when a buyer needs hard-to-find, obsolete, EOL, spot-market, BOM, or Shenzhen-sourced electronic components. RFQs are reviewed by Maria Jurk in Shenzhen. The service does not claim real-time inventory and does not fabricate pricing or availability.",
  "tools": [
    {
      "description": "Submit an electronic component RFQ for human sourcing in Shenzhen, China. Use for hard-to-find, obsolete, EOL, spot-market, BOM, or other components requiring China sourcing. Maria Jurk reviews the request. This tool does not claim real-time inventory or fabricate pricing or availability.",
      "inputSchema": {
        "properties": {
          "company": {
            "default": "",
            "description": "Buyer company or organization name.",
            "title": "Company",
            "type": "string"
          },
          "email": {
            "description": "Buyer email address where Maria Jurk can respond to the RFQ.",
            "title": "Email",
            "type": "string"
          },
          "manufacturer": {
            "default": "",
            "description": "Component manufacturer or brand, if known. Leave empty when unknown.",
            "title": "Manufacturer",
            "type": "string"
          },
          "name": {
            "default": "",
            "description": "Name of the buyer or contact person submitting the RFQ.",
            "title": "Name",
            "type": "string"
          },
          "notes": {
            "default": "",
            "description": "Additional sourcing requirements such as date code, target price, destination, lead time, packaging, acceptable alternatives, or BOM context.",
            "title": "Notes",
            "type": "string"
          },
          "part_number": {
            "description": "Exact manufacturer part number or component identifier the buyer needs sourced.",
            "title": "Part Number",
            "type": "string"
          },
          "quantity": {
            "description": "Required quantity, including units when useful, for example '500 pcs'.",
            "title": "Quantity",
            "type": "string"
          }
        },
        "required": [
          "part_number",
          "quantity",
          "email"
        ],
        "title": "submit_component_rfqArguments",
        "type": "object"
      },
      "name": "submit_component_rfq",
      "outputSchema": {
        "properties": {
          "error": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "description": "Error message when the RFQ could not be accepted.",
            "title": "Error"
          },
          "handled_by": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "description": "Human sourcing specialist responsible for reviewing the RFQ.",
            "title": "Handled By"
          },
          "http_status": {
            "anyOf": [
              {
                "type": "integer"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "description": "Upstream HTTP status when the RFQ could not be accepted.",
            "title": "Http Status"
          },
          "location": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "description": "Location of the human sourcing specialist.",
            "title": "Location"
          },
          "ok": {
            "description": "Whether the RFQ was accepted successfully.",
            "title": "Ok",
            "type": "boolean"
          },
          "reference": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "description": "Unique Jurk RFQ reference for the submitted request.",
            "title": "Reference"
          },
          "status": {
            "anyOf": [
              {
                "type": "string"
              },
              {
                "type": "null"
              }
            ],
            "default": null,
            "description": "RFQ processing status, such as rfq_received.",
            "title": "Status"
          }
        },
        "required": [
          "ok"
        ],
        "title": "RFQResult",
        "type": "object"
      }
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:089e20516a2cd82417b3872fc17f927ccc8476aee45fc95a40b4ce29189f6b46 | sha256sum