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

StratoForce AI Revenue Intelligence

REMOTE · STRATOFORCE-MCP.STRATOFORCE.WORKERS.DEV · SCANNED AUG 3

15 AI revenue intelligence tools for Salesforce — pipeline, deals, coaching, competitors.

Available components

remote · stratoforce-mcp.stratoforce.workers.dev 31
+12 this week 31 Trust /100
Trust breakdown (6 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 →

Endpoint Security77
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · stratoforce-mcp.stratoforce.workers.dev

# add to Claude Code
claude mcp add --transport http tgomolski-lgtm-revenue-intelligence https://stratoforce-mcp.stratoforce.workers.dev/mcp
# ~/.codex/config.toml
[mcp_servers.tgomolski-lgtm-revenue-intelligence]
url = "https://stratoforce-mcp.stratoforce.workers.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tgomolski-lgtm-revenue-intelligence": {
      "type": "remote",
      "url": "https://stratoforce-mcp.stratoforce.workers.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add tgomolski-lgtm-revenue-intelligence --url https://stratoforce-mcp.stratoforce.workers.dev/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  tgomolski-lgtm-revenue-intelligence:
    url: "https://stratoforce-mcp.stratoforce.workers.dev/mcp"
// mcp.json
{
  "mcpServers": {
    "tgomolski-lgtm-revenue-intelligence": {
      "type": "http",
      "url": "https://stratoforce-mcp.stratoforce.workers.dev/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.

  • 31 Jul 26 +12
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 19

    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 3 Aug 2026 · Probed https://stratoforce-mcp.stratoforce.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=stratoforce.workers.dev CN=YE2,O=Let's Encrypt,C=US 24 Jun 2026 22 Sept 2026 ECDSA 256 ECDSA-SHA384 5c356e5fbec8a6595658696d66ab2c57146
SANs: *.stratoforce.workers.dev, stratoforce.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of stratoforce-mcp.stratoforce.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On connection
HTTP status 401
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY

Protected resource metadata

Retrieved No
Problem no_resource_metadata
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://stratoforce-mcp.stratoforce.workers.dev/mcp Auth required 401
http (plaintext) http://stratoforce-mcp.stratoforce.workers.dev/mcp Served over HTTP 200
MCP tools

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.

No tool schema has been captured from this endpoint yet.