Skip to content
Jaxon logo

Jaxon MCP server

Which MCP servers are Jaxon's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-17

← Back to Jaxon

Whose server it is
  • Registry nameai.jaxon/dsailverified in the MCP registry

The registry name sits under jaxon.ai. 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-17
  • Staterequires sign-inchecked 2026-10-17

On 2026-10-17 the server answered and asked for a sign-in with a Jaxon account (OAuth). It shows its tool list only to signed-in users, so we list none here.

Should an agent connect itNot proven either way yet

    Once connected

    • Signs in by OAuth: the client opens the sign-in on first connect.

    Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

    Measured dailydaily checks: 8, the first on 2026-10-19
    • INITE MCP score81 of 100answers 100 · use 35
    • Use55 PyPI downloads a week9 GitHub stars
    • Answered100% of days8 of 8 daily checks
    • Median first answer249 ms
    • Sign-inOAuth: the client signs you in

    A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

    How to connect

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

    {
  "mcpServers": {
    "dsail": {
      "type": "http",
      "url": "https://agents.jaxon.ai/mcp"
    }
  }
}

    Add it

    Claude Code, in a terminal

    claude mcp add --transport http jaxon https://agents.jaxon.ai/mcp

    Add to CursorAdd to VS Code

    claude.ai, ChatGPT and other clients: add https://agents.jaxon.ai/mcp as a custom connector in the settings.

    The first time it connects, the client opens a Jaxon sign-in.

    Also shipped through: pypi

    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.