io.usefulapi/foxyio
REMOTE · FOXYIO.USEFULAPI.IO · SCANNED SEP 21
Read Foxy transactions, subscriptions, customers, carts and coupons; update customers and subs.
Available components
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1362 tokens (~97/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/foxyio MCP server?
io.usefulapi/foxyio is a hosted endpoint at https://foxyio.usefulapi.io/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 · foxyio.usefulapi.io
claude mcp add --transport http io-usefulapi-foxyio 'https://foxyio.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-foxyio": {
"url": "https://foxyio.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-foxyio": {
"type": "http",
"url": "https://foxyio.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-foxyio] url = "https://foxyio.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-foxyio": {
"type": "remote",
"url": "https://foxyio.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-foxyio --url 'https://foxyio.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-foxyio:
url: "https://foxyio.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-foxyio": {
"Transport": "http",
"Url": "https://foxyio.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-foxyio -t streamable-http -u 'https://foxyio.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-foxyio": {
"type": "http",
"url": "https://foxyio.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −11
- Stability: pass → 0.17 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Sept 2026 · Probed https://foxyio.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 3c65503452c8cd3c0e1a9c967a73ca7a |
| SANs: usefulapi.io, foxyio.usefulapi.io, *.foxyio.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of foxyio.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://foxyio.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://foxyio.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://foxyio.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://foxyio.usefulapi.io/mcp |
| Authorisation server | https://foxyio.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://foxyio.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://foxyio.usefulapi.io/mcp | Inconclusive | 401 |
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 →
foxy_get_api_home Get API home ~50
Get the Foxy hAPI home document — its _links / rels (including fx:store for the authenticated default store). Useful for HAL discovery. Foxy hAPI: GET /.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
foxy_get_customer Get customer ~62
Get a single customer by id, optionally zooming related resources (default_billing_address, subscriptions…). Foxy hAPI: GET /customers/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | Customer id. |
| zoom | string | – | Comma-separated related resources to embed. |
No output schema declared.
No examples provided.
foxy_get_default_store Get default store ~62
Resolve 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
foxy_get_store Get store ~58
Get a single store resource by id, including its settings and _links to sub-collections. Foxy hAPI: GET /stores/{store_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| store_id | – | yes | Store id (get it from foxy_get_default_store). |
No output schema declared.
No examples provided.
foxy_get_subscription Get subscription ~65
Get a single subscription by id, optionally zooming related resources. Foxy hAPI: GET /subscriptions/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | Subscription id. |
| zoom | string | – | Comma-separated related resources to embed, e.g. 'transaction_template,original_transaction'. |
No output schema declared.
No examples provided.
foxy_get_transaction Get transaction ~73
Get a single transaction by id, optionally zooming related resources (items, customer, payments, applied_taxes…). Foxy hAPI: GET /transactions/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | Transaction id. |
| zoom | string | – | Comma-separated related resources to embed, e.g. 'items,customer'. |
No output schema declared.
No examples provided.
foxy_list_carts List carts ~118
List a store's carts (in-progress / abandoned checkouts). Returns a HAL collection embedding fx:carts. Foxy hAPI: GET /stores/{store_id}/carts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results per page (Foxy default 20). |
| offset | integer | – | Pagination offset. |
| store_id | – | – | Store id. If omitted, the default store (fx:store) is used. |
| zoom | string | – | Comma-separated related resources to embed, e.g. 'items,customer'. |
No output schema declared.
No examples provided.
foxy_list_coupons List coupons ~118
List a store's coupons (discount codes and their rules). Returns a HAL collection embedding fx:coupons. Foxy hAPI: GET /stores/{store_id}/coupons.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results per page (Foxy default 20). |
| offset | integer | – | Pagination offset. |
| store_id | – | – | Store id. If omitted, the default store (fx:store) is used. |
| zoom | string | – | Comma-separated related resources to embed, e.g. 'coupon_codes'. |
No output schema declared.
No examples provided.
foxy_list_customers List customers ~100
List a store's customers. Returns a HAL collection embedding fx:customers. Foxy hAPI: GET /stores/{store_id}/customers.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Filter by exact customer email. | |
| limit | integer | – | Max results per page (Foxy default 20). |
| offset | integer | – | Pagination offset. |
| store_id | – | – | Store id. If omitted, the default store (fx:store) is used. |
No output schema declared.
No examples provided.
foxy_list_items List transaction items ~105
List the line items of a transaction (the products purchased). Returns a HAL collection embedding fx:items. Foxy hAPI: GET /transactions/{transaction_id}/items.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results per page (Foxy default 20). |
| offset | integer | – | Pagination offset. |
| transaction_id | – | yes | Transaction id whose line items to list. |
| zoom | string | – | Comma-separated related resources to embed, e.g. 'item_options'. |
No output schema declared.
No examples provided.
foxy_list_subscriptions List subscriptions ~135
List a store's subscriptions (recurring orders). Returns a HAL collection embedding fx:subscriptions. Foxy hAPI: GET /stores/{store_id}/subscriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| is_active | boolean | – | Filter to active (true) or inactive (false) subscriptions. |
| limit | integer | – | Max results per page (Foxy default 20). |
| offset | integer | – | Pagination offset. |
| store_id | – | – | Store id. If omitted, the default store (fx:store) is used. |
| zoom | string | – | Comma-separated related resources to embed, e.g. 'transaction_template,last_transaction'. |
No output schema declared.
No examples provided.
foxy_list_transactions List transactions ~169
List a store's transactions (orders), newest first. Returns a HAL collection embedding fx:transactions. Foxy hAPI: GET /stores/{store_id}/transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_email | string | – | Filter by the transaction's customer email. |
| is_test | boolean | – | Filter to test (true) or live (false) transactions. |
| limit | integer | – | Max results per page (Foxy default 20). |
| offset | integer | – | Pagination offset. |
| order | string | – | Sort expression, e.g. 'transaction_date desc'. |
| store_id | – | – | Store id. If omitted, the default store (fx:store) is used. |
| zoom | string | – | Comma-separated related resources to embed, e.g. 'items,customer,payments'. |
No output schema declared.
No examples provided.
foxy_update_customer Update customer ~94
UPDATES 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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | New email address. | |
| first_name | string | – | New first name. |
| id | – | yes | Customer id to update. |
| last_name | string | – | New last name. |
No output schema declared.
No examples provided.
foxy_update_subscription Update subscription ~153
UPDATES 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.
| Name | Type | Req | Description |
|---|---|---|---|
| frequency | string | – | Billing frequency, e.g. '1m' (monthly), '2w' (2 weeks), '1y' (yearly). |
| id | – | yes | Subscription id to update. |
| is_active | boolean | – | Set true to activate or false to pause the subscription. |
| next_transaction_date | string | – | Next run date, YYYY-MM-DD (reschedules the subscription). |
No output schema declared.
No examples provided.
What is the io.usefulapi/foxyio MCP server?
io.usefulapi/foxyio is an MCP server listed in the public MCP registry as io.usefulapi/foxyio. Read Foxy transactions, subscriptions, customers, carts and coupons; update customers and subs. This page covers its hosted endpoint (https://foxyio.usefulapi.io/mcp).
Is the io.usefulapi/foxyio MCP server safe to use?
io.usefulapi/foxyio scores 79 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.usefulapi/foxyio MCP server expose?
io.usefulapi/foxyio exposes 14 tools: foxy_get_api_home, foxy_get_default_store, foxy_get_store, foxy_list_transactions, foxy_get_transaction, and 9 more. Their descriptions and schemas cost roughly 1,362 tokens of context every time the server is loaded.
Does the io.usefulapi/foxyio MCP server require authentication?
Yes. io.usefulapi/foxyio asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/foxyio MCP server still maintained?
io.usefulapi/foxyio is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.