Skip to content
Own vs Charter logo

Own vs Charter MCP server

Which servers in the official MCP registry are Own vs Charter's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to Own vs Charter

Whose server it is
  • Registry namecom.ownvscharter/siteverified in the MCP registry

The registry name sits under ownvscharter.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13
  • Stateanswerschecked 2026-10-13
  • Tools6
  • Server calls itselfOwn vs Charter (ownvscharter.com)
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 909 ms.

Tools it offers6 tools · read 2026-10-13
  • checker_start

    The first question of the Own, fractional, jet card or charter decision guide.

  • checker_answer

    Given a question id and the chosen option (its `choice` index), return the next question or the final verdict.

  • checker_tree

    Every question, option and verdict of the Own, fractional, jet card or charter guide, for reasoning end to end.

  • enquiry_describe

    Read first. States plainly what submit_enquiry does on Own vs Charter: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the…

  • enquiry_fields

    Every field of the Own vs Charter enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.

  • submit_enquiry

    Submits an enquiry to Own vs Charter — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "site": {
      "type": "http",
      "url": "https://ownvscharter.com/mcp"
    }
  }
}

OpenAPI spec

7 paths, read 2026-10-13. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.