Online store and commerce
foxyio
foxyio was answering at the last check. Checked on 2026-10-04 (daily check).
Read Foxy transactions, subscriptions, customers, carts and coupons; update customers and subs.
Agents use servers like this to search products, build carts and place orders.
12 read-only0 change data2 high risk
https://foxyio.usefulapi.io/mcp
Follow (RSS): status changes, tool-list changes, new advisories and owner verification, in any feed reader.
Tools
14 tools: 12 read-only, 0 change data, 2 high risk (delete, pay, send or run code).
1 tool can move money or change orders; they are listed first.
- read-only
- Only reads or looks things up. Safe for an agent to call on its own.
- changes data
- Creates, edits or sends something. Worth a person's approval the first time.
- high risk
- Can delete, pay, send on your behalf or run code. Hard or impossible to undo.
Connecting costs an agent about 2,723 tokens of tool definitions and a 256 ms handshake.
- high risk
foxy_update_subscriptionmoves money or changes ordersUPDATES a subscription - reschedule its next run (next_transaction_date), change its frequency, or activate/pause it (is_active). This MODIFIES live store data and affects future billing. Foxy hAPI: PATCH /subscriptions/{id}. Provide only the fields you want to change. - high risk
foxy_update_customerUPDATES a customer's profile fields (first_name, last_name, email). This MODIFIES live store data. Foxy hAPI: PATCH /customers/{id}. Provide only the fields you want to change. - read-only
foxy_get_api_homeGet the Foxy hAPI home document - its _links / rels (including fx:store for the authenticated default store). Useful for HAL discovery. Foxy hAPI: GET /. - read-only
foxy_get_default_storeResolve and return the authenticated user's default store (and its id) by fetching the API home and following the fx:store link. Use this to discover the store_id the list tools accept. Foxy hAPI: GET / then GET fx:store. - read-only
foxy_get_storeGet a single store resource by id, including its settings and _links to sub-collections. Foxy hAPI: GET /stores/{store_id}. - read-only
foxy_list_transactionsList a store's transactions (orders), newest first. Returns a HAL collection embedding fx:transactions. Foxy hAPI: GET /stores/{store_id}/transactions. - read-only
foxy_get_transactionGet a single transaction by id, optionally zooming related resources (items, customer, payments, applied_taxes…). Foxy hAPI: GET /transactions/{id}. - read-only
foxy_list_subscriptionsList a store's subscriptions (recurring orders). Returns a HAL collection embedding fx:subscriptions. Foxy hAPI: GET /stores/{store_id}/subscriptions. - read-only
foxy_get_subscriptionGet a single subscription by id, optionally zooming related resources. Foxy hAPI: GET /subscriptions/{id}. - read-only
foxy_list_customersList a store's customers. Returns a HAL collection embedding fx:customers. Foxy hAPI: GET /stores/{store_id}/customers. - read-only
foxy_get_customerGet a single customer by id, optionally zooming related resources (default_billing_address, subscriptions…). Foxy hAPI: GET /customers/{id}. - read-only
foxy_list_cartsList a store's carts (in-progress / abandoned checkouts). Returns a HAL collection embedding fx:carts. Foxy hAPI: GET /stores/{store_id}/carts. - read-only
foxy_list_couponsList a store's coupons (discount codes and their rules). Returns a HAL collection embedding fx:coupons. Foxy hAPI: GET /stores/{store_id}/coupons. - read-only
foxy_list_itemsList the line items of a transaction (the products purchased). Returns a HAL collection embedding fx:items. Foxy hAPI: GET /transactions/{transaction_id}/items.
Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.
Trust and supply chain
No owner has verified this server yet.
No tool change since tracking began on 2026-10-04.
Status
Newest check: answered with tools, from the daily check, 2026-10-04, 256 ms.
From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.
Last 30 days
2026-09-052026-10-04
answered with toolssign-in or payment askednot answeringnot checked
Compare: the most reliable servers in Online store and commerce, ranked by days answering.
Badge
Live: status, days reachable, the tokens its tool list costs an agent. For a README:
[](https://7it.co.il/7maps/s/foxyio.usefulapi.io/mcp)
Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).
Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=foxyio.usefulapi.io%2Fmcp (add the same &style= for another style).
Own this server? Verify that it is yours.
Status widget
A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.
Script (renders where it is placed, in its own shadow DOM):
<script src="https://7it.co.il/7maps/widget/foxyio.usefulapi.io/mcp.js" async></script>
Or an iframe:
<iframe src="https://7it.co.il/7maps/widget/foxyio.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>
The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=foxyio.usefulapi.io%2Fmcp.
Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.
For AI agents
Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.
7Maps by 7IT maps the MCP servers AI agents use, from public listings. Observations with a date, not a judgement. Methodology · How we collect, and opting out.