MCP servers observed by Lowdown
pro.particle/particle-pro MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 44 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; tool definitions last changed on 2026-11-18 after 9 days without change; 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:pro.particle/particle-pro
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:pro.particle/particle-pro?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 3 compared days.
- 2026-11-18: input or output schemas changed, descriptions changed, tool names changed; tool count 39 → 44
What tools does it list?
44 tools on 2026-11-18:
particle_alert_createparticle_alert_deleteparticle_alert_getparticle_alert_listparticle_alert_list_matchesparticle_alert_previewparticle_alert_updateparticle_callparticle_catalogparticle_company_getparticle_company_get_statement_characteristicsparticle_company_list_peopleparticle_company_resolveparticle_entity_getparticle_entity_resolveparticle_expertise_getparticle_expertise_resolveparticle_person_getparticle_person_get_statement_characteristicsparticle_person_resolveparticle_podcast_compare_share_of_voiceparticle_podcast_find_mentionsparticle_podcast_get_entity_chartparticle_podcast_get_episodeparticle_podcast_get_episode_timeseriesparticle_podcast_get_guestparticle_podcast_get_mention_trendsparticle_podcast_get_rankingsparticle_podcast_get_share_of_voiceparticle_podcast_get_transcription_requestparticle_podcast_list_clipsparticle_podcast_list_episodesparticle_podcast_list_guestsparticle_podcast_list_relatedparticle_podcast_list_related_episodesparticle_podcast_request_transcriptionparticle_podcast_resolveparticle_podcast_search_transcriptsparticle_report_createparticle_report_deleteparticle_report_getparticle_report_listparticle_report_updateparticle_topic_browse
MCP Registry declaration
- Registry name:
pro.particle/particle-pro - Declared version: 1.0.0
- Status: active
- Declared hosts:
mcp.particle.pro
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:pro.particle/particle-pro", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:pro.particle/particle-pro?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).