Dorsal

com.godorsalPublished by godorsal.comOfficial publisherv1.3.0Updated Oct 24, 2026

Field evidence for coding agents: what AI builders shipped, broke, and fixed. Dated, source-linked.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Dorsal is a remote MCP server that gives an assistant dated, source-linked field evidence on what AI builders shipped, broke and fixed.

What you can do
Retrieve field evidence about AI builders' work, covering what was shipped, broken and fixed, through the remote Dorsal endpoint. Results are presented as dated entries with links back to their sources. The manifest lists no individual tools, so the exact operations available are not documented here.
When to use it
Useful when an assistant needs grounded, time-stamped examples of real AI-building outcomes, such as researching what shipped or what failed and was fixed, rather than general web results.
Requirements
A remote MCP connection to the Dorsal endpoint over streamable HTTP. OAuth authentication is required, passed as a Bearer token in the Authorization header; a token can be obtained from the provider's anonymous-access endpoint. No local runtime or packages are needed.
Before you install
The server requires an Authorization bearer token, which is a credential and should be kept private. The manifest lists no tools, so what the server can read or change is not documented; review its behavior before relying on it.

Installation

In SourceWeft

  1. Open Dorsal 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/com.godorsal%2Fdorsal/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": {
    "dorsal": {
      "type": "http",
      "url": "https://godorsal.com/api/dorsal"
    }
  }
}

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.3.0LatestSep 16, 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.