Final POS Docs
REMOTE · DOCS.FINALPOS.COM · SCANNED SEP 7
Search the Final POS REST API documentation.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Final POS Docs MCP server?
Final POS Docs is a hosted endpoint at https://docs.finalpos.com/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 · docs.finalpos.com
claude mcp add --transport http final-commerce-final-docs 'https://docs.finalpos.com/mcp'
{
"mcpServers": {
"final-commerce-final-docs": {
"url": "https://docs.finalpos.com/mcp"
}
}
} {
"servers": {
"final-commerce-final-docs": {
"type": "http",
"url": "https://docs.finalpos.com/mcp"
}
}
} [mcp_servers.final-commerce-final-docs] url = "https://docs.finalpos.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"final-commerce-final-docs": {
"type": "remote",
"url": "https://docs.finalpos.com/mcp",
"enabled": true
}
}
} openclaw mcp add final-commerce-final-docs --url 'https://docs.finalpos.com/mcp' --transport streamable-http
mcp_servers:
final-commerce-final-docs:
url: "https://docs.finalpos.com/mcp" {
"McpServers": {
"final-commerce-final-docs": {
"Transport": "http",
"Url": "https://docs.finalpos.com/mcp"
}
}
} assistant mcp add final-commerce-final-docs -t streamable-http -u 'https://docs.finalpos.com/mcp'
{
"mcpServers": {
"final-commerce-final-docs": {
"type": "http",
"url": "https://docs.finalpos.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.
- 7 Sept 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 6 Sept 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 5 Sept 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 4 Sept 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Sept 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 1 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Aug 26 0
- Server version: 2026-08-30 → 2026-08-31 functional
- 30 Aug 26 0
- Server version: 2026-08-29 → 2026-08-30 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 7 Sept 2026 · Probed https://docs.finalpos.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=docs.finalpos.com | CN=YE1,O=Let's Encrypt,C=US | 30 Jul 2026 | 28 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 597554953edbf05b0560e46c24175f24eab |
| SANs: docs.finalpos.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 docs.finalpos.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| finalpos.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://docs.finalpos.com/mcp | Unreachable | ||
| http (plaintext) | http://docs.finalpos.com/mcp | HTTPS enforced | 308 | https://docs.finalpos.com/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 →
get-endpoint-info ~92
Get comprehensive information about specific endpoint including parameters, security, and examples
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | yes | HTTP method (GET, POST, PUT, DELETE, etc.) |
| name | string | yes | API name |
| path | string | yes | Endpoint path (e.g. /api/v1/users) |
| version | string | – | API version (required when multiple APIs share the same name but differ by version) |
No output schema declared.
No examples provided.
get-endpoints ~48
Get all endpoints for a specific API
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | API name |
| version | string | – | API version (required when multiple APIs share the same name but differ by version) |
No output schema declared.
No examples provided.
get-full-api-description ~48
Get the complete OpenAPI description
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | API name |
| version | string | – | API version (required when multiple APIs share the same name but differ by version) |
No output schema declared.
No examples provided.
get-security-schemes ~51
Get the security schemes for a specific API
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | API name |
| version | string | – | API version (required when multiple APIs share the same name but differ by version) |
No output schema declared.
No examples provided.
list-apis ~58
Lists available APIs with their context and purpose
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | API name (or part of it) |
| limit | number | – | Number of APIs per page. Default is 300 |
| page | number | – | Page number |
No output schema declared.
No examples provided.
search ~44
Search across the documentation to fetch relevant content for a given query
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query. Should be a single word or that phrase that is presented in a documentation. |
No output schema declared.
No examples provided.
What is the Final POS Docs MCP server?
Final POS Docs is an MCP server listed in the public MCP registry as io.github.Final-Commerce/final-docs. Search the Final POS REST API documentation. This page covers its hosted endpoint (https://docs.finalpos.com/mcp).
Is the Final POS Docs MCP server safe to use?
Final POS Docs scores 0 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 Final POS Docs MCP server expose?
Final POS Docs exposes 6 tools: list-apis, get-endpoints, get-endpoint-info, get-security-schemes, get-full-api-description, search. Their descriptions and schemas cost roughly 341 tokens of context every time the server is loaded.
Does the Final POS Docs MCP server require authentication?
Its publisher declares no required credentials for Final POS Docs. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Final POS Docs MCP server still maintained?
Final POS Docs has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 31 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.