# ProfitCollector (remote · mcp.bakhour.ca)

22 pay-per-call developer, security, network and data utilities using x402 on Base.

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.bakhour.ca`: 65/100 (this document), [markdown](https://verifymcp.io/servers/ca-bakhour-profitcollector/mcp.md), [page](https://verifymcp.io/servers/ca-bakhour-profitcollector/mcp)

## Channel facts

- Endpoint: `https://mcp.bakhour.ca/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 31 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1754 tokens (~56/item across 31 items; 31 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 48% of tool parameters carry a description.
- **Tool Safety**: 50/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "post_text_dedupe_lines" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - Manipulation not yet verified: only 30 of 31 captured unit(s) of tool text has been judged so far, so we will not certify text no model has read as clean.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the ProfitCollector MCP server?

ProfitCollector is a hosted endpoint at https://mcp.bakhour.ca/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ca-bakhour-profitcollector 'https://mcp.bakhour.ca/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ca-bakhour-profitcollector": {
      "url": "https://mcp.bakhour.ca/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ca-bakhour-profitcollector": {
      "type": "http",
      "url": "https://mcp.bakhour.ca/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ca-bakhour-profitcollector]
url = "https://mcp.bakhour.ca/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ca-bakhour-profitcollector": {
      "type": "remote",
      "url": "https://mcp.bakhour.ca/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ca-bakhour-profitcollector --url 'https://mcp.bakhour.ca/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ca-bakhour-profitcollector:
    url: "https://mcp.bakhour.ca/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ca-bakhour-profitcollector": {
      "Transport": "http",
      "Url": "https://mcp.bakhour.ca/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ca-bakhour-profitcollector -t streamable-http -u 'https://mcp.bakhour.ca/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ca-bakhour-profitcollector": {
      "type": "http",
      "url": "https://mcp.bakhour.ca/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-18 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 61, 0)

- [security] Tool “post_x402_service_trust_report” rewrote its description, which is the text the model reads

### 2026-09-10 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (31)

### `get_dns_lookup` (~81 tokens)

Resolve ONE DNS record type for a domain. For all record types at once use /domain/intelligence; for a bundled DNS+TLS+headers audit use /web/audit or /security/posture; for mail-security plus a scored verdict use /domain/due-diligence.

Input parameters:

- `domain` (string, required)
- `record_type` (string)

### `get_jwt_decode` (~25 tokens)

Decode a JWT payload without signature verification.

Input parameters:

- `token` (string, required)

### `get_subnet_calculate` (~27 tokens)

Calculate subnet information from CIDR notation.

Input parameters:

- `cidr` (string, required)

### `post_json_repair` (~24 tokens)

Repair common malformed JSON formatting issues.

Input parameters:

- `text` (string, required)

### `post_media_image_convert` (~34 tokens)

Convert an image between common formats (e.g. PNG/JPEG/WebP) from a URL or base64 payload.

### `post_security_repo_risk_report_standard` (~92 tokens)

SBOM inventory plus real OSV.dev dependency-vulnerability matches and dependency-freshness signals for a public Git repository. One-shot alternative to a per-seat secret-scanning subscription.

Input parameters:

- `ref` (string): Optional branch/tag to analyze. Defaults to the repository's default branch.
- `repo_url` (string, required): Public https://github.com/... or https://gitlab.com/... repository URL.

### `post_security_repo_risk_report_deep` (~79 tokens)

Everything in the standard report, plus a repo-wide secret/credential exposure scan (matched values are never returned).

Input parameters:

- `ref` (string): Optional branch/tag to analyze. Defaults to the repository's default branch.
- `repo_url` (string, required): Public https://github.com/... or https://gitlab.com/... repository URL.

### `post_security_repo_risk_report_due_diligence` (~100 tokens)

Everything in the deep report, plus real OpenSSF Scorecard maintainer/governance signals and a prioritized recommendation. An automated baseline positioned against $5,000-$95,000 human technical due diligence.

Input parameters:

- `ref` (string): Optional branch/tag to analyze. Defaults to the repository's default branch.
- `repo_url` (string, required): Public https://github.com/... or https://gitlab.com/... repository URL.

### `post_x402_service_trust_report` (~125 tokens)

Live, on-demand check of ONE x402-protected endpoint before you pay it: payment-requirements structure, TLS certificate, payTo on-chain balance, known-asset recognition, resource/host consistency, and discovery-manifest cross-check -- not a cached aggregate reputation score.

Input parameters:

- `target_method` (string): HTTP method to request target_url with. Defaults to GET; use POST for action-style endpoints that only 402-challenge on POST.
- `target_url` (string, required): The full https:// URL of the x402-protected endpoint to evaluate.

### `post_freshdep_scan` (~132 tokens)

Flags pinned dependencies in a repository's requirements.txt, package-lock.json, or uv.lock published more recently than a freshness threshold -- a supply-chain-compromise tripwire. Free CLI (requirements.txt/package-lock.json only, uv.lock support pending there): github.com/sbakhour/freshdep.

Input parameters:

- `ref` (string): Optional branch/tag to check out instead of the default branch.
- `repo_url` (string, required): Full https://github.com/<owner>/<repo> URL to scan.
- `threshold_days` (number): Flag anything published more recently than this many days ago. Defaults to 7.

### `post_quebec_invoice_compliance_check` (~162 tokens)

Verifies GST/QST were calculated correctly per Revenu Quebec's current (non-compounded) formula, and flags whether a French invoice version is present per Charter of the French Language s.57/89/91. Pure arithmetic + text check; not legal or tax advice.

Input parameters:

- `english_text` (string): The invoice's primary/other-language text (optional but needed for the language check).
- `french_text` (string): The invoice's French text, if any (optional -- its absence is itself flagged).
- `gst_amount` (number, required): GST amount as shown on the invoice.
- `qst_amount` (number, required): QST amount as shown on the invoice.
- `subtotal` (number, required): Pre-tax subtotal in CAD.

### `post_quebec_invoice_generate` (~147 tokens)

Assembles a bilingual (French/English) Quebec invoice document with GST/QST computed exactly per Revenu Quebec's current formula -- you supply both languages' line-item text, this does not translate. Not legal or tax advice.

Input parameters:

- `invoice_number` (string, required): Your own invoice number/reference.
- `line_items` (array, required): Each item needs description_en, description_fr (both required -- this assembles, it does not translate), and amount.
- `seller_gst_number` (string): GST registration number, optional.
- `seller_name` (string, required): Seller/business name to display.
- `seller_qst_number` (string): QST registration number, optional.

### `post_json_validate` (~24 tokens)

Validate JSON text and return parsing details.

Input parameters:

- `text` (string, required)

### `post_json_pretty` (~23 tokens)

Pretty-print valid JSON text.

Input parameters:

- `text` (string, required)

### `post_json_minify` (~23 tokens)

Minify valid JSON text.

Input parameters:

- `text` (string, required)

### `post_base64_encode` (~26 tokens)

Encode UTF-8 text using Base64.

Input parameters:

- `text` (string, required)

### `post_base64_decode` (~26 tokens)

Decode Base64 to UTF-8 text.

Input parameters:

- `text` (string, required)

### `post_hash_sha256` (~25 tokens)

Generate SHA-256 digest from text.

Input parameters:

- `text` (string, required)

### `post_hash_sha512` (~25 tokens)

Generate SHA-512 digest from text.

Input parameters:

- `text` (string, required)

### `get_uuid_generate` (~24 tokens)

Generate a random UUID version 4.

Input parameters:

- `count` (integer)

### `get_url_parse` (~23 tokens)

Parse a URL into structured components.

Input parameters:

- `url` (string, required)

### `post_text_stats` (~26 tokens)

Calculate character, word, line and byte statistics.

Input parameters:

- `text` (string, required)

### `post_text_dedupe_lines` (~27 tokens)

Remove duplicate lines while preserving original order.

Input parameters:

- `text` (string, required)

### `get_timestamp_convert` (~27 tokens)

Convert a Unix timestamp to UTC ISO-8601.

Input parameters:

- `timestamp` (number, required)

### `post_domain_due_diligence` (~111 tokens)

The most comprehensive domain assessment: DNS + mail security (SPF/DKIM/DMARC) + TLS + HTTP headers, scored. The only endpoint in this group that adds mail-security analysis. Use for a one-shot decision-grade verdict on an unfamiliar domain; use /dns/lookup, /ssl/check, /security/headers, /web/audit or /security/posture instead for a single fact or a cheaper signal.

Input parameters:

- `domain` (string, required): Public domain name to assess

### `get_domain_intelligence` (~54 tokens)

Collect ALL common DNS record types (A/AAAA/MX/NS/TXT/CAA) for a domain in one call -- the multi-record bundle version of /dns/lookup.

Input parameters:

- `domain` (string, required)

### `get_web_audit` (~75 tokens)

Consolidated DNS, TLS and HTTP security audit for a public HTTPS website, returned as RAW findings (no score) -- the bundled version of /dns/lookup + /ssl/check + /security/headers. Use /security/posture instead for a 0-100 score/grade.

Input parameters:

- `url` (string, required)

### `get_security_posture` (~55 tokens)

Assess TLS and HTTP security posture for a public HTTPS website -- the SAME inspection as /web/audit, but returns a 0-100 score/grade and findings instead of raw fields.

Input parameters:

- `url` (string, required)

### `post_data_transform` (~31 tokens)

Normalize and transform common structured text automatically.

Input parameters:

- `operation` (string)
- `text` (string, required)

### `get_security_headers` (~50 tokens)

Inspect HTTP security headers for ONE URL only. For headers combined with TLS and DNS, use /web/audit (raw) or /security/posture (scored).

Input parameters:

- `url` (string, required)

### `get_ssl_check` (~51 tokens)

Inspect the TLS certificate for ONE hostname only. For TLS combined with HTTP headers and DNS, use /web/audit (raw) or /security/posture (scored).

Input parameters:

- `hostname` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ca-bakhour-profitcollector/mcp#diagnostics

## Score history

- 2026-09-20: 65
- 2026-09-19: 65
- 2026-09-18: 65
- 2026-09-17: 64
- 2026-09-16: 64
- 2026-09-15: 63
- 2026-09-14: 63
- 2026-09-13: 62
- 2026-09-12: 62
- 2026-09-11: 61
- 2026-09-10: 61
- 2026-09-09: 60
- 2026-09-08: 60
- 2026-09-07: 59
- 2026-09-06: 59
- 2026-09-05: 58
- 2026-09-04: 58
- 2026-09-03: 58
- 2026-09-02: 57
- 2026-09-01: 56
- 2026-08-31: 55
- 2026-08-30: 53
- 2026-08-29: 53

## Common questions

### What is the ProfitCollector MCP server?

ProfitCollector is an MCP server listed in the public MCP registry as ca.bakhour/profitcollector. 22 pay-per-call developer, security, network and data utilities using x402 on Base. This page covers its hosted endpoint (https://mcp.bakhour.ca/mcp).

### Is the ProfitCollector MCP server safe to use?

ProfitCollector scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ProfitCollector MCP server expose?

ProfitCollector exposes 31 tools: get_dns_lookup, get_jwt_decode, get_subnet_calculate, post_json_repair, post_media_image_convert, and 26 more. Their descriptions and schemas cost roughly 1,754 tokens of context every time the server is loaded.

### Does the ProfitCollector MCP server require authentication?

No. We connected to ProfitCollector without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ProfitCollector MCP server still maintained?

ProfitCollector is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.bakhour.ca/mcp
- Website: https://mcp.bakhour.ca/
- Changelog RSS feed: https://verifymcp.io/servers/ca-bakhour-profitcollector/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ca-bakhour-profitcollector/mcp.json
- HTML version of this page: https://verifymcp.io/servers/ca-bakhour-profitcollector/mcp