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.

Saaskly: B2B software reviews and comparisons

REMOTE · SAASKLY.COM · SCANNED SEP 23

Read-only tools over Saaskly's B2B software reviews: rankings, pricing, comparisons. Public.

Available components

+3 this week 81 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 Security83
Transport & Reachability100
Schema Quality & AI Usability83
  • 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 542 tokens (~60/item across 9 items; 8 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 33% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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 Saaskly: B2B software reviews and comparisons MCP server?

Saaskly: B2B software reviews and comparisons is a hosted endpoint at https://saaskly.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 · saaskly.com

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

  • 23 Sept 26 +1

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

  • 20 Sept 26 +1

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

  • 18 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 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 16 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.

  • 14 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.

  • 11 Sept 26 +1

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

  • 10 Sept 26 0
    • Stability: unverified → 0.03 functional
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 23 Sept 2026 · Probed https://saaskly.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=saaskly.com CN=Certainly Intermediate R1,O=Certainly,C=US 16 Sept 2026 16 Oct 2026 RSA 2048 SHA256-RSA 79b67872d017a590ac69e048fe4b0e2849e9
SANs: saaskly.com, www.saaskly.com
CN=Certainly Intermediate R1,O=Certainly,C=US (CA) CN=Starfield Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 22 Jun 2022 21 Jun 2032 RSA 2048 SHA256-RSA 11831cde4cb573e5

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of saaskly.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
saaskly.com. present 50931 13 Verified
saaskly.com. Verified address RRset verified with the apex keys
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; preload
content-security-policy frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://saaskly.com/mcp Verified 200
http (plaintext) http://saaskly.com/mcp HTTPS enforced 301 https://saaskly.com/mcp
MCP tools · 8 exposed · ~358 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_providers ~56

Side-by-side comparison table (Markdown) for a category, optionally limited to given provider slugs.

NameTypeReqDescription
categorystringyes
slugsarrayLimit to these provider slugs; omit for the whole category

No output schema declared.

No examples provided.

get_article ~39

One article as Markdown (section = comparisons | guides | reviews | news | opinion).

NameTypeReqDescription
sectionstringyes
slugstringyes

No output schema declared.

No examples provided.

get_page ~47

A policy/about page as Markdown: editorial-policy (scoring method), ai-transparency, about, advertise, terms, privacy-policy, cookie-policy, contact.

NameTypeReqDescription
slugstringyes

No output schema declared.

No examples provided.

get_provider ~54

Full review of one provider as Markdown: verdict, pros/cons, month-to-month and annual pricing, spec sheet, disclosure.

NameTypeReqDescription
categorystringyes
slugstringyesProvider slug from list_providers

No output schema declared.

No examples provided.

list_articles ~27

Published comparison articles and buying guides, optionally filtered by category.

NameTypeReqDescription
categorystring

No output schema declared.

No examples provided.

list_categories ~51

List the software categories Saaskly covers, with slugs and how many providers are ranked in each.

NameTypeReqDescription
includeEmptybooleanInclude categories that are still in testing (no ranked providers). Default true.

No output schema declared.

No examples provided.

list_providers ~48

Ranked providers in a category with editorial score (0–5), one-line summary, entry price and partner disclosure.

NameTypeReqDescription
categorystringyesCategory slug
limitinteger

No output schema declared.

No examples provided.

search ~36

Search providers and articles by keyword (name, summary, title). Returns matches with links and .md mirrors.

NameTypeReqDescription
querystringyes

No output schema declared.

No examples provided.

Common questions

What is the Saaskly: B2B software reviews and comparisons MCP server?

Saaskly: B2B software reviews and comparisons is an MCP server listed in the public MCP registry as com.saaskly/mcp. Read-only tools over Saaskly's B2B software reviews: rankings, pricing, comparisons. Public. This page covers its hosted endpoint (https://saaskly.com/mcp).

Is the Saaskly: B2B software reviews and comparisons MCP server safe to use?

Saaskly: B2B software reviews and comparisons scores 81 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 Saaskly: B2B software reviews and comparisons MCP server expose?

Saaskly: B2B software reviews and comparisons exposes 8 tools: list_categories, list_providers, get_provider, compare_providers, search, and 3 more. Their descriptions and schemas cost roughly 358 tokens of context every time the server is loaded.

Does the Saaskly: B2B software reviews and comparisons MCP server require authentication?

No. We connected to Saaskly: B2B software reviews and comparisons without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Saaskly: B2B software reviews and comparisons MCP server still maintained?

Saaskly: B2B software reviews and comparisons is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.