MCP servers observed by Lowdown
io.github.SeoScoreAPI/seoscoreapi-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; tool definitions last changed on 2026-11-17 after 6 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:io.github.SeoScoreAPI/seoscoreapi-mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.SeoScoreAPI/seoscoreapi-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?
Tool definitions changed on 1 of 2 compared days.
- 2026-11-17: input or output schemas changed, server version changed
What tools does it list?
45 tools on 2026-11-17:
accessibility_auditadd_geo_monitoradd_monitorai_readabilityauditbacklinksbatch_auditcitation_auto_reloadcitation_checkcitation_starter_promptscitation_suggest_promptscitation_topup_checkoutcitation_topupscitation_tracker_historycomparecompetitive_auditconversioncrawl_sitecreate_citation_trackerdeep_auditdeep_audit_usagedelete_citation_trackergeo_auditgeo_brand_probegeo_monitor_historyget_citation_runget_citation_trackerget_crawlget_deep_audithistoryhistory_domainslist_citation_trackerslist_geo_monitorslist_monitorsllms_txtquick_winsremove_geo_monitorremove_monitorreport_urlrun_citation_trackerstart_crawlstart_deep_audittrackersupdate_citation_trackerusage
MCP Registry declaration
- Registry name:
io.github.SeoScoreAPI/seoscoreapi-mcp - Declared version: 1.5.1
- Status: active
- Declared hosts:
seoscoreapi.com
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:io.github.SeoScoreAPI/seoscoreapi-mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.SeoScoreAPI/seoscoreapi-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:io.github.SeoScoreAPI/seoscoreapi-mcp -- npx -y seoscoreapi-mcp
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).