su.hpt/hptsu-mcp
REMOTE · MCP.HPT.SU · 2 COMPONENTS · SCANNED SEP 21
Search hpt.su — Russian/EAEU vehicle compliance documents: type approvals, certificates, VIN lookup.
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 → Why this is hard to score →
Endpoint Security63
- 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 21 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 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 3352 tokens (~152/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
How do I install the su.hpt/hptsu-mcp server?
su.hpt/hptsu-mcp is a hosted endpoint at https://mcp.hpt.su/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 · mcp.hpt.su
claude mcp add --transport http su-hpt-hptsu-mcp 'https://mcp.hpt.su/mcp'
{
"mcpServers": {
"su-hpt-hptsu-mcp": {
"url": "https://mcp.hpt.su/mcp"
}
}
} {
"servers": {
"su-hpt-hptsu-mcp": {
"type": "http",
"url": "https://mcp.hpt.su/mcp"
}
}
} [mcp_servers.su-hpt-hptsu-mcp] url = "https://mcp.hpt.su/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"su-hpt-hptsu-mcp": {
"type": "remote",
"url": "https://mcp.hpt.su/mcp",
"enabled": true
}
}
} openclaw mcp add su-hpt-hptsu-mcp --url 'https://mcp.hpt.su/mcp' --transport streamable-http
mcp_servers:
su-hpt-hptsu-mcp:
url: "https://mcp.hpt.su/mcp" {
"McpServers": {
"su-hpt-hptsu-mcp": {
"Transport": "http",
"Url": "https://mcp.hpt.su/mcp"
}
}
} assistant mcp add su-hpt-hptsu-mcp -t streamable-http -u 'https://mcp.hpt.su/mcp'
{
"mcpServers": {
"su-hpt-hptsu-mcp": {
"type": "http",
"url": "https://mcp.hpt.su/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.
- 26 Aug 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
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 20 Aug 26 0
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 21 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- 19 Aug 26 0
- TLS certificate: pass → 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
- 11 Aug 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
- 9 Aug 26 0
- Tool “download_document_file” rewrote its description, which is the text the model reads security
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 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
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 Sept 2026 · Probed https://mcp.hpt.su/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.hpt.su | CN=YE2,O=Let's Encrypt,C=US | 24 Jul 2026 | 22 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5225dd39d98a7444e5f7985c9e3f6aa568c |
| SANs: *.hpt.su, hpt.su | ||||||
| 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 mcp.hpt.su. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| su. | present | 42982 | 8 | Verified |
| hpt.su. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.hpt.su/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.hpt.su/mcp | HTTPS enforced | 301 | https://mcp.hpt.su/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 →
download_document_file ~224
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.
| Name | Type | Req | Description |
|---|---|---|---|
| file_uid | string | yes | DocumentFile UID (from list_document_files). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
fulltext_search ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | – | – | Filter by registry kind. One of: otts, otch, zotts, zotch. Default: search across all 4 type-approval kinds. |
| page | integer | – | 1-based page index. |
| page_size | integer | – | Rows per page (max 50). |
| query | string | yes | Free-text query (Russian, tsquery-syntax allowed). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_document ~86
Fetch a single Document by slug+kind.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | One of: otts, otch, zotts, zotch, sbkts, zoets, sout, cert, decl. Slug isn't globally unique between kinds, so kind is required. |
| slug | string | yes | Document slug — URL-form of the number (the same as in site URL). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_brands ~70
Resolve a vehicle brand name to its canonical record (used to filter type approvals).
| Name | Type | Req | Description |
|---|---|---|---|
| name | – | – | Brand name substring (e.g. 'KAMAZ'). |
| page | integer | – | 1-based page index. |
| page_size | integer | – | Rows per page (max 50). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_certification_bodies ~62
Lookup accredited certification bodies (issuers of сертификатов/деклараций).
| Name | Type | Req | Description |
|---|---|---|---|
| name | – | – | Body name substring. |
| page | integer | – | 1-based page index. |
| page_size | integer | – | Rows per page (max 50). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_document_files ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| document_slug | string | yes | Document slug (from search.slug field). |
| kind | string | yes | One of: otts, otch, zotts, zotch, sbkts, zoets, sout, cert, decl. Slug isn't globally unique between kinds, so kind is required. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_test_labs ~66
Lookup accredited testing laboratories (issuers of СБКТС/ЗОЕТС).
| Name | Type | Req | Description |
|---|---|---|---|
| name | – | – | Lab name, full or partial. |
| page | integer | – | 1-based page index. |
| page_size | integer | – | Rows per page (max 50). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_tnved_codes ~101
TN VED EAEU classifier lookup. Note: TN VED codes are linked **only** to certificates and declarations — not to vehicle type approvals or safety reports.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page index. |
| page_size | integer | – | Rows per page (max 50). |
| prefix | – | – | TN VED code prefix (e.g. '8704'). |
| query | – | – | Free-text description search. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_vehicle_models ~76
Resolve a vehicle model name (within a brand) to canonical record.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | – | – | Brand name (auto-resolved to id) or numeric brand id. |
| name | – | – | Model name substring. |
| page | integer | – | 1-based page index. |
| page_size | integer | – | Rows per page (max 50). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_by_vin ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| vin | string | yes | VIN substring or full code (5-17 chars). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_certificates ~153
Search conformity certificates (ТР ТС / ТР ЕАЭС).
| Name | Type | Req | Description |
|---|---|---|---|
| applicant | – | – | Applicant name, full or partial. |
| applicant_inn | – | – | Applicant INN (exact match). |
| manufacturer | – | – | Manufacturer name, full or partial. |
| number | – | – | Certificate number, full or partial. |
| page | integer | – | 1-based page index. |
| page_size | integer | – | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_declarations ~154
Search declarations of conformity (ТР ТС / ТР ЕАЭС).
| Name | Type | Req | Description |
|---|---|---|---|
| applicant | – | – | Applicant name, full or partial. |
| applicant_inn | – | – | Applicant INN (exact match). |
| manufacturer | – | – | Manufacturer name, full or partial. |
| number | – | – | Declaration number, full or partial. |
| page | integer | – | 1-based page index. |
| page_size | integer | – | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_documents ~61
Cross-registry search by document number across all hpt.su kinds.
| Name | Type | Req | Description |
|---|---|---|---|
| number | – | – | Document number, full or partial. |
| page | integer | – | 1-based page index. |
| page_size | integer | – | Rows per page (max 50). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_otch ~222
Search ОТШ (chassis type approvals).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| page | integer | – | 1-based page index. |
| page_size | integer | – | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_otts ~293
Search ОТТС (vehicle type approvals, ТР ТС 018/2011).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| page | integer | – | 1-based page index. |
| page_size | integer | – | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_sbkts ~354
Search СБКТС (vehicle safety certificate).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| page | integer | – | 1-based page index. |
| page_size | integer | – | 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). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_sout ~73
Search СУТ (vehicle type notification — small dataset, only basic fields).
| Name | Type | Req | Description |
|---|---|---|---|
| brand | – | – | Brand. |
| number | – | – | СУТ number. |
| page | integer | – | 1-based page index. |
| page_size | integer | – | Rows per page (max 50). |
| type | – | – | Type. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_zoets ~335
Search ЗОЕТС (vehicle technical expertise conclusion).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| page | integer | – | 1-based page index. |
| page_size | integer | – | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_zotch ~206
Search ЗОТШ (chassis conformity assessment conclusion).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| page | integer | – | 1-based page index. |
| page_size | integer | – | Rows per page (max 50). |
| type | – | – | Type. |
| vin | – | – | VIN substring. |
| wheel_formula | – | – | Wheel formula (e.g. '4x2'); auto-resolved to reference id. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_zotts ~205
Search ЗОТТС (vehicle conformity assessment conclusion).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| page | integer | – | 1-based page index. |
| page_size | integer | – | Rows per page (max 50). |
| type | – | – | Type. |
| vin | – | – | VIN substring. |
| wheel_formula | – | – | Wheel formula (e.g. '4x2'); auto-resolved to reference id. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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 hosted endpoint (https://mcp.hpt.su/mcp).
Is the su.hpt/hptsu-mcp server safe to use?
su.hpt/hptsu-mcp scores 75 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 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,240 tokens of context every time the server is loaded.
Does the su.hpt/hptsu-mcp server require authentication?
No. We connected to su.hpt/hptsu-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.