Piping Toolset Engineering Data MCP server
com.pipingtoolset/datapipingtoolset.comstreamable-httpv0.1.0Scanned
Engineering code-table data with citations: standard, edition, table, row and column.
10 tools: 1 change things and 9 only read.
- Reads private data · 4
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Piping Toolset Engineering Data MCP server can do
The Piping Toolset Engineering Data MCP server is published by pipingtoolset.com, a domain the MCP Registry verified. It has 10 tools. It can create or change data (1 tool: verify_connector), but cannot delete data. 9 tools only read.
4 tools read private data (find_dataset, describe_dataset, lookup_value and 1 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 12, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
10 tools
Changes things 1Claude Code: ask
verify_connectorReport 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check the connection
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 9Show 9 read-only tools
describe_datasetDescribe 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 va…Reads private dataNo findings
Why it is in this group
- The name "describe_dataset" says "describe": a word for reading.
What it can reach
- private-dataThe description's first sentence says "describe" and "table": it reads databases.
Description, as the server wrote it 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.
Annotations the server declares
- title: Describe a code dataset
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
find_datasetSearch the engineering code-table datasets by keyword (standard, table, quantity, material).Reads private dataNo findings
Why it is in this group
- The name "find_dataset" says "find": a word for reading.
What it can reach
- private-dataThe description's first sentence says "search" and "table": it reads databases.
Description, as the server wrote it 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.
Annotations the server declares
- title: Find a code dataset
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_aisc_shapeReturn the dimensions and section properties of one AISC shape by designation (e.g.No findings
Why it is in this group
- The name "get_aisc_shape" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: AISC shape properties
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_fixture_exampleReturn 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 na…No findings
Why it is in this group
- The name "get_fixture_example" says "get": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Worked example for a skill
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_pipe_dimensionsReturn 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 gi…No findings
Why it is in this group
- The name "get_pipe_dimensions" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Pipe OD and wall by schedule
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_pointerFor 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/…Reads private dataNo findings
Why it is in this group
- The name "get_pointer" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "table": it reads databases.
Description, as the server wrote it 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.
Annotations the server declares
- title: Locate a value in a standard
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_skey_mapReturn 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, subst…No findings
Why it is in this group
- The name "get_skey_map" says "get": a word for reading.
Description, as the server wrote it 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'.
Annotations the server declares
- title: SKEY and PCF mapping
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_keysList 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.No findings
Why it is in this group
- The name "list_keys" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List the row identifiers of a dataset
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
lookup_valueReturn 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.Reads private dataNo findings
Why it is in this group
- The name "lookup_value" says "lookup": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "table": it reads databases.
Description, as the server wrote it 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.
Annotations the server declares
- title: Look up one cited code-table value
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:21 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://pipingtoolset.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://ptqikcvueeyldwzcqtfg.supabase.co/auth/v1
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://pipingtoolset.com/mcp: tools/list returned 10 tools to an anonymous client, including verify_connector (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http data https://pipingtoolset.com/mcpclaude mcp add --transport http data https://pipingtoolset.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__data__find_dataset",
"mcp__data__describe_dataset",
"mcp__data__lookup_value",
"mcp__data__list_keys",
"mcp__data__get_pointer",
"mcp__data__get_skey_map",
"mcp__data__get_fixture_example",
"mcp__data__get_aisc_shape",
"mcp__data__get_pipe_dimensions"
],
"ask": [
"mcp__data__verify_connector"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as data. Review it before you use it.
Capability tags behind 4 rules
- mcp__data__find_dataset private-data
- mcp__data__describe_dataset private-data
- mcp__data__lookup_value private-data
- mcp__data__get_pointer private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.pipingtoolset/data/verify?hash=c827828d904b8560c9b2acb5916223a17f89bee94bf7d6d803f09915f6203b5a" | jq -e '.changed == false'Pinned hash c827828d904b, from Nov 12, 2026, 11:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.pipingtoolset/data/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.pipingtoolset/data)Source: MCP Registry · repository. Synced Nov 12, 2026, 11:17 UTC.
Piping Toolset Engineering Data MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Piping Toolset Engineering Data MCP server safe?
- No scan can promise that. What its definitions show: 10 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Piping Toolset Engineering Data MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Piping Toolset Engineering Data MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Piping Toolset Engineering Data MCP server have?
- 10 tools: 1 write, 9 read. verify_connector, find_dataset, describe_dataset, lookup_value, list_keys, get_pointer, get_skey_map, get_fixture_example and 2 more.
Does the Piping Toolset Engineering Data MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Piping Toolset Engineering Data MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Piping Toolset Engineering Data MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.