MCP servers observed by Lowdown
dev.apifleet/apifleet 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); 67 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:dev.apifleet/apifleet
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.apifleet/apifleet?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?
67 tools on 2026-11-17:
apifleet_check_assistant_configapifleet_estimate_call_costapifleet_get_provider_matrixbind_numbercheck_entitlementscreate_api_keycreate_assistantcreate_browser_test_tokencreate_knowledge_documentcreate_outbound_callcreate_simulationcreate_simulation_personacreate_simulation_scenariocreate_toolcreate_webhookdelete_assistantdelete_knowledge_documentdelete_recordingdelete_simulationdelete_simulation_personadelete_simulation_rundelete_simulation_scenariodelete_tooldelete_webhookget_assistantget_assistant_voice_presetsget_billing_policyget_knowledge_documentget_metricsget_simulationget_simulation_personaget_simulation_runget_simulation_scenarioget_toolget_tts_settingsget_walletget_waveformlist_api_keyslist_assistantslist_balance_activitylist_callslist_knowledge_documentslist_numberslist_paymentslist_provider_credentialslist_simulation_personaslist_simulation_runslist_simulation_scenarioslist_simulationslist_toolslist_tts_rateslist_tts_voiceslist_voice_presetslist_webhooksrevoke_api_keyset_assistant_knowledgeset_assistant_toolsstart_simulation_batchstart_simulation_rununbind_numberupdate_assistantupdate_knowledge_documentupdate_simulationupdate_simulation_personaupdate_simulation_scenarioupdate_toolupdate_webhook
MCP Registry declaration
- Registry name:
dev.apifleet/apifleet - Declared version: 1.2.0
- Status: active
- Declared hosts:
apifleet.dev
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:dev.apifleet/apifleet", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.apifleet/apifleet?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).