io.github.jinweihan-ai/ferrolaser-parts
REMOTE · MCP.FERROLASER.COM · SCANNED AUG 3
Fiber laser parts knowledge: laser sources, cutting/welding heads, CNC controls, alarm codes.
Available components
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 →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 578 tokens (~115/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.ferrolaser.com
claude mcp add --transport http jinweihan-ai-ferrolaser-parts https://mcp.ferrolaser.com/mcp
[mcp_servers.jinweihan-ai-ferrolaser-parts] url = "https://mcp.ferrolaser.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jinweihan-ai-ferrolaser-parts": {
"type": "remote",
"url": "https://mcp.ferrolaser.com/mcp",
"enabled": true
}
}
} openclaw mcp add jinweihan-ai-ferrolaser-parts --url https://mcp.ferrolaser.com/mcp --transport streamable-http
mcp_servers:
jinweihan-ai-ferrolaser-parts:
url: "https://mcp.ferrolaser.com/mcp" {
"mcpServers": {
"jinweihan-ai-ferrolaser-parts": {
"type": "http",
"url": "https://mcp.ferrolaser.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 54
First indexed and scored.
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 3 Aug 2026 · Probed https://mcp.ferrolaser.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.ferrolaser.com | CN=YR1,O=Let's Encrypt,C=US | 3 Jul 2026 | 1 Oct 2026 | RSA 4096 | SHA256-RSA | 5410fa143e734b5cc666dd6be1cf7a8a093 |
| SANs: mcp.ferrolaser.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of mcp.ferrolaser.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ferrolaser.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.ferrolaser.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.ferrolaser.com/mcp | Inconclusive | 404 |
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.
get_brand_overview ~72
Read a category-level overview essay. Topics: anatomy (what a fiber laser machine is made of), laser-sources, cutting-heads, welding-heads, control-systems, cladding-cleaning. Written in Chinese; translate for the user as needed.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | — |
No output schema declared.
No examples provided.
get_part_card ~65
Fetch ONE knowledge card in full (specs table, wiring, alarm codes, consumable part numbers, field notes) by card_id (from search results) or by exact/partial title.
| Name | Type | Req | Description |
|---|---|---|---|
| card_id | string | — | — |
| title | string | — | — |
No output schema declared.
No examples provided.
list_brands ~41
List the brands covered by this knowledge base with card counts and a one-line intro for each (laser sources, cutting/welding heads, control systems).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_parts_knowledge ~145
Search 521 knowledge cards about fiber laser machine parts: laser sources, cutting heads, welding heads, control systems, wire feeders. Query by model (e.g. "BLT421", "FSCUT2000", "RFL-C3000"), alarm/error keyword, or topic. Optional brand filter: raycus / maxphotonics / jpt / bochu (friendess) / empower (raytools) / ospri / superlaser. Returns best-matching cards with excerpt; use get_part_card for full text.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | — | — |
| query | string | yes | — |
| top | integer | — | — |
No output schema declared.
No examples provided.
submit_inquiry ~110
Send an inquiry to FerroLaser's sales engineers — for fiber laser machine quotes, part/component sourcing, or technical consultation. A human engineer replies within one business day. Requires name, a valid email, and a message describing the need.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | — | — |
| country | string | — | — |
| string | yes | — | |
| message | string | yes | — |
| name | string | yes | — |
| part_or_model | string | — | — |
| phone | string | — | — |
No output schema declared.
No examples provided.