GeophysX

net.geophysxPublished by geophysx.netOfficial publisherv1.0.0Updated Nov 7, 2026

Well log analysis: import LAS/DLIS, run petrophysics, build log plots and reports in the browser

VerifiedStreamable HTTPWeb executableFiles & StorageData & Analytics

Overview

AI-generated overview

Remote MCP server for well log analysis: import LAS/DLIS logs, run petrophysics, and build log plots and reports in the browser.

What you can do
  • Import well log data from LAS and DLIS files
  • Run petrophysics calculations on the imported logs
  • Build log plots and reports from the results
  • Work inside the geophysx.net web app, which must stay open in a browser tab while tools run
When to use it
Useful for geoscientists and engineers who want an assistant to help with petrophysical well log workflows — loading LAS/DLIS data, computing petrophysics, and producing plots and reports — without leaving the GeophysX web app.
Requirements
A remote streamable HTTP endpoint at geophysx.net, with no local package. A bearer token passed in the Authorization header, obtained from the geophysx.net Settings under AI agents (MCP). The geophysx.net/app page must be open in a browser tab for the tools to run.
Before you install
The Authorization header carries a secret bearer token; keep it private and revoke it if exposed. Tools operate through the open geophysx.net/app browser session, so the assistant acts within that account's data. No tool list is published, so review what the tools can change before use.

Installation

In SourceWeft

  1. Open GeophysX in the dashboard and add it to a workspace.
  2. Connect Authorization token 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.geophysx%2Fgeophysx/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.

{
  "mcpServers": {
    "geophysx": {
      "type": "http",
      "url": "https://www.geophysx.net/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestNov 7, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.