MCP servers observed by Lowdown
ca.bakhour/profitcollector MCP server: daily status and tool changes
Answered initialize and tools/list on all 21 daily checks recorded in the last 30 days (2026-10-29 to 2026-11-18); 31 tools listed. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-29; tool definitions last changed on 2026-11-15 after 1 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:ca.bakhour/profitcollector
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ca.bakhour/profitcollector?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: 21
- Answered initialize and tools/list: 21
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 21 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 4 of 20 compared days.
- 2026-11-15: input or output schemas changed, descriptions changed, tool names changed; tool count 25 → 31
- 2026-11-14: input or output schemas changed, descriptions changed, tool names changed; tool count 31 → 25
- 2026-11-12: input or output schemas changed, descriptions changed, tool names changed; tool count 25 → 31
- 2026-11-11: input or output schemas changed, descriptions changed, tool names changed; tool count 31 → 25
What tools does it list?
31 tools on 2026-11-18:
get_dns_lookupget_domain_intelligenceget_jwt_decodeget_security_headersget_security_postureget_ssl_checkget_subnet_calculateget_timestamp_convertget_url_parseget_uuid_generateget_web_auditpost_base64_decodepost_base64_encodepost_data_transformpost_domain_due_diligencepost_freshdep_scanpost_hash_sha256post_hash_sha512post_json_minifypost_json_prettypost_json_repairpost_json_validatepost_media_image_convertpost_quebec_invoice_compliance_checkpost_quebec_invoice_generatepost_security_repo_risk_report_deeppost_security_repo_risk_report_due_diligencepost_security_repo_risk_report_standardpost_text_dedupe_linespost_text_statspost_x402_service_trust_report
MCP Registry declaration
- Registry name:
ca.bakhour/profitcollector - Declared version: 1.0.0
- Status: active
- Declared hosts:
mcp.bakhour.ca
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:ca.bakhour/profitcollector", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ca.bakhour/profitcollector?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).