Oxynet

net.oxynetPublished by oxynet.netOfficial publisherv1.0.0Updated Oct 30, 2026

Cardiopulmonary exercise test (CPET) analysis: ventilatory thresholds, metrics and substrate use.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Remote Oxynet MCP server that lets an assistant work with cardiopulmonary exercise test (CPET) analysis, including ventilatory thresholds, metrics and…

What you can do
  • Analyze cardiopulmonary exercise test (CPET) data.
  • Derive ventilatory thresholds from test results.
  • Report exercise metrics and substrate use.
  • No tool list is published, so the exact operations are not documented.
When to use it
Useful when an assistant needs to interpret or discuss CPET results, such as thresholds, exercise metrics or substrate utilization, for sports, clinical or research work.
Requirements
A remote MCP endpoint at app.oxynet.net over streamable HTTP, with OAuth sign-in required. No packages, environment variables or headers are declared.
Before you install
OAuth access to an Oxynet account is required, so the assistant acts with that account's permissions. CPET data is health-related and may be sensitive; confirm what is shared with the service before uploading test data. The tool set is not published, so review the granted scopes after connecting.

Installation

In SourceWeft

  1. Open Oxynet in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/net.oxynet%2Fcpet/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "oxynet": {
      "type": "http",
      "url": "https://app.oxynet.net/oxynet-mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 30, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.