_ registry / mcp streamable-http · checked 12h ago

pipingtoolset-data

https://pipingtoolset.com

Registry code: abba4978d90740a8

api record

Engineering code-table data with citations. Use find_dataset, then describe_dataset for the key fields, then lookup_value for one row and one column. Every value carries its standard, edition, table, row and column; confirm it against the printed page before issue. Pointer results name the table, row and column to read; they carry no value.

endpoint
https://pipingtoolset.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is pipingtoolset-data live?
Yes — it answered the hub's last check (checked 12h ago). It answered 100% of checks over the last 30 days.
Is pipingtoolset-data free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does pipingtoolset-data have?
10 tools: describe_dataset, get_pointer, get_skey_map, get_aisc_shape, find_dataset, lookup_value, list_keys, get_fixture_example, ….
Is pipingtoolset-data safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,121ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 10 tools
1 open1 auth-required 8 never probed 2 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • verify_connector open 12h ago

    Report whether the caller is signed in, the caller's tier, how many datasets return values at that tier, and the remaining daily lookups when the server tracks them. Returns no email, name or account id.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_pipe_dimensions auth-required 12h ago

    Return the outside diameter and nominal wall thickness (in) for a nominal pipe size per ASME B36.10M / B36.19M: one schedule with its wall and inside diameter when `schedule` is given (e.g. 40, STD, XS, 80, 10S), otherwise the walls of every schedule listed at that size.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "nps"
      ],
      "properties": {
        "nps": {
          "type": "string",
          "maxLength": 10,
          "minLength": 1,
          "description": "Nominal pipe size, e.g. 6, 1-1/2, 3/4"
        },
        "schedule": {
          "type": "string",
          "maxLength": 20,
          "description": "Schedule or weight class, e.g. 40, STD, XS, 160, 10S"
        }
      }
    }
    arguments 20 lines
  • describe_dataset unknown never probed

    Describe one dataset: the key fields a lookup needs, the value columns with units and which need a temperature, the citation (standard, edition, table), whether lookups return a value or a pointer, the tier at which values are returned, and the daily lookup limits. Returns structure only, no table values.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "dataset_id"
      ],
      "properties": {
        "dataset_id": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "Dataset id from find_dataset"
        }
      }
    }
    arguments 15 lines
  • get_pointer unknown 12h ago

    For a quantity whose value this server does not return (for example PVP2011-57100 nozzle allowables, ASCE 7-22 SDS, Ip, CAR and Rpo, AISC Fy/Fu, ACI anchor product values, API 617/611/612 and NEMA SM 23 coefficients, API 650 Annex P coefficients, and any dataset currently returned as a location only), return where to read it: standard, edition, table or figure, the row key and columns, and the inputs needed. Never returns a value.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "standard",
        "quantity"
      ],
      "properties": {
        "quantity": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "What you need, e.g. 'SDS' or 'allowable nozzle loads class 150'"
        },
        "standard": {
          "type": "string",
          "maxLength": 60,
          "minLength": 1,
          "description": "Standard, e.g. 'ASCE 7-22', 'API 617', 'PVP2011-57100'"
        }
      }
    }
    arguments 22 lines
  • get_skey_map unknown never probed

    Return the Isogen-style SKEY vocabulary Piping Toolset uses (component prefixes, end-condition suffixes, fitting and support keys) with scope 'isogen', or the PCF record set, substitutions and default SKEYs that import cleanly into CAESAR II with scope 'caesar-safe'. `component` narrows the result to one group, e.g. 'valve_prefix' or 'safe_substitutions'.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "scope"
      ],
      "properties": {
        "scope": {
          "enum": [
            "isogen",
            "caesar-safe"
          ],
          "type": "string",
          "description": "isogen = SKEY registry; caesar-safe = PCF records for CAESAR II import"
        },
        "component": {
          "type": "string",
          "maxLength": 60,
          "description": "Optional group name within the scope"
        }
      }
    }
    arguments 22 lines
  • get_aisc_shape unknown 39h ago

    Return the dimensions and section properties of one AISC shape by designation (e.g. W8X31, HSS6X6X3/8, PIPE4STD, L4X4X1/2): weight, area, depth, flange and web dimensions, I, S, Z, r, J and Cw as applicable. Source: AISC Shapes Database v16.0; L, HSS and Pipe computed from nominal geometry.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "designation"
      ],
      "properties": {
        "designation": {
          "type": "string",
          "maxLength": 40,
          "minLength": 1,
          "description": "AISC designation, spaces ignored, e.g. W8X31"
        }
      }
    }
    arguments 15 lines
  • find_dataset unknown never probed

    Search the engineering code-table datasets by keyword (standard, table, quantity, material). Returns up to 10 matches, each with its id, title, standard, edition and table, whether lookups return a value or a pointer (table, row and column only), and the tier at which values are returned.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Keywords, e.g. 'B31.3 allowable stress A106' or 'support spacing'"
        },
        "standard": {
          "type": "string",
          "maxLength": 60,
          "description": "Optional standard filter, e.g. 'ASME B31.1'"
        }
      }
    }
    arguments 20 lines
  • lookup_value unknown never probed

    Return one value from one row and one column of a code-table dataset, with its citation (standard, edition, table, row, column), unit and the tabulated entries used. Temperature columns take T in °F; allowable-stress and flange-rating columns interpolate linearly between the two bracketing tabulated temperatures and never extrapolate. Datasets in pointer mode return the citation with value null. The key must identify exactly one row; use list_keys for identifiers.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "dataset_id",
        "key"
      ],
      "properties": {
        "key": {
          "type": "object",
          "description": "Key fields from describe_dataset, e.g. {\"nps\": 2} or {\"spec\": \"A106\", \"grade\": \"B\", \"T\": 650}",
          "propertyNames": {
            "type": "string"
          },
          "additionalProperties": {
            "type": [
              "string",
              "number",
              "boolean"
            ]
          }
        },
        "column": {
          "type": "string",
          "maxLength": 40,
          "description": "Value column; optional when the dataset has a default column"
        },
        "dataset_id": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "Dataset id from find_dataset"
        }
      }
    }
    arguments 35 lines
  • list_keys unknown never probed

    List the key identifiers of a dataset's rows (for example spec, grade, class, size, and the row position `line`) so lookup_value can address exactly one row. Returns identifiers only, never table values, at most 50 per call; `prefix` filters on the first key field. For pointer datasets it returns the key schema without rows.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "dataset_id"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum identifiers to return (default 20, max 50)"
        },
        "prefix": {
          "type": "string",
          "maxLength": 60,
          "description": "Only identifiers whose first key field starts with this text"
        },
        "dataset_id": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "Dataset id from find_dataset"
        }
      }
    }
    arguments 26 lines
  • get_fixture_example unknown 39h ago

    Return one worked example case for a Piping Toolset plugin skill: the inputs, the expected outputs and the pass/fail status from the hand-checked calculation fixtures, with case names removed. `case` selects among the skill's cases (0-based; the result gives the count).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "skill"
      ],
      "properties": {
        "case": {
          "type": "integer",
          "maximum": 500,
          "minimum": 0,
          "description": "0-based case index (default 0)"
        },
        "skill": {
          "enum": [
            "pipe-stress-check",
            "bolted-flange",
            "nozzle-load",
            "pipe-support",
            "load-case-builder",
            "stress-import",
            "pressure-design",
            "stress-screening",
            "iso-to-pcf"
          ],
          "type": "string",
          "description": "Plugin skill slug (current names first; 0.9.x names stay accepted)"
        }
      }
    }
    arguments 30 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id abba4978d90740a8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/abba4978d90740a8/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/abba4978d90740a8/badge.svg)](https://brick.blue/agent/abba4978d90740a8?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.