hptsu MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HPTSU_API_KEY | Yes | Bearer key from hpt.su cabinet. | |
| HPTSU_TIMEOUT | No | Per-request HTTP timeout (s). | 30.0 |
| HPTSU_BASE_URL | No | Override for staging / on-prem deployments. | https://hpt.su/api/v1 |
| HPTSU_LOG_LEVEL | No | Standard logging levels. | INFO |
| HPTSU_TRANSPORT | No | stdio · streamable-http · sse. | stdio |
| HPTSU_USER_AGENT | No | User-Agent header. | hptsu-mcp/0.1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_documentsB | Cross-registry search by document number across all hpt.su kinds. |
| get_documentA | Fetch a single Document by slug+kind. |
| search_certificatesC | Search conformity certificates (ТР ТС / ТР ЕАЭС). |
| search_declarationsB | Search declarations of conformity (ТР ТС / ТР ЕАЭС). |
| search_ottsC | Search ОТТС (vehicle type approvals, ТР ТС 018/2011). |
| search_otchC | Search ОТШ (chassis type approvals). |
| search_zottsC | Search ЗОТТС (vehicle conformity assessment conclusion). |
| search_zotchC | Search ЗОТШ (chassis conformity assessment conclusion). |
| search_sbktsC | Search СБКТС (vehicle safety certificate). |
| search_zoetsC | Search ЗОЕТС (vehicle technical expertise conclusion). |
| search_soutB | Search СУТ (vehicle type notification — small dataset, only basic fields). |
| search_by_vinA | Aggregated search by VIN across all car-kinds (ОТТС/ОТШ/ЗОТТС/ЗОТШ/ СБКТС/ЗОЕТС). Open for any active API key — no subscription required. Returns substring matches via UNION across kind-tables sorted by
|
| fulltext_searchA | Full-text search inside type-approval document bodies (PDF text). Covers ОТТС / ОТШ / ЗОТТС / ЗОТШ — kinds where Premium feature — requires a paid MCP key with |
| list_document_filesA | List the files attached to a document. Returns A document often has several PDFs (e.g. cleaned + original); use this tool to enumerate them and pick the right one before download. |
| download_document_fileA | Issue a signed URL to download the document PDF from hpt.su. Returns Requires an active subscription covering the document's kind or a stand-alone DOC_PURCHASE. On the free tier returns 403 with an upgrade prompt to https://hpt.su/pricing/. |
| list_brandsB | Resolve a vehicle brand name to its canonical record (used to filter type approvals). |
| list_vehicle_modelsC | Resolve a vehicle model name (within a brand) to canonical record. |
| list_test_labsB | Lookup accredited testing laboratories (issuers of СБКТС/ЗОЕТС). |
| list_certification_bodiesA | Lookup accredited certification bodies (issuers of сертификатов/деклараций). |
| list_tnved_codesA | TN VED EAEU classifier lookup. Note: TN VED codes are linked only to certificates and declarations — not to vehicle type approvals or safety reports. |
| list_registry_kindsB | Return the catalogue of registry kinds exposed by the hpt.su public API. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| about_registry |
TDQS
Scored across 21 tools
Each tool has a clearly distinct purpose: list tools for reference data, search tools for specific document kinds or aggregated searches, and document retrieval tools. No two tools overlap in functionality, and descriptions make the differences clear.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., search_otts, list_brands, download_document_file). The verbs are consistently 'search', 'list', 'get', 'download', and 'fulltext' as a modifier. No mixing of conventions.
With 21 tools, the set is slightly large but justifiable given the many document kinds and search methods. Each tool addresses a specific need, and the number is within a reasonable range for such a comprehensive data retrieval server.
The tool surface covers the full lifecycle of document discovery: reference lookup (brands, models, labs, etc.), multiple search modalities (by VIN, document number, fulltext, per-kind), file listing, and download. No obvious gaps for a read-oriented API.