Salvo

com.sendsalvoPublished by sendsalvo.comOfficial publisherv1.0.0Updated Oct 24, 2026

Job applications done for you: check applications and interviews, get prep, apply to a job by URL.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote MCP server that lets an assistant check job applications and interviews, get interview prep, and apply to a job by URL.

What you can do
Salvo connects an assistant to a job-application service. According to the description, it can check the status of applications and interviews, provide interview preparation, and submit an application to a job given by its URL. The manifest lists no individual tools, so the exact tool set is not documented here.
When to use it
Useful when you are actively job hunting and want an assistant to track where your applications and interviews stand, prepare for interviews, or submit an application from a job posting link.
Requirements
A remote streamable HTTP endpoint at sendsalvo.com; no local package or runtime is needed. Authentication is OAuth and is required, so you need a Salvo account and must complete the OAuth sign-in. No environment variables or headers are declared.
Before you install
The server can submit job applications on your behalf, which is a real-world action taken with your identity and details; review what will be sent before letting it apply. It also holds your application and interview data, and OAuth grants it access to your Salvo account.

Installation

In SourceWeft

  1. Open Salvo 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.sendsalvo%2Fsalvo/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": {
    "salvo": {
      "type": "http",
      "url": "https://sendsalvo.com/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 16, 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.