Partglyph MCP Gateway
REMOTE · APP.PARTGLYPH.COM
Deterministic industrial replacement engine with official catalogs and expert accuracy checks.
Available components
Last scanned (2 months ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 17 Aug 2026.
Category E-commerce
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HTTPS
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool Safety in Tool SafetyNot scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Aug 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 23 Aug 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 22 Aug 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Aug 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Aug 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 18 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.73 → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Schema quality: 50 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 17 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Aug 2026 · Probed https://app.partglyph.com/api-mcp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=partglyph.com | CN=YE2,O=Let's Encrypt,C=US | 9 Jul 2026 | 7 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5d4e5568b2bc249a65999623b69e7955e91 |
| SANs: *.partglyph.com, partglyph.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.partglyph.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| partglyph.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.partglyph.com/api-mcp/mcp | Unreachable | ||
| http (plaintext) | http://app.partglyph.com/api-mcp/mcp | HTTPS enforced | 301 | https://app.partglyph.com/api-mcp/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
build_match_request ~65
Build a user-management match-run request after deterministic validation.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | – | – | – |
| include_non_drop_in | boolean | – | – |
| limit | – | – | – |
| prepared_input | object | yes | – |
| product_id | string | yes | – |
| query_text | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_ball_valve_identity_rows ~57
Read Ball Valve lazy identity rows through user management history.
| Name | Type | Req | Description |
|---|---|---|---|
| bearer_token | – | – | – |
| correlation_id | – | – | – |
| family_id | string | yes | – |
| history_id | string | yes | – |
| request_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_client_instruction_resource ~29
Return deterministic customer-side LLM instruction text by resource name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_input_preparation_guide ~35
Return product-specific input modes, field guidance, examples, and clarification order.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_match_history ~44
Read match history through user management.
| Name | Type | Req | Description |
|---|---|---|---|
| bearer_token | – | – | – |
| correlation_id | – | – | – |
| limit | – | – | – |
| offset | – | – | – |
| request_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_match_result_detail ~46
Read a match history detail bundle through user management.
| Name | Type | Req | Description |
|---|---|---|---|
| bearer_token | – | – | – |
| correlation_id | – | – | – |
| history_id | string | yes | – |
| request_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_product_contract ~47
Return the generated product contract for a supported product.
| Name | Type | Req | Description |
|---|---|---|---|
| include_fixtures | boolean | – | – |
| include_full_schemas | boolean | – | – |
| product_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_product_selection_catalog ~18
Return source-backed product selection catalog entries.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_result_display_guide ~32
Return product-specific result class, flag, and table presentation guidance.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
health_check ~18
Return MCP runtime health and generated contract bundle status.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
hide_match_history_item ~51
Hide a match history item through user management when the token has write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| bearer_token | – | – | – |
| correlation_id | – | – | – |
| history_id | string | yes | – |
| request_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_product_families ~18
List matcher-derived supported product families.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
run_match ~80
Run a paid governed match through user management.
| Name | Type | Req | Description |
|---|---|---|---|
| bearer_token | – | – | – |
| correlation_id | – | – | – |
| idempotency_key | – | – | – |
| include_non_drop_in | boolean | – | – |
| limit | – | – | – |
| prepared_input | object | yes | – |
| product_id | string | yes | – |
| query_text | – | – | – |
| request_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
validate_prepared_input ~36
Validate a prepared matcher input without charging match credits.
| Name | Type | Req | Description |
|---|---|---|---|
| prepared_input | object | yes | – |
| product_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Partglyph MCP Gateway server?
Partglyph MCP Gateway is a hosted endpoint at https://app.partglyph.com/api-mcp/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · app.partglyph.com
claude mcp add --transport http com-partglyph-mcp-gateway 'https://app.partglyph.com/api-mcp/mcp'
What is the Partglyph MCP Gateway server?
Partglyph MCP Gateway is listed in the public MCP registry as com.partglyph/mcp-gateway. Deterministic industrial replacement engine with official catalogs and expert accuracy checks. This page covers its hosted endpoint (https://app.partglyph.com/api-mcp/mcp).
Is the Partglyph MCP Gateway server safe to use?
Partglyph MCP Gateway scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Partglyph MCP Gateway server expose?
Partglyph MCP Gateway exposes 14 tools: health_check, list_product_families, get_product_selection_catalog, get_product_contract, get_result_display_guide, and 9 more. Their descriptions and schemas cost roughly 576 tokens of context every time the server is loaded.
Does the Partglyph MCP Gateway server require authentication?
Its publisher declares that Partglyph MCP Gateway requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.
Is the Partglyph MCP Gateway server still maintained?
Partglyph MCP Gateway has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 17 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Partglyph MCP Gateway server?
VerifyMCP ran 4 checks on Partglyph MCP Gateway, covering TLS certificate, HTTPS, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Partglyph MCP Gateway: Authorization, HSTS header, Schema quality, Stability and 3 more. 4 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.