MCP servers observed by Lowdown
net.vibesprings/x402-tools MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 25 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; no tool definition change in 2 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:net.vibesprings/x402-tools
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:net.vibesprings/x402-tools?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 2 compared days.
What tools does it list?
25 tools on 2026-11-17:
audit_agent_visibilitycheck_listing_healthcheck_watchcheck_watches_batchconvert_currencyget_bazaar_category_trendsget_bazaar_competitorsget_crypto_newsget_crypto_pricesget_defi_yieldsget_delay_riskget_delay_risk_demoget_exchange_ratesget_forecastget_gas_pricesget_listing_intelget_market_historyget_market_pulseget_risk_reportget_travel_briefget_wallet_intelget_weather_historyhealthregister_watchsearch_services
MCP Registry declaration
- Registry name:
net.vibesprings/x402-tools - Declared version: 1.0.0
- Status: active
- Declared hosts:
vibesprings.net
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:net.vibesprings/x402-tools", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:net.vibesprings/x402-tools?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).