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.

su.hpt/hptsu-mcp

PYPI · HPTSU-MCP · 2 COMPONENTS

Search hpt.su — Russian/EAEU vehicle compliance documents: type approvals, certificates, VIN lookup.

Available components

remote · mcp.hpt.su 38 pypi · hptsu-mcp 74
+1 this week 74 Trust /100

Last scanned (5 hours ago)

Scores higher than 71% of PyPI servers

Category Documents and Files

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to HPT-SU/hptsu-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 78 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability43
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3322 tokens (~151/item across 22 items; 21 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • 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 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (15)

  • 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

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

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.

  • 5 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 31 Oct 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail ▼ functional
  • 30 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: fail → unverified ▼ functional
  • 29 Oct 26 −1
    • Stability: pass → 0.93 functional
  • 25 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 23 Oct 26 0
    • Stability: 0.97 → pass security
  • 22 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: pass → 0.97 functional
  • 21 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
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 5 Nov 2026 · Analysed pypi/hptsu-mcp@0.4.4

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 pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo HPT-SU/hptsu-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/HPT-SU/hptsu-mcp/.github/workflows/publish-pypi.yml@refs/tags/v0.4.4
Rekor log index 2515050112
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:32397c0eb0ce0fe22551fd2f3c9516719acdf8617f19efaa76c0e6580e234e50

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 28 packages
Packages resolved 28
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 21 exposed · ~3,210 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
download_document_file ~213

Get links for a document file: page URL for everyone, direct download URL when the plan allows it. Always returns `document_page_url` — the document's page on hpt.su where the user can download the file manually under their account. Share this link with the user. When the plan includes direct downloads, the response also contains `download_url` — a personal temporary link to the PDF. It can be fetched programmatically: send a GET request with the same `X-API-Key: <key>` header used for this API. In a browser it works when signed in to hpt.su under the account that owns the key. The link is bound to the key owner — it does not work with anyone else's key or account. The download quota is charged at actual download time. Otherwise `download_url` is null and `download_note` explains why.

NameTypeReqDescription
file_uidstringyesDocumentFile UID (from list_document_files).
NameTypeReqDescription
resultstringyes–

No examples provided.

fulltext_search ~191

Full-text search inside type-approval document bodies (PDF text). Covers ОТТС / ОТШ / ЗОТТС / ЗОТШ. Other document kinds (СБКТС / ЗОЕТС / СУТ / cert / decl) are not covered by full-text search. **Premium feature** — requires a plan that includes full-text search (see https://hpt.su/pricing/) with a subscription covering at least one type-approval kind.

NameTypeReqDescription
kind––Filter by registry kind. One of: otts, otch, zotts, zotch. Default: search across all 4 type-approval kinds.
pageinteger–1-based page index.
page_sizeinteger–Rows per page (max 50).
querystringyesFree-text query (Russian, tsquery-syntax allowed).
NameTypeReqDescription
resultstringyes–

No examples provided.

get_document ~86

Fetch a single Document by slug+kind.

NameTypeReqDescription
kindstringyesOne of: otts, otch, zotts, zotch, sbkts, zoets, sout, cert, decl. Slug isn't globally unique between kinds, so kind is required.
slugstringyesDocument slug — URL-form of the number (the same as in site URL).
NameTypeReqDescription
resultstringyes–

No examples provided.

list_brands ~69

Resolve a vehicle brand name to its canonical record (used to filter type approvals).

NameTypeReqDescription
name––Brand name substring (e.g. 'KAMAZ').
pageinteger–1-based page index.
page_sizeinteger–Rows per page (max 50).
NameTypeReqDescription
resultstringyes–

No examples provided.

list_certification_bodies ~62

Lookup accredited certification bodies (issuers of сертификатов/деклараций).

NameTypeReqDescription
name––Body name substring.
pageinteger–1-based page index.
page_sizeinteger–Rows per page (max 50).
NameTypeReqDescription
resultstringyes–

No examples provided.

list_document_files ~143

List the files attached to a document. Returns `[{file_uid, file_name, kind, pages_count, published_at}]` — each entry's `file_uid` can be passed to `download_document_file`. A document often has several PDFs (e.g. cleaned + original); use this tool to enumerate them and pick the right one before download.

NameTypeReqDescription
document_slugstringyesDocument slug (from search.slug field).
kindstringyesOne of: otts, otch, zotts, zotch, sbkts, zoets, sout, cert, decl. Slug isn't globally unique between kinds, so kind is required.
NameTypeReqDescription
resultstringyes–

No examples provided.

list_registry_kinds ~26

Return the catalogue of registry kinds exposed by the hpt.su public API.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

list_test_labs ~66

Lookup accredited testing laboratories (issuers of СБКТС/ЗОЕТС).

NameTypeReqDescription
name––Lab name, full or partial.
pageinteger–1-based page index.
page_sizeinteger–Rows per page (max 50).
NameTypeReqDescription
resultstringyes–

No examples provided.

list_tnved_codes ~98

TN VED EAEU classifier lookup. Note: TN VED codes are linked **only** to certificates and declarations — not to vehicle type approvals or safety reports.

NameTypeReqDescription
pageinteger–1-based page index.
page_sizeinteger–Rows per page (max 50).
prefix––TN VED code prefix (e.g. '8704').
query––Free-text description search.
NameTypeReqDescription
resultstringyes–

No examples provided.

list_vehicle_models ~76

Resolve a vehicle model name (within a brand) to canonical record.

NameTypeReqDescription
brand––Brand name (auto-resolved to id) or numeric brand id.
name––Model name substring.
pageinteger–1-based page index.
page_sizeinteger–Rows per page (max 50).
NameTypeReqDescription
resultstringyes–

No examples provided.

search_by_vin ~124

Aggregated search by VIN across all car-kinds (ОТТС/ОТШ/ЗОТТС/ЗОТШ/ СБКТС/ЗОЕТС). Open for any active API key — no subscription required. Returns documents whose VIN field contains the given fragment, newest first. For exact full-VIN search within a single registry use the per-kind tool (search_otts/search_sbkts/…) with its `vin` parameter.

NameTypeReqDescription
vinstringyesVIN substring or full code (5-17 chars).
NameTypeReqDescription
resultstringyes–

No examples provided.

search_certificates ~153

Search conformity certificates (ТР ТС / ТР ЕАЭС).

NameTypeReqDescription
applicant––Applicant name, full or partial.
applicant_inn––Applicant INN (exact match).
manufacturer––Manufacturer name, full or partial.
number––Certificate number, full or partial.
pageinteger–1-based page index.
page_sizeinteger–Rows per page (max 50).
product––Product full name, full or partial.
regulations––Technical regulation code (e.g. 'ТР ТС 018/2011').
scheme––Certification scheme — '1с'…'9с'.
status––Certificate status code.
NameTypeReqDescription
resultstringyes–

No examples provided.

search_declarations ~154

Search declarations of conformity (ТР ТС / ТР ЕАЭС).

NameTypeReqDescription
applicant––Applicant name, full or partial.
applicant_inn––Applicant INN (exact match).
manufacturer––Manufacturer name, full or partial.
number––Declaration number, full or partial.
pageinteger–1-based page index.
page_sizeinteger–Rows per page (max 50).
product––Product full name, full or partial.
regulations––Technical regulation code (e.g. 'ТР ТС 018/2011').
scheme––Declaration scheme — '1д'…'6д'.
status––Declaration status code.
NameTypeReqDescription
resultstringyes–

No examples provided.

search_documents ~61

Cross-registry search by document number across all hpt.su kinds.

NameTypeReqDescription
number––Document number, full or partial.
pageinteger–1-based page index.
page_sizeinteger–Rows per page (max 50).
NameTypeReqDescription
resultstringyes–

No examples provided.

search_otch ~222

Search ОТШ (chassis type approvals).

NameTypeReqDescription
axis_count––Axle count (e.g. '2') or exact 'axes / wheels' (e.g. '2 / 4') — auto-resolved to reference id. A bare axle count may match several wheel configs; then candidates are returned to pick from.
brand––Brand.
category––Vehicle category.
comm_name––Commercial name.
eco_class––Ecological class — '5' or name; auto-resolved to reference id.
issuer––Certification body name — auto-resolved to id (or pass numeric id).
number––ОТШ number, full or partial.
pageinteger–1-based page index.
page_sizeinteger–Rows per page (max 50).
type––Type / model.
vin––VIN substring (5-17 chars).
wheel_formula––Wheel formula (e.g. '4x2'); auto-resolved to reference id.
NameTypeReqDescription
resultstringyes–

No examples provided.

search_otts ~293

Search ОТТС (vehicle type approvals, ТР ТС 018/2011).

NameTypeReqDescription
axis_count––Axle count (e.g. '2') or exact 'axes / wheels' (e.g. '2 / 4') — auto-resolved to reference id. A bare axle count may match several wheel configs; then candidates are returned to pick from.
brand––Vehicle brand (e.g. 'Toyota').
category––Vehicle category (M1, N2, L3, …).
chassis––Chassis identifier, full or partial.
comm_name––Commercial name, full or partial.
eco_class––Ecological class — pass '5' or the name; auto-resolved to reference id.
issuer––Certification body name — auto-resolved to id (or pass numeric id). See list_certification_bodies.
mods––Modifications, full or partial.
number––ОТТС number, full or partial.
pageinteger–1-based page index.
page_sizeinteger–Rows per page (max 50).
type––Vehicle type / model, full or partial.
vin––VIN, full or partial (5-17 characters).
wheel_formula––Wheel formula (e.g. '4x2'); auto-resolved to reference id.
NameTypeReqDescription
resultstringyes–

No examples provided.

search_sbkts ~354

Search СБКТС (vehicle safety certificate).

NameTypeReqDescription
axis_count––Axle count (e.g. '2') or exact 'axes / wheels' (e.g. '2 / 4') — auto-resolved to reference id. A bare axle count may match several wheel configs; then candidates are returned to pick from.
brand––Brand.
category––Vehicle category.
comm_name––Commercial name.
date_from––Issue date from (YYYY-MM-DD).
date_to––Issue date to (YYYY-MM-DD).
eco_class––Ecological class — '5' or name; auto-resolved to reference id.
engine––ICE engine model, full or partial.
fuel––Engine fuel type, one of: 'бензин', 'дизель', 'газ', 'электро', 'водород'.
issuer––Testing lab name — auto-resolved to id (or pass numeric id). See list_test_labs.
motor––Electric motor model, full or partial.
motor_power––Motor power (kW).
number––СБКТС number.
pageinteger–1-based page index.
page_sizeinteger–Rows per page (max 50).
powertrain––Powertrain type: 'ice' (combustion), 'hybrid', 'electric'.
type––Type.
vin––VIN (10-17 chars; substring/exact).
wheel_formula––Wheel formula (e.g. '4x2'); auto-resolved to reference id.
year––Manufacture year (YYYY).
NameTypeReqDescription
resultstringyes–

No examples provided.

search_sout ~73

Search СУТ (vehicle type notification — small dataset, only basic fields).

NameTypeReqDescription
brand––Brand.
number––СУТ number.
pageinteger–1-based page index.
page_sizeinteger–Rows per page (max 50).
type––Type.
NameTypeReqDescription
resultstringyes–

No examples provided.

search_zoets ~335

Search ЗОЕТС (vehicle technical expertise conclusion).

NameTypeReqDescription
axis_count––Axle count (e.g. '2') or exact 'axes / wheels' (e.g. '2 / 4') — auto-resolved to reference id. A bare axle count may match several wheel configs; then candidates are returned to pick from.
brand––Brand.
category––Vehicle category.
comm_name––Commercial name.
date_from––Issue date from (YYYY-MM-DD).
date_to––Issue date to (YYYY-MM-DD).
eco_class––Ecological class — '5' or name; auto-resolved to reference id.
engine––ICE engine model.
fuel––Engine fuel type, one of: 'бензин', 'дизель', 'газ', 'электро', 'водород'.
issuer––Testing lab name — auto-resolved to id (or pass numeric id).
motor––Electric motor model.
motor_power––Motor power (kW).
number––ЗОЕТС number.
pageinteger–1-based page index.
page_sizeinteger–Rows per page (max 50).
powertrain––Powertrain type: 'ice' (combustion), 'hybrid', 'electric'.
type––Type.
vin––VIN (10-17 chars).
wheel_formula––Wheel formula (e.g. '4x2'); auto-resolved to reference id.
year––Manufacture year.
NameTypeReqDescription
resultstringyes–

No examples provided.

search_zotch ~206

Search ЗОТШ (chassis conformity assessment conclusion).

NameTypeReqDescription
axis_count––Axle count (e.g. '2') or exact 'axes / wheels' (e.g. '2 / 4') — auto-resolved to reference id. A bare axle count may match several wheel configs; then candidates are returned to pick from.
brand––Brand.
category––Vehicle category.
eco_class––Ecological class — '5' or name; auto-resolved to reference id.
issuer––Certification body name — auto-resolved to id (or pass numeric id).
number––ЗОТШ number.
pageinteger–1-based page index.
page_sizeinteger–Rows per page (max 50).
type––Type.
vin––VIN substring.
wheel_formula––Wheel formula (e.g. '4x2'); auto-resolved to reference id.
NameTypeReqDescription
resultstringyes–

No examples provided.

search_zotts ~205

Search ЗОТТС (vehicle conformity assessment conclusion).

NameTypeReqDescription
axis_count––Axle count (e.g. '2') or exact 'axes / wheels' (e.g. '2 / 4') — auto-resolved to reference id. A bare axle count may match several wheel configs; then candidates are returned to pick from.
brand––Brand.
category––Vehicle category.
eco_class––Ecological class — '5' or name; auto-resolved to reference id.
issuer––Certification body name — auto-resolved to id (or pass numeric id).
number––ЗОТТС number.
pageinteger–1-based page index.
page_sizeinteger–Rows per page (max 50).
type––Type.
vin––VIN substring.
wheel_formula––Wheel formula (e.g. '4x2'); auto-resolved to reference id.
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the su.hpt/hptsu-mcp server?

su.hpt/hptsu-mcp runs locally as a PyPI package, launched with uvx hptsu-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · hptsu-mcp

# add to Claude Code
claude mcp add su-hpt-hptsu-mcp -- uvx hptsu-mcp
Common questions

What is the su.hpt/hptsu-mcp server?

su.hpt/hptsu-mcp is listed in the public MCP registry as su.hpt/hptsu-mcp. Search hpt.su, Russian/EAEU vehicle compliance documents: type approvals, certificates, VIN lookup. This page covers its PyPI package (hptsu-mcp).

Is the su.hpt/hptsu-mcp server safe to use?

su.hpt/hptsu-mcp scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 su.hpt/hptsu-mcp server expose?

su.hpt/hptsu-mcp exposes 21 tools: search_documents, get_document, search_certificates, search_declarations, search_otts, and 16 more. Their descriptions and schemas cost roughly 3,210 tokens of context every time the server is loaded.

Is the su.hpt/hptsu-mcp server still maintained?

su.hpt/hptsu-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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 su.hpt/hptsu-mcp server under?

su.hpt/hptsu-mcp 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 su.hpt/hptsu-mcp server?

VerifyMCP ran 15 checks on su.hpt/hptsu-mcp, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about su.hpt/hptsu-mcp: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.