io.github.Fish-Tacos/sati-grumpy
REMOTE · SATI-GRUMPY.FLY.DEV
MCP commerce surface for refurbished datacenter hardware, with x402 agent-payment discovery.
Available components
Last scanned (1 hour ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 350 tokens (~70/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 current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 0
- Stability: pass → 0.97 functional
- 12 Oct 26 0
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 3.4.7 → 4.1.0 functional
- Tool “add_to_cart” changed its title: Add To Cart cosmetic
- Tool “checkout” changed its title: Checkout cosmetic
- Tool “confirm_payment” changed its title: Confirm Payment cosmetic
- Tool “get_product” changed its title: Get Product cosmetic
- Tool “search_products” changed its title: Search Products cosmetic
- 3 Oct 26 +48
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Tool coverage: unverified → 100 ▲ functional
- 2 Oct 26 27
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 28 Sept 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
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://sati-grumpy.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 | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5e6e25e6df778e81cd07b85fc9f12d4df7d |
| 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-grumpy.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-grumpy.fly.dev/mcp | Verified | 200 | |
| http (plaintext) | http://sati-grumpy.fly.dev/mcp | HTTPS enforced | 301 | https://sati-grumpy.fly.dev/mcp |
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 →
add_to_cart Add To Cart ~52
Add a Salvage & Surplus product to your cart and receive a cart token. Requires a valid SKU. Returns cart_token needed for checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| quantity | integer | – | – |
| sku | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
checkout 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.
| Name | Type | Req | Description |
|---|---|---|---|
| cart_token | string | yes | – |
| string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
confirm_payment Confirm Payment ~56
Confirm payment using a payment_token from checkout and a cc_token (credit card token). Completes the Salvage & Surplus purchase and returns an order confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| cc_token | string | yes | – |
| payment_token | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_product Get Product ~53
Retrieve full details for a Salvage & Surplus product by SKU. Example SKUs: GR-001, GR-002, GR-003, GR-004, GR-005.
| Name | Type | Req | Description |
|---|---|---|---|
| sku | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_products Search Products ~58
Search Salvage & Surplus product catalog. Returns matching GPU rigs, server racks, drive arrays, and network gear. Filter by category: compute, servers, storage, networking, support.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.Fish-Tacos/sati-grumpy MCP server?
io.github.Fish-Tacos/sati-grumpy is a hosted endpoint at https://sati-grumpy.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-grumpy.fly.dev
claude mcp add --transport http fish-tacos-sati-grumpy 'https://sati-grumpy.fly.dev/mcp'
What is the io.github.Fish-Tacos/sati-grumpy MCP server?
io.github.Fish-Tacos/sati-grumpy is an MCP server listed in the public MCP registry as io.github.Fish-Tacos/sati-grumpy. MCP commerce surface for refurbished datacenter hardware, with x402 agent-payment discovery. This page covers its hosted endpoint (https://sati-grumpy.fly.dev/mcp).
Is the io.github.Fish-Tacos/sati-grumpy MCP server safe to use?
io.github.Fish-Tacos/sati-grumpy 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 io.github.Fish-Tacos/sati-grumpy MCP server expose?
io.github.Fish-Tacos/sati-grumpy exposes 5 tools: search_products, get_product, add_to_cart, checkout, confirm_payment. Their descriptions and schemas cost roughly 270 tokens of context every time the server is loaded.
Does the io.github.Fish-Tacos/sati-grumpy MCP server require authentication?
No. We connected to io.github.Fish-Tacos/sati-grumpy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.Fish-Tacos/sati-grumpy MCP server still maintained?
io.github.Fish-Tacos/sati-grumpy 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.