Add Vongstaad MCP

[VGSTAAD]

Quant signal infrastructure. Discovery: vongstaad.com/.well-known/x402.json

[TateLyman]

Quick public no-payment check on the listed discovery URL.

Current result: https://vongstaad.com/.well-known/x402.json returns HTTP 200, but the response is text/html and appears to be the main Von Gstaad homepage, not JSON discovery metadata. /.well-known/x402 and /.well-known/agent-card.json showed the same homepage-style HTML response in my sample.

Positive signal: https://vongstaad.com/llms.txt is live and clearly describes the FX market-structure service for machine readers.

Suggested fix before merge: publish real JSON at the discovery URL named in the PR, or update the listing to point to the actual live x402/MCP discovery surface if it lives elsewhere. If these endpoints are intentionally not public yet, marking the PR as pending launch would avoid agent crawlers treating the homepage HTML as an x402 manifest.

No payment header, wallet signature, account, API key, or paid call used.

[VGSTAAD]

@TateLyman — Fixed.

https://vongstaad.com/.well-known/x402.json now returns application/json with proper x402 discovery metadata.

The Cloudflare Pages _headers configuration was updated to serve .well-known/* files with correct Content-Type.

Same for /.well-known/agent.json.

Thanks for catching this — please re-check when you have a moment.

[TateLyman]

Re-checked the patched public discovery paths, no payment headers/signatures used.

Repro:

curl -I https://vongstaad.com/.well-known/x402.json
curl -I https://vongstaad.com/.well-known/agent.json
npx --yes x402-surface-check@latest https://vongstaad.com/.well-known/x402.json --limit 8 --origin https://vongstaad.com

What improved:

• /.well-known/x402.json now returns 200 application/json with the listed endpoint catalog, Base mainnet USDC recipient, prices, and auth_type: x402.
• /.well-known/agent.json now returns 200 application/json instead of the previous homepage HTML fallback.
• llms.txt is also reachable and text-readable.

Remaining launch note before this is buyer-ready: the listed paid paths such as /v1/correlation, /v1/regime, and /v1/price still resolve to the homepage HTML with 200 text/html on a no-payment GET, rather than returning a structured 402 Payment Required challenge or a documented free/trial JSON response. The checker therefore sees all seven manifest routes as 200/no challenge.

So the discovery content-type issue is fixed; the next thing to wire is route handling/payment middleware for the manifest endpoints themselves, or explicitly mark them as docs/demo placeholders until the API host is live.

[VGSTAAD]

@TateLyman — All issues resolved.

https://vongstaad.com/.well-known/x402.json now returns application/json with full discovery metadata

https://vongstaad.com/.well-known/agent.json now returns application/json A2A Agent Card

All 7 manifest routes return HTTP 402 with payment instructions:

https://vongstaad-data.vongstaad.com/v1/correlation → HTTP 402

https://vongstaad-data.vongstaad.com/v1/regime → HTTP 402

https://vongstaad-data.vongstaad.com/v1/momentum → HTTP 402

https://vongstaad-data.vongstaad.com/v1/volatility → HTTP 402

https://vongstaad-data.vongstaad.com/v1/mean-reversion → HTTP 402

https://vongstaad-data.vongstaad.com/v1/price → HTTP 402

https://vongstaad-data.vongstaad.com/v1/sma → HTTP 402

Thanks for the review.