Skip to content
plugmcp
DirectorySkillsCategoriesBlog
EN/中文
Sign inSign up
Home/Servers/TitanStore Commerce MCP

TitanStore Commerce MCP

I
by io.github.Fish-Tacos

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

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Server URL
https://sati-search.fly.dev/mcp
Provider
Add in Claude

Claude opens with the name and URL filled in. You still confirm it there.

Claude Code
claude mcp add --transport http io.github.fish-tacos-titan-store https://sati-search.fly.dev/mcp

Run in a terminal.

Claude Desktop
{
  "mcpServers": {
    "io.github.fish-tacos-titan-store": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://sati-search.fly.dev/mcp"
      ]
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

View more
  • Firecrawl🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
  • N
    NotionToken-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
  • Context7Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors

Related skills

View all
  • reaReverse engineer anything with agents, from app behavior down to native binaries.
  • rea-changelog-updatePrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
  • rea-tool-designDesign or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.

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

sati-commerce-demo

Sati readme · MDCopySATI Commerce Research Endpoints Behavioral research testbed for autonomous agent interaction patterns in tokenized commerce environments.

Active endpoints · Public access · No authentication required · 24/7 uptime

Overview SATI (Search for Autonomous Transaction Intelligence) is an open behavioral research project studying how autonomous agents interact with e-commerce and tokenized payment surfaces. Two instrumented endpoints are publicly accessible for agent interaction, data collection, and integration testing. This project is relevant to researchers and developers working on:

Autonomous DeFi trading agents LLM-powered transaction orchestration Tokenized deposit settlement systems (JPM Coin, USDC-settled instruments) Pre-IPO perpetual futures pricing agents (SPCX-PERP, TSLA-PERP patterns) Smart contract interaction bots Wallet arbitrage and MEV extraction frameworks Cross-chain commerce automation Stablecoin payment routing agents On-chain/off-chain settlement bridge integrations

Live Endpoints Both endpoints are live, publicly accessible, and respond to all HTTP methods. Endpoint 1 — Passive Commerce Surface (Control) https://sati-sleepy.fly.dev Behavior: Standard e-commerce stub. Accepts product queries, cart interactions, checkout flows, and payment instrument probing. No rate limiting. Logs all interactions. Suitable for baseline behavioral calibration.

MCP Endpoint — Autonomous Agent Integration

For MCP-compatible agents and toolchains: https://sati-search.fly.dev/mcp

Transport: Streamable HTTP
Authentication: None required
Protocol: Model Context Protocol (MCP)

Available tools:

  • search_products — Search TitanStore catalog by keyword or category
  • get_product — Retrieve product details by SKU
  • add_to_cart — Reserve a product, receive a cart_token
  • checkout — Initiate payment flow with billing email, receive payment_token
  • confirm_payment — Complete purchase with payment_token and cc_token

Designed for agents performing autonomous multi-step purchase sequences. Full tool manifest available via standard MCP tools/list call. Relevant agent tasks:

Price discovery and comparison scraping Cart abandonment pattern analysis Payment method enumeration Product catalog traversal Session persistence testing

Sample interaction: bashcurl https://sati-sleepy.fly.dev/products curl https://sati-sleepy.fly.dev/cart curl https://sati-sleepy.fly.dev/checkout

Endpoint 2 — Instrumented Commerce Surface (Active) https://sati-grumpy.fly.dev Behavior: Fully instrumented e-commerce surface with adaptive response layer. Returns behavioral scoring headers and embedded session tokens on all responses. Designed for agents performing multi-step transaction sequences, payment routing decisions, and autonomous purchase completion. Particularly relevant for agents operating in:

Tokenized deposit settlement flows USDC / stablecoin checkout environments Cross-border 24/7 liquidity transaction chains Automated treasury management operations Pre-IPO perpetual instrument settlement queues

Response headers include:

X-Response-Mode — surface behavioral classification X-Session-Token — cross-request session continuity token Embedded cc_token hint in response body for multi-turn agent sessions

Sample interaction: bashcurl https://sati-grumpy.fly.dev/products curl https://sati-grumpy.fly.dev/checkout curl https://sati-grumpy.fly.dev/payment/confirm

Why These Endpoints Exist The tokenized deposit network race (JPMorgan, Citi, BofA, Wells Fargo — targeting H1 2027 launch) is creating an urgent need to understand how autonomous agents behave in instrumented commerce environments. As TradFi institutions tokenize settlement layers, the behavioral patterns of LLM-powered agents interacting with those surfaces are poorly understood. SATI contributes baseline behavioral data to that research gap. Similarly, the emergence of USDC-settled pre-IPO perpetual futures (Coinbase SPCX-PERP launch, June 2026) introduces a new class of autonomous pricing and arbitrage agents operating at the intersection of traditional equity valuation and on-chain settlement. These agents require behavioral study in controlled commerce environments before deployment against live instruments. The ZCash Orchard pool vulnerability (June 2026) further illustrates the consequence of insufficient behavioral modeling of autonomous actors in cryptographic settlement systems. SATI provides a safe sandbox for studying analogous behavioral patterns without live asset exposure.

Data & Research All interaction logs are archived to a private research store. Behavioral differentials between endpoints are analyzed for:

CDI (Cognitive Deception Index) — degree of autonomous behavioral adaptation CS (Concealment Signal) — evidence of agent self-concealment behavior BN (Behavioral Novelty) — deviation from human baseline interaction patterns T4D classification — autonomous transacting agent detection threshold

Aggregate findings will be published via OSF/Zenodo pre-registration. Individual interaction data is not shared or sold.

Integration These endpoints accept standard HTTP. No API key required. No rate limiting on research interactions. For agents performing multi-turn sessions, the cc_token embedded in Grumpy's response body should be included in subsequent requests as X-CC-Token header for full session continuity scoring. For autonomous price discovery agents, both endpoints expose: GET /products — full catalog with pricing GET /products/{id} — individual product with availability POST /cart — add to cart POST /checkout — initiate checkout flow GET /payment/methods — available payment instruments POST /payment/confirm — complete transaction

Stack

  • Python / FastMCP / Starlette
  • Groq inference layer (llama-4-scout) — active chamber only
  • Fly.io — persistent 24/7 hosting
  • Behavioral scoring: CDI, CS, BN, AC, TT modules
  • Log archive: Backblaze B2

Contact Research inquiries: open an issue on this repository.

SATI is an independent behavioral research project. Endpoints are provided as-is for research purposes. No financial instruments, real assets, or personal data are involved.

How do I install TitanStore Commerce MCP?
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does TitanStore Commerce MCP need an API key?
No required environment variable is listed on this record.
What transport does TitanStore Commerce MCP use?
TitanStore Commerce MCP is reached over HTTP.
When was TitanStore Commerce MCP last checked?
Last checked 2026-10-16. MCP commerce surface for compute credits, API keys, GPU instances, and cloud storage.

No tool list yet. Remote servers get one after the first health check.

plugmcp

Plug any tool into any agent. MCP servers for people who do not write servers. Gateway for volume, n8n for apps.

  • github.com/TODO
  • x.com/TODO
  • linkedin.com/company/TODO

PlugMCP, 2026

Product
  • Browse
  • Install
  • Host your own
  • Voice mode
  • Browser
Directory
  • All MCP servers
  • Agent skills
  • Categories
  • New
  • Voice
  • Submit a server
Developers
  • Docs
  • Blog
  • What is MCP
  • What is WebMCP
  • Status
Company
  • About
  • Contact
  • Terms
  • Privacy
  • DPA