MCP servers observed by Lowdown
dev.agentseo.www/agentseo-mcp 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); 45 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.agentseo.www/agentseo-mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.agentseo.www/agentseo-mcp?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?
45 tools on 2026-11-17:
agentseo_ai_overview_extractagentseo_ai_visibility_prompt_setagentseo_analyze_serpagentseo_backlinks_anchorsagentseo_backlinks_competitorsagentseo_backlinks_domain_pagesagentseo_backlinks_listagentseo_backlinks_new_lost_timeseriesagentseo_backlinks_opportunity_finderagentseo_backlinks_page_intersectionagentseo_backlinks_referring_domainsagentseo_backlinks_summaryagentseo_content_action_planagentseo_content_briefagentseo_content_cannibalizationagentseo_content_competitor_gap_matrixagentseo_content_draft_qaagentseo_content_gapagentseo_content_internal_linksagentseo_content_keyword_mapagentseo_content_programmatic_templateagentseo_content_refresh_briefagentseo_content_schema_planagentseo_content_serp_outlineagentseo_content_technical_qaagentseo_content_title_metaagentseo_domain_competitorsagentseo_domain_intersectionagentseo_domain_ranked_keywordsagentseo_domain_relevant_pagesagentseo_domain_traffic_estimateagentseo_extractagentseo_job_statusagentseo_keyword_ideas_suggestagentseo_keyword_metrics_overviewagentseo_local_auditagentseo_local_visibility_trackagentseo_opportunities_briefagentseo_opportunities_findagentseo_page_cro_qaagentseo_page_intersectionagentseo_rank_trackagentseo_searchagentseo_serp_volatilityagentseo_site_sitemap_audit
MCP Registry declaration
- Registry name:
dev.agentseo.www/agentseo-mcp - Declared version: 0.1.6
- Status: active
- Declared hosts:
www.agentseo.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.agentseo.www/agentseo-mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.agentseo.www/agentseo-mcp?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:dev.agentseo.www/agentseo-mcp -- npx -y @agentseo/mcp-server
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).