Genko Prior Auth public docs
REMOTE · PRIORAUTH.GETGENKO.COM
Read-only Genko Prior Auth docs, guides, specialty checklists, facts, pricing and fit checks.
Available components
Last scanned (7 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 661 tokens (~110/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://priorauth.getgenko.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=priorauth.getgenko.com | CN=YR2,O=Let's Encrypt,C=US | 14 Oct 2026 | 12 Jan 2027 | RSA 2048 | SHA256-RSA | 5dda5f00da625f16f1f9a3410ce3bbd2524 |
| SANs: priorauth.getgenko.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of priorauth.getgenko.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| getgenko.com. | 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://priorauth.getgenko.com/mcp | Verified | 200 | |
| http (plaintext) | http://priorauth.getgenko.com/mcp | HTTPS enforced | 308 | https://priorauth.getgenko.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 →
check_fit Does Genko Prior Auth fit this practice? ~123
Say whether Genko Prior Auth supports a practice's specialty (own form, general form, or not supported) and what it offers there, from what the product implements. A payer can be given, but the product does not evaluate payers or payer rules, and the answer says so.
| Name | Type | Req | Description |
|---|---|---|---|
| payer | string | – | Optional payer name. The product does not evaluate payers; the answer says so. |
| specialty | string | yes | The practice's specialty in plain words, e.g. 'dental', 'physical therapy', 'aesthetics', 'optometry'. |
| Name | Type | Req | Description |
|---|---|---|---|
| caveats | array | yes | – |
| fit | string | yes | dedicated = own code lists and findings form; generic_form = general form; not_supported = no |
| next_step | string | yes | – |
| page_url | string|null | yes | – |
| payer | – | yes | – |
| specialty | – | yes | – |
| summary | string | yes | – |
| what_it_offers | array | yes | – |
No examples provided.
get_packet_checklist What Prior Auth collects for a specialty ~90
What Genko Prior Auth collects for a prior authorization request in a specialty (dental, aesthetics, physiotherapy, or the generic form): request details, structured-findings fields and choices, and code systems. Useful for 'what goes in a packet'. No patient data, no code descriptors.
| Name | Type | Req | Description |
|---|---|---|---|
| specialty | string | yes | Practice type. 'generic' is the form every other practice type uses. |
| Name | Type | Req | Description |
|---|---|---|---|
| code_areas | object | yes | – |
| label | string | yes | – |
| page_url | string|null | yes | – |
| request_records | array | yes | – |
| specialty | string | yes | – |
| structured_findings | object | yes | – |
No examples provided.
get_page Read a public Genko Prior Auth page ~113
Read one public Genko Prior Auth page as Markdown (the same text as its .md version), by path or URL, e.g. '/pricing', '/facts', '/docs/faq'. Public pages only; the signed-in app is never available.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Public page path, e.g. '/', '/docs/faq', '/guides/what-is-prior-authorization', '/specialties/dental', '/pricing'. A '.md' suffix or a full URL on this site also works. |
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | – |
| path | string | yes | – |
| url | string | yes | – |
No examples provided.
get_pricing Genko Prior Auth plans and prices ~55
Current Genko Prior Auth plans in US dollars per practice per month, with each plan's monthly draft and AI-token limits and the free trial's terms. Use this to answer 'how much does it cost'; never estimate prices.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | – |
| draft_definition | string | yes | – |
| how_to_start | string | yes | – |
| plans | array | yes | – |
| trial | object | yes | – |
| updated | string | yes | Date the prices were last confirmed against the billing database (YYYY-MM-DD) |
| url | string | yes | – |
No examples provided.
get_product_facts Genko Prior Auth facts to quote ~65
Checked facts about Genko Prior Auth: what it is and isn't, who it's for, stage, specialties, how payers are handled, security, limits, pricing and what exists for agents. Same source as /facts and /facts.json. Quote these instead of guessing.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| facts | array | yes | – |
| json_url | string | yes | – |
| not_yet | array | yes | – |
| payers | object | yes | – |
| pricing | object | yes | – |
| security | array | yes | – |
| source_url | string | yes | – |
| specialties | object | yes | – |
| updated | string | yes | Date the facts were last checked (YYYY-MM-DD) |
| what_it_is | string | yes | – |
| what_it_is_not | array | yes | – |
No examples provided.
search_docs Search Genko Prior Auth public docs ~129
Search Genko Prior Auth's public site: docs, prior authorization guides, specialty pages (dental, aesthetics, physiotherapy), pricing, facts and agent information. Returns up to 10 ranked pages with URL and snippet; read one in full with get_page. Public content only, no practice or patient data.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Most results to return (1-10, default 5). |
| query | string | yes | What to look for, in plain words, e.g. 'appeal a denied physiotherapy request', 'dental crown', 'how much does it cost'. |
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| results | array | yes | – |
No examples provided.
How do I install the Genko Prior Auth public docs MCP server?
Genko Prior Auth public docs is a hosted endpoint at https://priorauth.getgenko.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 · priorauth.getgenko.com
claude mcp add --transport http com-getgenko-prior-auth-docs 'https://priorauth.getgenko.com/mcp'
What is the Genko Prior Auth public docs MCP server?
Genko Prior Auth public docs is an MCP server listed in the public MCP registry as com.getgenko/prior-auth-docs. Read-only Genko Prior Auth docs, guides, specialty checklists, facts, pricing and fit checks. This page covers its hosted endpoint (https://priorauth.getgenko.com/mcp).
Is the Genko Prior Auth public docs MCP server safe to use?
Genko Prior Auth public docs scores 82 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 Genko Prior Auth public docs MCP server expose?
Genko Prior Auth public docs exposes 6 tools: search_docs, get_page, get_packet_checklist, get_product_facts, get_pricing, check_fit. Their descriptions and schemas cost roughly 575 tokens of context every time the server is loaded.
Does the Genko Prior Auth public docs MCP server require authentication?
No. We connected to Genko Prior Auth public docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Genko Prior Auth public docs MCP server still maintained?
Genko Prior Auth public docs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.