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.

SaaS Puppy

REMOTE · SAASPUPPY.COM · 2 COMPONENTS

Look up or compare free-tier developer tools, with the catch spelled out.

74 Trust /100

Last scanned (3 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Developer Tools

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 Security80
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 410 tokens (~205/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
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 current MCP spec version (2026-07-28).Pass
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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +5
    • Tool “list_tools” rewrote its description, which is the text the model reads security
    • Schema quality: 156 → 205 ▼ functional
    • Tool coverage: 0% → 100% ▲ functional
    • Schema quality: fair → good functional
    • “list_tools” reworded the description of “query” cosmetic
    • “compare_tools” reworded the description of “slugs” cosmetic
    • “list_tools” reworded the description of “pricing_models” cosmetic
    • “list_tools” reworded the description of “category” cosmetic
  • 1 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 31 Oct 26 67

    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 5 Nov 2026 · Probed https://saaspuppy.com/MCP

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=saaspuppy.com CN=WE1,O=Google Trust Services,C=US 21 Oct 2026 19 Jan 2027 ECDSA 256 ECDSA-SHA256 38ae2a9ce3456f381399fd0ebd8f917a
SANs: saaspuppy.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 saaspuppy.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
saaspuppy.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
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://saaspuppy.com/MCP Verified 200
http (plaintext) http://saaspuppy.com/MCP HTTPS enforced 301 https://saaspuppy.com/MCP
MCP tools · 2 exposed · ~208 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
compare_tools ~66

Compare short purpose, quota, pros, cons and catch summaries for two or three tools in one category; full details remain on SaaS Puppy.

NameTypeReqDescription
slugsarrayyesTwo or three tool slugs from the same category, for example ["supabase", "neon"].

No output schema declared.

No examples provided.

list_tools ~142

Summarize one exact tool name or slug, or up to three examples from a specific category. Use this to check one tool's free plan; to compare tools, use compare_tools. No bulk exports, pagination or full records; visit SaaS Puppy for more.

NameTypeReqDescription
categorystring–Category to sample, for example "hosting". Returns at most three examples.
pricing_modelsarray–Optional filters: free-forever, free-trial, open-source, self-hosted.
querystring–Exact tool name or slug, for example "Neon" or "cloudflare-turnstile". Leave empty to sample a category.

No output schema declared.

No examples provided.

Install

How do I install the SaaS Puppy MCP server?

SaaS Puppy is a hosted endpoint at https://saaspuppy.com/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 · saaspuppy.com

# add to Claude Code
claude mcp add --transport http rahulparathy-saas-puppy 'https://saaspuppy.com/MCP'
Common questions

What is the SaaS Puppy MCP server?

SaaS Puppy is an MCP server listed in the public MCP registry as io.github.rahulparathy/saas-puppy. Look up or compare free-tier developer tools, with the catch spelled out. This page covers its hosted endpoint (https://saaspuppy.com/MCP).

Is the SaaS Puppy MCP server safe to use?

SaaS Puppy scores 74 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 SaaS Puppy MCP server expose?

SaaS Puppy exposes 2 tools: list_tools, compare_tools. Their descriptions and schemas cost roughly 208 tokens of context every time the server is loaded.

Does the SaaS Puppy MCP server require authentication?

No. We connected to SaaS Puppy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SaaS Puppy MCP server still maintained?

SaaS Puppy is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.