Traversal

com.traversalPublished by traversal.comOfficial publisherv0.1.0Updated Nov 7, 2026

AI SRE: investigate production incidents across your observability stack.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote Traversal MCP server that lets an assistant act as an AI SRE, investigating production incidents across your observability stack.

What you can do
  • Investigate production incidents with an AI SRE workflow
  • Work across the observability stack connected to Traversal
  • No tool list is published, so specific actions are not documented here
When to use it
Worth considering when you want an assistant to help triage and investigate production incidents using the observability data already connected to Traversal.
Requirements
A remote endpoint at api.prod.traversal.com over streamable HTTP. A Traversal API key is required, sent as a bearer token in the Authorization header; the key is created in the Traversal app under Settings, API keys.
Before you install
The server requires a Traversal API key sent in the Authorization header, so treat it as a secret. It works over production observability data, and the published description does not state which actions read or change anything, so confirm scope before use.

Installation

In SourceWeft

  1. Open Traversal 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/com.traversal%2Fmcp/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": {
    "traversal": {
      "type": "http",
      "url": "https://api.prod.traversal.com/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. v0.1.0LatestNov 7, 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.