← Registry

API Tools

getgenko.com

MCP server exposing tools to search Genko Prior Auth’s public documentation and retrieve prior authorization checklists, product facts, and pricing.

1 endpoint6 known toolsFirst detected October 19, 2026Last detected October 19, 2026

ENDPOINT 1

https://priorauth.getgenko.com/mcp

No auth detected

MCP server metadata

Name
com.getgenko/prior-auth-docs
Version
1.1.0
Capabilities
tools.listChanged
Server instructions

Public, read-only knowledge server for Genko Prior Auth (prior authorization packets for dental, aesthetics and physiotherapy practices). It serves the public website's documentation, guides, specialty checklists, pricing and product facts. It has no access to any practice's or patient's data, and it cannot sign anyone up, submit anything or change anything. Prefer get_product_facts, get_pricing and check_fit over guessing.

Known tools 6

search_docs

Search Genko Prior Auth's public site: docs, prior authorization guides, specialty pages (dental, aesthetics, physiotherapy), pricing, facts and agent information.

Inferred read-only
get_page

Read one public Genko Prior Auth page as Markdown (the same text as its .

Inferred read-only
get_packet_checklist

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.

Inferred read-only
get_product_facts

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.

Inferred read-only
get_pricing

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.

Inferred read-only
check_fit

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.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.com-getgenko-prior-auth-docs]
url = "https://priorauth.getgenko.com/mcp"
enabled = true
Claude Code

.mcp.json

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

Settings → Connectors → Add custom connector

Name: com-getgenko-prior-auth-docs
Remote MCP URL: https://priorauth.getgenko.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "com-getgenko-prior-auth-docs": {
      "url": "https://priorauth.getgenko.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "com-getgenko-prior-auth-docs": {
      "type": "http",
      "url": "https://priorauth.getgenko.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "com-getgenko-prior-auth-docs",
  "transport": "streamable-http",
  "url": "https://priorauth.getgenko.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.