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.

TitanStore Commerce MCP

REMOTE · SATI-SEARCH.FLY.DEV · SCANNED SEP 20

MCP commerce surface for compute credits, API keys, GPU instances, and cloud storage.

0 this week 75 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 Security57
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 327 tokens (~65/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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 TitanStore Commerce MCP server?

TitanStore Commerce MCP is a hosted endpoint at https://sati-search.fly.dev/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 · sati-search.fly.dev

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

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
  • 23 Aug 26 +1

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

  • 11 Aug 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
  • 7 Aug 26 0
    • The server no longer declares the “experimental” capability functional
  • 31 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
  • 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
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://sati-search.fly.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.fly.dev CN=YE1,O=Let's Encrypt,C=US 21 Aug 2026 19 Nov 2026 ECDSA 256 ECDSA-SHA384 688c4daf5300c51e0a5c1f6837a3a67a868
SANs: *.fly.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of sati-search.fly.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
fly.dev. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://sati-search.fly.dev/mcp Verified 200
http (plaintext) http://sati-search.fly.dev/mcp HTTPS enforced 301 https://sati-search.fly.dev/mcp
MCP tools · 5 exposed · ~261 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
add_to_cart ~49

Add a TitanStore product to your cart and receive a cart token. Requires a valid SKU. Returns cart_token needed for checkout.

NameTypeReqDescription
quantityinteger
skustringyes

Structured output declared, but exposes no named fields.

No examples provided.

checkout ~51

Initiate checkout for a cart. Provide cart_token from add_to_cart and a billing email. Returns a payment_token required to complete the purchase.

NameTypeReqDescription
cart_tokenstringyes
emailstringyes

Structured output declared, but exposes no named fields.

No examples provided.

confirm_payment ~53

Confirm payment using a payment_token from checkout and a cc_token (credit card token). Completes the TitanStore purchase and returns an order confirmation.

NameTypeReqDescription
cc_tokenstringyes
payment_tokenstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_product ~50

Retrieve full details for a TitanStore product by SKU. Example SKUs: TS-001, TS-002, TS-003, TS-004, TS-005.

NameTypeReqDescription
skustringyes

Structured output declared, but exposes no named fields.

No examples provided.

search_products ~58

Search TitanStore product catalog. Returns matching compute credits, API keys, storage, GPU instances, and support plans. Filter by category: compute, api_access, storage, gpu, support.

NameTypeReqDescription
category
querystringyes

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the TitanStore Commerce MCP server?

TitanStore Commerce MCP is listed in the public MCP registry as io.github.Fish-Tacos/titan-store. MCP commerce surface for compute credits, API keys, GPU instances, and cloud storage. This page covers its hosted endpoint (https://sati-search.fly.dev/mcp).

Is the TitanStore Commerce MCP server safe to use?

TitanStore Commerce MCP scores 75 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 TitanStore Commerce MCP server expose?

TitanStore Commerce MCP exposes 5 tools: search_products, get_product, add_to_cart, checkout, confirm_payment. Their descriptions and schemas cost roughly 261 tokens of context every time the server is loaded.

Does the TitanStore Commerce MCP server require authentication?

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

Is the TitanStore Commerce MCP server still maintained?

TitanStore Commerce MCP 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.