Optical Dispense Record
GOC-compliant optical dispense record validation. Captures prescription, lens choice, fitting measurements, supplier traceability for UK opticians.
Install
pip install dispense-record-mcp
Tools
| Tool | Purpose |
|---|---|
validate_dispense_record |
GOC requirements check on a dispense record |
rx_transcription_check |
Catch common Rx transcription errors (sphere/cylinder/axis) |
lens_suitability |
Lens type suitability against prescription + lifestyle |
supplier_traceability |
Lens/frame batch + supplier traceability |
flag_dispensing_complaint_risk |
Common dispense-complaint triggers |
Built by a UK practitioner
Nicholas Templeman runs an active UK optical practice (templeman-opticians.com) + AI compliance company. This MCP encodes lessons from real workflows, not paperwork theory.
Pricing
- Free: 10 calls/day. No API key.
- Pro £79/mo: unlimited + signed attestations. Subscribe
- Enterprise £1,499/mo: white-label + on-premise. hello@meok.ai
License
MIT © MEOK AI Labs
💸 Try MEOK in 30 seconds — instant buy ladder
| Tier | Price | What you get | Stripe |
|---|---|---|---|
| Smoke test | £1 | Signed sample MCP-Hardening report + Article 50 PDF | https://buy.stripe.com/aFa7sNcgAdQS0ZT1Uc8k91t |
| Quick Kit | £9 | EU AI Act Article 50 implementation guide (C2PA + EU-Icon) | https://buy.stripe.com/aFa7sNcgAdQS0ZT1Uc8k91t |
| Founder Call | £29 | 30-min 1-on-1 with the founder | https://buy.stripe.com/aFa7sNcgAdQS0ZT1Uc8k91t |
Refundable. UK Stripe — VAT-clean. Builds on the 81-MCP MEOK fleet. Verify any signed report at https://meok.ai/verify.
Configuration
Add to your claude_desktop_config.json (Claude Desktop) or your MCP client config:
{
"mcpServers": {
"dispense-record-mcp": {
"command": "uvx",
"args": ["dispense-record-mcp"]
}
}
}
Or: pip install dispense-record-mcp then run the dispense-record-mcp command (stdio transport).
Examples
Once configured, ask your assistant, for example:
- "Use
validate_dispense_recordto …" - "Use
rx_transcription_checkto …" - "Use
lens_suitabilityto …"
1 maintainer
Metadata
1 maintainer
Release files for dispense-record-mcp 1.0.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| dispense_record_mcp-1.0.9.tar.gz | 10.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dispense_record_mcp-1.0.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.1 kB
Release files / dispense_record_mcp-1.0.9.tar.gz
| Download URL | dispense_record_mcp-1.0.9.tar.gz |
|---|---|
| Size | 10.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
04c14a12c1c91b797714ebc01723cca31a4fb55d6e690104addaf723346be817
|
|
BLAKE2b-256 checksum How to use checksums |
89b283f1f363a75197eb9aa5d9083dec0c5146daa8bd1de4ac466c4df36d4142
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Release files / dispense_record_mcp-1.0.9-py3-none-any.whl
| Download URL | dispense_record_mcp-1.0.9-py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4845811e58b4ab57de5cd95f4c7304738e33c6ce4a138e173517b259b147cd17
|
|
BLAKE2b-256 checksum How to use checksums |
84dcbd88c0cba2907b73bd8ffb2342e6b8443ba69e5cb27edcdbc258cdddd827
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for dispense-record-mcp 1.0.9
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
