Skip to content

Foxy.io MCP by usefulapi

io.usefulapi/foxyiousefulapi.iostreamable-httpv1.40.4Scanned

Read Foxy transactions, subscriptions, customers, carts and coupons; update customers and subs.

14 tools: 2 can delete or cancel things and 12 only read.

Tools: 2 delete, 0 irreversible, 0 write, 12 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Foxy.io MCP by usefulapi can do

The Foxy.io MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (2 tools: foxy_update_customer and foxy_update_subscription). 12 tools only read.

1 tool reads private data (foxy_get_api_home).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

14 tools

Deletes or cancels 2Claude Code: deny
  • foxy_update_customerUPDATES a customer's profile fields (first_name, last_name, email).No findings

    Why it is in this group

    • The name "foxy_update_customer" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Update customer
    • destructiveHint: true
  • foxy_update_subscriptionUPDATES a subscription — reschedule its next run (next_transaction_date), change its frequency, or activate/pause it (is_active).No findings

    Why it is in this group

    • The name "foxy_update_subscription" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Update subscription
    • destructiveHint: true
Only reads 12Show 12 read-only tools
  • foxy_get_api_homeGet the Foxy hAPI home document — its _links / rels (including fx:store for the authenticated default store).Reads private dataNo findings

    Why it is in this group

    • The name "foxy_get_api_home" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "document": it reads documents.
    Description, as the server wrote it
    Get the Foxy hAPI home document — its _links / rels (including fx:store for the authenticated default store). Useful for HAL discovery. Foxy hAPI: GET /.

    Annotations the server declares

    • title: Get API home
    • readOnlyHint: true
  • foxy_get_customerGet a single customer by id, optionally zooming related resources (default_billing_address, subscriptions…).No findings

    Why it is in this group

    • The name "foxy_get_customer" says "get": a word for reading.
    Description, as the server wrote it
    Get a single customer by id, optionally zooming related resources (default_billing_address, subscriptions…). Foxy hAPI: GET /customers/{id}.

    Annotations the server declares

    • title: Get customer
    • readOnlyHint: true
  • 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.No findings

    Why it is in this group

    • The name "foxy_get_default_store" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get default store
    • readOnlyHint: true
  • foxy_get_storeGet a single store resource by id, including its settings and _links to sub-collections.No findings

    Why it is in this group

    • The name "foxy_get_store" says "get": a word for reading.
    Description, as the server wrote it
    Get a single store resource by id, including its settings and _links to sub-collections. Foxy hAPI: GET /stores/{store_id}.

    Annotations the server declares

    • title: Get store
    • readOnlyHint: true
  • foxy_get_subscriptionGet a single subscription by id, optionally zooming related resources.No findings

    Why it is in this group

    • The name "foxy_get_subscription" says "get": a word for reading.
    Description, as the server wrote it
    Get a single subscription by id, optionally zooming related resources. Foxy hAPI: GET /subscriptions/{id}.

    Annotations the server declares

    • title: Get subscription
    • readOnlyHint: true
  • foxy_get_transactionGet a single transaction by id, optionally zooming related resources (items, customer, payments, applied_taxes…).No findings

    Why it is in this group

    • The name "foxy_get_transaction" says "get": a word for reading.
    Description, as the server wrote it
    Get a single transaction by id, optionally zooming related resources (items, customer, payments, applied_taxes…). Foxy hAPI: GET /transactions/{id}.

    Annotations the server declares

    • title: Get transaction
    • readOnlyHint: true
  • foxy_list_cartsList a store's carts (in-progress / abandoned checkouts).No findings

    Why it is in this group

    • The name "foxy_list_carts" says "list": a word for reading.
    Description, as the server wrote it
    List a store's carts (in-progress / abandoned checkouts). Returns a HAL collection embedding fx:carts. Foxy hAPI: GET /stores/{store_id}/carts.

    Annotations the server declares

    • title: List carts
    • readOnlyHint: true
  • foxy_list_couponsList a store's coupons (discount codes and their rules).No findings

    Why it is in this group

    • The name "foxy_list_coupons" says "list": a word for reading.
    Description, as the server wrote it
    List a store's coupons (discount codes and their rules). Returns a HAL collection embedding fx:coupons. Foxy hAPI: GET /stores/{store_id}/coupons.

    Annotations the server declares

    • title: List coupons
    • readOnlyHint: true
  • foxy_list_customersList a store's customers.No findings

    Why it is in this group

    • The name "foxy_list_customers" says "list": a word for reading.
    Description, as the server wrote it
    List a store's customers. Returns a HAL collection embedding fx:customers. Foxy hAPI: GET /stores/{store_id}/customers.

    Annotations the server declares

    • title: List customers
    • readOnlyHint: true
  • foxy_list_itemsList the line items of a transaction (the products purchased).No findings

    Why it is in this group

    • The name "foxy_list_items" says "list": a word for reading.
    Description, as the server wrote it
    List the line items of a transaction (the products purchased). Returns a HAL collection embedding fx:items. Foxy hAPI: GET /transactions/{transaction_id}/items.

    Annotations the server declares

    • title: List transaction items
    • readOnlyHint: true
  • foxy_list_subscriptionsList a store's subscriptions (recurring orders).No findings

    Why it is in this group

    • The name "foxy_list_subscriptions" says "list": a word for reading.
    Description, as the server wrote it
    List a store's subscriptions (recurring orders). Returns a HAL collection embedding fx:subscriptions. Foxy hAPI: GET /stores/{store_id}/subscriptions.

    Annotations the server declares

    • title: List subscriptions
    • readOnlyHint: true
  • foxy_list_transactionsList a store's transactions (orders), newest first.No findings

    Why it is in this group

    • The name "foxy_list_transactions" says "list": a word for reading.
    Description, as the server wrote it
    List a store's transactions (orders), newest first. Returns a HAL collection embedding fx:transactions. Foxy hAPI: GET /stores/{store_id}/transactions.

    Annotations the server declares

    • title: List transactions
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:35 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://foxyio.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://foxyio.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://foxyio.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://foxyio.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http foxyio https://foxyio.usefulapi.io/mcp
claude mcp add --transport http foxyio https://foxyio.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__foxyio__foxy_get_api_home",
      "mcp__foxyio__foxy_get_default_store",
      "mcp__foxyio__foxy_get_store",
      "mcp__foxyio__foxy_list_transactions",
      "mcp__foxyio__foxy_get_transaction",
      "mcp__foxyio__foxy_list_subscriptions",
      "mcp__foxyio__foxy_get_subscription",
      "mcp__foxyio__foxy_list_customers",
      "mcp__foxyio__foxy_get_customer",
      "mcp__foxyio__foxy_list_carts",
      "mcp__foxyio__foxy_list_coupons",
      "mcp__foxyio__foxy_list_items"
    ],
    "ask": [],
    "deny": [
      "mcp__foxyio__foxy_update_customer",
      "mcp__foxyio__foxy_update_subscription"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as foxyio. Review it before you use it.

Capability tags behind 1 rule
  • mcp__foxyio__foxy_get_api_home private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/foxyio/verify?hash=d33c23f86fc922634a125ba2b686a7b93f83e478c74597ffe7853c0dd6d31a77" | jq -e '.changed == false'

Pinned hash d33c23f86fc9, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/foxyio/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/foxyio
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/foxyio.svg)](https://radar.anlyon.com/servers/io.usefulapi/foxyio)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Foxy.io MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Foxy.io MCP by usefulapi safe?

No scan can promise that. What its definitions show: 14 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Foxy.io MCP by usefulapi delete data?

Yes. 2 tools can delete, cancel or revoke something: foxy_update_customer and foxy_update_subscription.

Can the Foxy.io MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Foxy.io MCP by usefulapi have?

14 tools: 2 destructive, 12 read. foxy_update_customer, foxy_update_subscription, foxy_get_api_home, foxy_get_default_store, foxy_get_store, foxy_list_transactions, foxy_get_transaction, foxy_list_subscriptions and 6 more.

Does the Foxy.io MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Foxy.io MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Foxy.io MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.