Final POS Docs
io.github.Final-Commerce/final-docs
Search the Final POS REST API documentation.
— the operator's own registry description reported
Publisher io.github.Final-Commerce · first seen 2026-08-12 · endpoint https://docs.finalpos.com/mcp
Dependency rating derived
Cluster mid-shared · distinctiveness 0.131 (typical). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.
🔏 Signed receipt rr_afaebac1111329f938a22b95 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.
What kind of tools these are derived
Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. This server's 6 tools, classified, with what checking applies to each kind (the full methodology →):
| nature | tools | meaning | what checking applies |
|---|---|---|---|
| retrieval-public | 6 | serves public facts | truth-checkable against a public source — the V-ladder applies in full |
Tools last seen
Harness readiness observed
Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.
| legibility check | tools passing | ok |
|---|---|---|
| name is clear & specific | 6/6 | ✓ |
| has a description | 6/6 | ✓ |
| description is substantive | 4/6 | 4/6 |
| parameters are typed | 6/6 | ✓ |
| parameters are described | 6/6 | ✓ |
6 of 6 tools graded · 6 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.
Truth checks observed
Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.
Protocol conformance observed
Capabilities: logging tools
Drift
No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.
History observed
Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.
changelog (1 events)
| date | type | what changed |
|---|---|---|
| 2026-08-12 | outcome | first probe: ok_tools |
raw probe records
| probed (UTC) | outcome | http | ms | protocol |
|---|---|---|---|---|
| 2026-08-14T19:59:01Z | ok_tools | 200 | 159 | 2025-06-18 |
| 2026-08-12T05:34:15Z | ok_tools | 200 | 87 | 2025-06-18 |
Watch or embed this verdict
Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:
[](https://robinsaige.com/s/io.github.Final-Commerce/final-docs)
Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.