Server definition
- Hash
- sha256:1dbc64fc8ae694b919f6af20438ce64ec13bdc58db1d7f1752573af8d8d7cb17
- What it is
- What a remote MCP server returned when asked what it offers: 6 tools
The blob, as servednamed by its sha256
{
"instructions": "Scrub a medical claim against the NCCI procedure-to-procedure and medically unlikely edits in force on its date of service, and explain a CARC/RARC denial from a remittance. No model: every answer is a deterministic projection of a cited CMS or X12 dataset, so identical input always returns an identical verdict. A finding or lookup status of no_data means the code or pair was never checked against our dataset - it is NOT a pass, and CMS may still deny a claim on an edit outside our loaded subset. A confidence of \"verify\" means the value could not be confirmed against the official source and must be treated as unverified, not as fact. Every versioned edit carries the CMS quarter it applies to. Procedure codes are referenced numerically only: CPT long descriptors are AMA-copyrighted and are never reproduced here. This is billing and administrative guidance citing CMS or X12 sources - it is not medical advice, not a coverage determination, and not a guarantee of payment. draft_appeal is the one tool that requires a Pro or Scale plan; every other tool is free and keyless, throttled by IP, and an API key only lifts the rate limit.",
"tools": [
{
"description": "Scrub a claim against the NCCI procedure-to-procedure (PTP) edits and medically unlikely edits (MUE) in force on its date of service. Deterministic: no model, so identical input always returns an identical verdict. Every finding.status is one of pass (checked against a real edit and clean), fail (an edit fires), bypassed (an edit fires but a modifier already on the line legitimately resolves it), or no_data (we hold no edit for this code or pair in our dataset). no_data is NOT a pass: treat it as unchecked, since CMS may still deny the line under an edit outside our loaded subset. summary.clean is true only when every finding is pass and none are no_data - never report a claim clean because nothing failed if some lines were never checked. The response echoes editQuarter (the CMS quarter version the verdict was computed against) and coverage (how many PTP pairs and MUE codes are loaded), so you can tell a caller exactly what was checked. Free, no API key needed; a key only raises the rate limit.",
"inputSchema": {
"properties": {
"dateOfService": {
"description": "ISO yyyy-mm-dd, e.g. \"2026-07-01\". Selects which CMS edit quarter applies.",
"format": "date",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"type": "string"
},
"lines": {
"description": "The billed lines on this claim.",
"items": {
"properties": {
"code": {
"description": "CPT/HCPCS code, referenced numerically only, e.g. \"80053\".",
"type": "string"
},
"modifiers": {
"description": "Modifiers on this line, e.g. [\"59\"].",
"items": {
"type": "string"
},
"type": "array"
},
"units": {
"description": "Units billed on this line.",
"minimum": 1,
"type": "integer"
}
},
"required": [
"code",
"units"
],
"type": "object"
},
"maxItems": 500,
"minItems": 1,
"type": "array"
},
"payerSlug": {
"description": "Optional payer slug for context. Does not change the PTP/MUE verdict.",
"type": "string"
}
},
"required": [
"dateOfService",
"lines"
],
"type": "object"
},
"name": "check_claim",
"outputSchema": null
},
{
"description": "Generate an appeal letter for a denial, assembled deterministically from cited facts. REQUIRES A PRO OR SCALE PLAN. Called by an anonymous caller or a key on the free plan, this returns an upgrade_required error naming the pricing page - it never fabricates or partially generates a letter for a caller who cannot access the feature. The letter argues the billing question only: it never asserts anything about the patient's clinical condition. Any fact only the practice holds (providerName, claimNumber, dateOfService, codes, the signature) that is not supplied is rendered as an explicit \"[TO BE COMPLETED BY PRACTICE]\" placeholder in the letter body and listed by name in placeholders, never invented. grounded is true only when we hold the CARC supplied and could argue it with our own corrective-action data; when false, the letter still assembles around payer/claim details and any practiceNote given, but the substantive grounds section is left as a placeholder for the practice to write.",
"inputSchema": {
"properties": {
"carc": {
"description": "CARC code from the remittance, e.g. \"CO-45\" or \"45\".",
"type": "string"
},
"claimNumber": {
"description": "Optional. Rendered as a placeholder if omitted.",
"type": "string"
},
"codes": {
"description": "Optional procedure codes at issue, numeric reference only.",
"items": {
"type": "string"
},
"type": "array"
},
"dateOfService": {
"description": "Optional, ISO yyyy-mm-dd. Rendered as a placeholder if omitted.",
"format": "date",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"type": "string"
},
"payerSlug": {
"description": "Optional payer slug, to cite that payer's appeal policy and window.",
"enum": [
"medicare",
"medicaid",
"aetna",
"cigna",
"unitedhealthcare",
"anthem-bcbs",
"bcbs-general",
"humana",
"kaiser-permanente",
"tricare",
"molina",
"centene-ambetter",
"oscar-health",
"bright-health",
"wellcare",
"highmark",
"horizon-bcbs",
"independence-blue-cross",
"emblemhealth",
"health-net"
],
"type": "string"
},
"practiceNote": {
"description": "Optional free-text detail from the practice, appended to the argument section.",
"type": "string"
},
"providerName": {
"description": "Optional. Rendered as a placeholder if omitted.",
"type": "string"
},
"rarc": {
"description": "Optional RARC codes on the same remittance line.",
"items": {
"type": "string"
},
"type": "array"
}
},
"required": [
"carc"
],
"type": "object"
},
"name": "draft_appeal",
"outputSchema": null
},
{
"description": "Explain a CARC (Claim Adjustment Reason Code) and any RARCs (Remittance Advice Remark Codes) from a remittance: plain meaning, ranked corrective actions, and whether an appeal is worth filing. found:false means we do not hold that CARC in our dataset (X12 publishes far more codes than we have curated) - the response still returns the group-code meaning when a group prefix (CO/PR/OA/PI) was supplied, and note explains the gap rather than leaving it silent. unknownRarc reports, rather than silently drops, any RARC you passed that we do not hold. Passing payer additionally attaches that payer's appeal deadline where we hold one. Free, no API key needed.",
"inputSchema": {
"properties": {
"carc": {
"description": "CARC code, with or without a group prefix, e.g. \"CO-45\" or \"45\".",
"type": "string"
},
"payer": {
"description": "Optional payer slug, to attach a timely-filing appeal deadline.",
"enum": [
"medicare",
"medicaid",
"aetna",
"cigna",
"unitedhealthcare",
"anthem-bcbs",
"bcbs-general",
"humana",
"kaiser-permanente",
"tricare",
"molina",
"centene-ambetter",
"oscar-health",
"bright-health",
"wellcare",
"highmark",
"horizon-bcbs",
"independence-blue-cross",
"emblemhealth",
"health-net"
],
"type": "string"
},
"rarc": {
"description": "Optional RARC codes on the same remittance line.",
"items": {
"type": "string"
},
"type": "array"
}
},
"required": [
"carc"
],
"type": "object"
},
"name": "explain_denial",
"outputSchema": null
},
{
"description": "Look up the medically unlikely edit (MUE) unit limit for a single CPT/HCPCS code. status is found or no_data; no_data means we hold no MUE value for this code in our dataset, not that CMS publishes none. When found, the returned limit.mai (adjudication indicator: \"1\" line edit - denies the excess units on the line; \"2\" date-of-service absolute - never payable above the limit on that date, not even on appeal; \"3\" date-of-service clinical - may be allowed above the limit with supporting documentation) governs what a biller can do above the limit, explained in limit.maiMeaning. Free, no API key needed.",
"inputSchema": {
"properties": {
"code": {
"description": "CPT/HCPCS code, e.g. \"36415\".",
"type": "string"
}
},
"required": [
"code"
],
"type": "object"
},
"name": "get_mue",
"outputSchema": null
},
{
"description": "Look up NCCI procedure-to-procedure (PTP) edits, in two modes. Pair mode: pass column1, column2 (either order) and dateOfService to check whether that specific pair bundles on that date; status is no_data (we hold no edit for this pair in our dataset - NOT confirmation CMS has none), not_applicable (we hold the edit but it does not apply on this date, either outside its effective/deletion window or modifierIndicator \"9\" meaning the edit is deleted or never applicable), or applies. List mode: pass code alone to get every pair in the dataset involving that code, in either column, with no date filtering. modifierIndicator \"0\" means no modifier may ever bypass the edit; \"1\" means a modifier may bypass it, but only where the services were genuinely distinct. Free, no API key needed.",
"inputSchema": {
"oneOf": [
{
"required": [
"column1",
"column2",
"dateOfService"
],
"title": "Pair mode: does this specific pair bundle on this date?"
},
{
"required": [
"code"
],
"title": "List mode: every pair involving this code"
}
],
"properties": {
"code": {
"description": "List mode: a single code. Returns every pair in the dataset involving it, in either column, with no date filtering.",
"type": "string"
},
"column1": {
"description": "Pair mode: a CPT/HCPCS code. Send with column2 and dateOfService. Column order does not matter; the response reports the pair in CMS column order.",
"type": "string"
},
"column2": {
"description": "Pair mode: the other code in the pair.",
"type": "string"
},
"dateOfService": {
"description": "Pair mode, required: ISO yyyy-mm-dd, e.g. \"2026-07-01\". NCCI PTP edits are versioned quarterly, so a pair lookup cannot be answered without a date.",
"format": "date",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"type": "string"
}
},
"type": "object"
},
"name": "get_ncci_edits",
"outputSchema": null
},
{
"description": "Days remaining to file an initial claim (or, if already past, how far over) for a payer given a date of service. daysRemaining and expired are null when we hold no published timely filing limit for that payer, which is common since many limits are contract-specific - check note before treating the result as an actual deadline. Free, no API key needed.",
"inputSchema": {
"properties": {
"dateOfService": {
"description": "ISO yyyy-mm-dd, e.g. \"2026-01-15\".",
"format": "date",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"type": "string"
},
"payer": {
"description": "Payer slug, e.g. \"aetna\".",
"enum": [
"medicare",
"medicaid",
"aetna",
"cigna",
"unitedhealthcare",
"anthem-bcbs",
"bcbs-general",
"humana",
"kaiser-permanente",
"tricare",
"molina",
"centene-ambetter",
"oscar-health",
"bright-health",
"wellcare",
"highmark",
"horizon-bcbs",
"independence-blue-cross",
"emblemhealth",
"health-net"
],
"type": "string"
}
},
"required": [
"payer",
"dateOfService"
],
"type": "object"
},
"name": "get_timely_filing",
"outputSchema": null
}
]
}Verify it yourself
curl -s https://api.teppi.xyz/v1/evidence/sha256:1dbc64fc8ae694b919f6af20438ce64ec13bdc58db1d7f1752573af8d8d7cb17 | sha256sum