FOXIFY Agent Commerce
REMOTE · FOXIFY.PRO
Hosted x402 preflight for action authority, payment mandate, destination, expiry and replay.
Available components
Last scanned (23 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Security
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 Security66
- 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 3 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 319 tokens (~106/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 40% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 37. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 20 to 30. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 20. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 6 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 23 Oct 2026 · Probed https://foxify.pro/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=foxify.pro | CN=WE1,O=Google Trust Services,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f22c4d704376faf30e6b489126824607 |
| SANs: foxify.pro, x402.foxify.pro, *.x402.foxify.pro | ||||||
| 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 secure
Validation of foxify.pro. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| pro. | present | 33289, 42154 | 8, 8 | Verified |
| foxify.pro. | present | 2371 | 13 | Verified |
| foxify.pro. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://foxify.pro/mcp | Verified | 200 | |
| http (plaintext) | http://foxify.pro/mcp | HTTPS enforced | 301 | https://foxify.pro/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 →
foxify_preflight_info FOXIFY Preflight Info ~24
Free metadata for FOXIFY machine-payable authority preflight tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_agent_action_intent Verify Agent Action Intent ~132
Paid exact-action authority preflight for consequential agent tool calls. Binds subject, tool, operation, target, canonical parameters, authority lifetime, retries and postcondition requirements. Costs $0.25 USDC on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| action | object | yes | – |
| action_id | string | yes | Unique action-intent identifier |
| authority | object | yes | – |
| execution | object | – | – |
| expires_at | string | yes | ISO-8601 action-intent expiry |
| nonce | string | yes | Unique anti-replay nonce |
| postcondition | object | – | – |
| subject | object | yes | – |
No output schema declared.
No examples provided.
verify_agent_payment_intent Verify Agent Payment Intent ~112
Paid transaction preflight. Checks mandate, amount, destination, merchant, expiry and replay risk before an autonomous payment executes. Costs $0.05 USDC on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | object | – | – |
| authorization | object | yes | – |
| expires_at | string | yes | ISO-8601 intent expiry |
| intent_id | string | yes | Unique payment-intent identifier |
| merchant | object | yes | – |
| nonce | string | yes | Unique anti-replay nonce |
| payment | object | yes | – |
No output schema declared.
No examples provided.
How do I install the FOXIFY Agent Commerce MCP server?
FOXIFY Agent Commerce is a hosted endpoint at https://foxify.pro/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 · foxify.pro
claude mcp add --transport http pro-foxify-agent-commerce 'https://foxify.pro/mcp'
What is the FOXIFY Agent Commerce MCP server?
FOXIFY Agent Commerce is an MCP server listed in the public MCP registry as pro.foxify/agent-commerce. Hosted x402 preflight for action authority, payment mandate, destination, expiry and replay. This page covers its hosted endpoint (https://foxify.pro/mcp).
Is the FOXIFY Agent Commerce MCP server safe to use?
FOXIFY Agent Commerce scores 74 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 FOXIFY Agent Commerce MCP server expose?
FOXIFY Agent Commerce exposes 3 tools: foxify_preflight_info, verify_agent_payment_intent, verify_agent_action_intent. Their descriptions and schemas cost roughly 268 tokens of context every time the server is loaded.
Does the FOXIFY Agent Commerce MCP server require authentication?
No. We connected to FOXIFY Agent Commerce without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FOXIFY Agent Commerce MCP server still maintained?
FOXIFY Agent Commerce is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.