Server definition

Hash: sha256:90c4625fb13978d6b5bf2078c63da66f55ccc980d5b4dc4a094da5228ed5c581
What it is: What a remote MCP server returned when asked what it offers: 3 tools

The blob, as servednamed by its sha256

{
  "instructions": "Three read-only tools. discover_domain: what a domain publishes (the raw normalized list). connect_domain: given a domain AND your client's capabilities, HOW to connect — one outcome (ready | credentials-required | incomplete | broken | no-compatible-method) with a connection plan, or the exact missing field. check_readiness: per-endpoint readiness for a domain, client-agnostic. All read the domain live, store no discovered domain or resource data, make no ownership/safety claim; credentials stay with the caller.",
  "tools": [
    {
      "description": "Given a domain, return each connectable resource it publishes with a readiness assessment (ready | credentials-required | incomplete | broken, with the exact missing field) read from the service's own metadata. Client-agnostic; read-only. Use connect_domain when you know the client's capabilities.",
      "inputSchema": {
        "properties": {
          "domain": {
            "description": "Registrable domain, e.g. example.com",
            "type": "string"
          }
        },
        "required": [
          "domain"
        ],
        "type": "object"
      },
      "name": "check_readiness",
      "outputSchema": null
    },
    {
      "description": "Given a domain AND the calling client's capabilities, return HOW the client can connect: one outcome (ready | credentials-required | incomplete | broken | no-compatible-method) with a connection plan (protocol, endpoint, transport, version, and the auth metadata the service published — e.g. the OAuth authorize/token endpoints and scopes), or the exact missing field when the service under-publishes. Deterministic matching, no scores. Read-only; credentials stay with the caller and are never sent to NessGate.",
      "inputSchema": {
        "properties": {
          "client": {
            "description": "The calling client's capabilities. Omit a dimension to accept any. If client/supports is omitted entirely, a broad default (mcp, openapi, a2a) is assumed and the response carries clientAssumed:true.",
            "properties": {
              "prefer": {
                "description": "Optional cross-protocol tie-break order.",
                "items": {
                  "type": "string"
                },
                "type": "array"
              },
              "supports": {
                "description": "Protocols the client speaks, each optionally narrowing versions/transports/auth.",
                "items": {
                  "properties": {
                    "auth": {
                      "items": {
                        "type": "string"
                      },
                      "type": "array"
                    },
                    "protocol": {
                      "description": "e.g. mcp, openapi, a2a",
                      "type": "string"
                    },
                    "transports": {
                      "items": {
                        "type": "string"
                      },
                      "type": "array"
                    },
                    "versions": {
                      "items": {
                        "type": "string"
                      },
                      "type": "array"
                    }
                  },
                  "required": [
                    "protocol"
                  ],
                  "type": "object"
                },
                "type": "array"
              }
            },
            "type": "object"
          },
          "domain": {
            "description": "Registrable domain, e.g. example.com",
            "type": "string"
          }
        },
        "required": [
          "domain"
        ],
        "type": "object"
      },
      "name": "connect_domain",
      "outputSchema": null
    },
    {
      "description": "Given a domain, read whatever it publishes at the standard machine-discovery locations (llms.txt, /.well-known/ard.json, /.well-known/agent-card.json, /.well-known/api-catalog, ai-info.json, openapi.json, and more) and return one normalized answer. Each resource keeps a sourceUrl pointing back to the domain so the caller can verify. NessGate reads the domain live and stores no discovered domain or resource data; it makes no ownership or safety claim.",
      "inputSchema": {
        "properties": {
          "domain": {
            "description": "Registrable domain, e.g. example.com",
            "type": "string"
          }
        },
        "required": [
          "domain"
        ],
        "type": "object"
      },
      "name": "discover_domain",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:90c4625fb13978d6b5bf2078c63da66f55ccc980d5b4dc4a094da5228ed5c581 | sha256sum