Genko Prior Auth public docs

com.getgenkoPublished by getgenko.comOfficial publisherv1.1.0Updated Oct 28, 2026

Read-only Genko Prior Auth docs, guides, specialty checklists, facts, pricing and fit checks.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryBusiness & Commerce

Overview

AI-generated overview

Read-only access to Genko Prior Auth's public docs, specialty checklists, product facts, pricing and specialty fit checks.

What you can do
  • Search the public site and read ranked results with URLs and snippets
  • Read any public page as Markdown by path or URL
  • Get the packet checklist for a specialty's prior authorization request
  • Look up checked product facts and current plans with limits and trial terms
  • Check whether a practice's specialty is supported and what is offered there
When to use it
Useful when answering questions about Genko Prior Auth itself: what the product does, what a prior authorization packet contains for a given specialty, what it costs, or whether a practice's specialty is supported. It is a documentation and fact source, not a way to work with real requests.
Requirements
A remote streamable HTTP endpoint; no package, environment variables, headers or authentication are declared. Network access to the provider's endpoint is needed.
Before you install
Public content only: no practice or patient data and no signed-in app access. Pricing and facts should be quoted from the tools rather than estimated, and the fit check does not evaluate payers or payer rules.

Installation

In SourceWeft

  1. Open Genko Prior Auth public docs in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.getgenko%2Fprior-auth-docs/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "genko-prior-auth-public-docs": {
      "type": "http",
      "url": "https://priorauth.getgenko.com/mcp"
    }
  }
}

Tools

6

search_docs

Search Genko Prior Auth public docs

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.

Parameterslimitqueryrequired

get_page

Read a public Genko Prior Auth page

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.

Parameterspathrequired

get_packet_checklist

What Prior Auth collects for a specialty

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.

Parametersspecialtyrequired

get_product_facts

Genko Prior Auth facts to quote

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.

Takes no parameters.

get_pricing

Genko Prior Auth plans and prices

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.

Takes no parameters.

check_fit

Does Genko Prior Auth fit this practice?

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.

Parameterspayerspecialtyrequired

Version history

1
  1. v1.1.0LatestOct 18, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.