Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Altınkaya Enclosures

NPM · ALTINKAYA-MCP · 2 COMPONENTS

Search, filter and compare Altınkaya electronic enclosures and get their CAD files.

+3 this week 87 Trust /100

Last scanned (20 hours ago)

Scores higher than 81% of npm servers

Category IoT and Hardware

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 6 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to amazeng-co/altinkaya-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 13 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 7483 tokens (~14/item across 520 items; 6 tools + 514 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 65% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +2
    • Stability: unverified → 0.17 ▲ functional
  • 8 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 7 Nov 26 66

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/altinkaya-mcp@0.1.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo amazeng-co/altinkaya-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/amazeng-co/altinkaya-mcp/.github/workflows/release.yml@refs/heads/main
Rekor log index 3745846400
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:644390da931ab6241a70c2ebd1954fb41ce12e0d08f8e031a807153d290827bdce26d78f6855e2efcfb599e3f60bf730be0203e47e4b21e5878ff76b7

Background: How many MCP packages publish verified provenance →

Dependencies 6 packages
Packages resolved 6
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~521 tokens

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 →

Tool Tokens
compare_enclosures ~33

Side-by-side comparison of 2–10 enclosures; lists which fields differ.

NameTypeReqDescription
codesarrayyes–
NameTypeReqDescription
differencesarrayyes–
enclosuresarrayyes–
notFoundarrayyesCodes that were unknown or ambiguous, with hints

No examples provided.

filter_enclosures ~198

Parametric search: outer size limits, minimum IP rating, material and category. Use min_outer_mm with your PCB or contents size as a first pass, then confirm the inner space on the drawing. Dimensions are outer dimensions in mm. Usable inner space is smaller: check the drawing (get_cad_files) before committing to a PCB size.

NameTypeReqDescription
categorystring–Category id, slug or name (includes subcategories)
limitinteger––
materialsarray–Any of, e.g. ["ABS", "Alüminyum"]
max_outer_mmobject–Outer dimensions must be at most this
min_ipstring–e.g. "IP65"
min_outer_mmobject–Outer dimensions must be at least this
offsetinteger––
querystring–Optional keyword filter
sortstring–volume = smallest first
NameTypeReqDescription
notestringyes–
offsetnumberyes–
resultsarrayyes–
totalnumberyes–

No examples provided.

get_cad_files ~59

Download links for an enclosure's dimensioned PDF drawing, DXF, STEP 3D model, IP certificate, CNC machining template and UV print template.

NameTypeReqDescription
codestringyes–
typesarray–Only these document types
NameTypeReqDescription
codestringyes–
documentsarrayyes–
productUrlstringyes–

No examples provided.

get_enclosure ~130

Full details for one enclosure: all specifications, drawing dimensions, documents, images and its variants (colors, lids, lengths… with order codes and barcodes). optionValues lists every option; pass `options` to get the order code of a specific configuration.

NameTypeReqDescription
codestringyesModel code (EC-1015), variant order code (EC-1015-7-0-0-G-0) or slug
optionsobject–Only variants with these options, e.g. { "Renk": "Siyah" }
variant_limitinteger––
NameTypeReqDescription
categorystringyes–
enclosureobjectyes–
notestringyes–

No examples provided.

list_categories ~22

The enclosure category tree with the number of enclosures in each category.

Input schema present but exposes no named parameters.

NameTypeReqDescription
categoriesarrayyes–

No examples provided.

search_enclosures ~79

Keyword search across the Altınkaya enclosure catalog: product codes (EC-1015, RT-014), Turkish or English names, categories, materials and IP ratings.

NameTypeReqDescription
limitinteger––
querystringyese.g. "EC-1015", "IP67 abs", "din rail", "el tipi"
NameTypeReqDescription
resultsarrayyes–
totalnumberyes–

No examples provided.

Install

How do I install the Altınkaya Enclosures MCP server?

Altınkaya Enclosures runs locally as an npm package, launched with npx -y altinkaya-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · altinkaya-mcp

# add to Claude Code
claude mcp add amazeng-co-altinkaya-mcp -- npx -y altinkaya-mcp
Common questions

What is the Altınkaya Enclosures MCP server?

Altınkaya Enclosures is an MCP server listed in the public MCP registry as io.github.amazeng-co/altinkaya-mcp. Search, filter and compare Altınkaya electronic enclosures and get their CAD files. This page covers its npm package (altinkaya-mcp).

Is the Altınkaya Enclosures MCP server safe to use?

Altınkaya Enclosures scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Altınkaya Enclosures MCP server expose?

Altınkaya Enclosures exposes 6 tools: search_enclosures, filter_enclosures, get_enclosure, compare_enclosures, list_categories, get_cad_files. Their descriptions and schemas cost roughly 521 tokens of context every time the server is loaded.

Is the Altınkaya Enclosures MCP server still maintained?

Altınkaya Enclosures is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Altınkaya Enclosures MCP server under?

Altınkaya Enclosures declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Altınkaya Enclosures MCP server?

VerifyMCP ran 16 checks on Altınkaya Enclosures, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.