Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Software Sausage Recipe Finder

REMOTE · SOFTWARESAUSAGE.COM · SCANNED SEP 20

Find source-linked AI tool recipes and retrieve complete, reproducible run kits.

+3 this week 70 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 714 tokens (~34/item across 21 items; 2 tools + 19 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Software Sausage Recipe Finder MCP server?

Software Sausage Recipe Finder is a hosted endpoint at https://softwaresausage.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · softwaresausage.com

# add to Claude Code
claude mcp add --transport http pinkpwningclub-recipes 'https://softwaresausage.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "pinkpwningclub-recipes": {
      "url": "https://softwaresausage.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "pinkpwningclub-recipes": {
      "type": "http",
      "url": "https://softwaresausage.com/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.pinkpwningclub-recipes]
url = "https://softwaresausage.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pinkpwningclub-recipes": {
      "type": "remote",
      "url": "https://softwaresausage.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add pinkpwningclub-recipes --url 'https://softwaresausage.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  pinkpwningclub-recipes:
    url: "https://softwaresausage.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "pinkpwningclub-recipes": {
      "Transport": "http",
      "Url": "https://softwaresausage.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add pinkpwningclub-recipes -t streamable-http -u 'https://softwaresausage.com/api/mcp'
// mcp.json
{
  "mcpServers": {
    "pinkpwningclub-recipes": {
      "type": "http",
      "url": "https://softwaresausage.com/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1
    • Stability: unverified → 0.03 functional
  • 10 Sept 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://softwaresausage.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=softwaresausage.com CN=WE1,O=Google Trust Services,C=US 3 Sept 2026 2 Dec 2026 ECDSA 256 ECDSA-SHA256 94575224bec2da140e1173ef62917e74
SANs: softwaresausage.com, www.softwaresausage.com, *.www.softwaresausage.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of softwaresausage.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
softwaresausage.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://softwaresausage.com/api/mcp Verified 200
http (plaintext) http://softwaresausage.com/api/mcp HTTPS enforced 301 https://softwaresausage.com/api/mcp
MCP tools · 2 exposed · ~80 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
find_agent_recipes ~43

Find read-only, job-focused agent workflows with roles, checks, safety boundaries, source links, and a complete MCP resource URI.

NameTypeReqDescription
querystringyes

No output schema declared.

No examples provided.

search_software ~37

Find commercial and open-source software options from the Software Sausage editorial catalog. Results are not paid rankings.

NameTypeReqDescription
querystringyes

No output schema declared.

No examples provided.

Common questions

What is the Software Sausage Recipe Finder MCP server?

Software Sausage Recipe Finder is an MCP server listed in the public MCP registry as io.github.pinkpwningclub/recipes. Find source-linked AI tool recipes and retrieve complete, reproducible run kits. This page covers its hosted endpoint (https://softwaresausage.com/api/mcp).

Is the Software Sausage Recipe Finder MCP server safe to use?

Software Sausage Recipe Finder scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Software Sausage Recipe Finder MCP server expose?

Software Sausage Recipe Finder exposes 2 tools: search_software, find_agent_recipes. Their descriptions and schemas cost roughly 80 tokens of context every time the server is loaded.

Does the Software Sausage Recipe Finder MCP server require authentication?

No. We connected to Software Sausage Recipe Finder without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Software Sausage Recipe Finder MCP server still maintained?

Software Sausage Recipe Finder is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.