ProfitCollector
REMOTE · MCP.BAKHOUR.CA
22 pay-per-call developer, security, network and data utilities using x402 on Base.
Available components
Last scanned (7 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1754 tokens (~56/item across 31 items; 31 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 48% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 31 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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 in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Oct 26 71
- Stability: fail → pass ▲ security
- 29 Sept 26 0
- Stability: pass → fail ▼ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 0
- Tool “post_x402_service_trust_report” rewrote its description, which is the text the model reads security
- 2 Sept 26 0
- Tool “post_media_video_generate_long” was removed ▼ security
- Tool “post_media_video_generate_medium” was removed ▼ security
- Tool “post_media_video_generate_short” was removed ▼ security
- Tool “get_dns_lookup” rewrote its description, which is the text the model reads security
- Tool “get_domain_intelligence” rewrote its description, which is the text the model reads security
- Tool “get_security_headers” rewrote its description, which is the text the model reads security
- Tool “get_security_posture” rewrote its description, which is the text the model reads security
- Tool “get_ssl_check” rewrote its description, which is the text the model reads security
- Tool “get_web_audit” rewrote its description, which is the text the model reads security
- Tool “post_domain_due_diligence” rewrote its description, which is the text the model reads security
- Schema quality: 47 → 56 ▼ functional
- Tool coverage: 40% → 48% ▲ functional
- 1 Sept 26 0
- Schema quality: 38 → 47 ▼ functional
- Tool coverage: 21% → 40% ▲ functional
- New tool “post_freshdep_scan” functional
- New tool “post_quebec_invoice_compliance_check” functional
- New tool “post_quebec_invoice_generate” functional
- 31 Aug 26 0
- Tool “post_media_video_generate” was removed ▼ security
- Tool “post_media_image_convert” rewrote its description, which is the text the model reads security
- Schema quality: 26 → 38 ▼ functional
- Tool coverage: 4% → 21% ▲ functional
- New tool “post_media_video_generate_long” functional
- New tool “post_media_video_generate_medium” functional
- New tool “post_media_video_generate_short” functional
- New tool “post_security_repo_risk_report_deep” functional
- New tool “post_security_repo_risk_report_due_diligence” functional
- New tool “post_security_repo_risk_report_standard” functional
- New tool “post_x402_service_trust_report” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.bakhour.ca/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bakhour.ca | CN=WE1,O=Google Trust Services,C=US | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | e7935630a69905f81364d41c9c9eab2f |
| SANs: bakhour.ca, *.bakhour.ca | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.bakhour.ca. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ca. | DS published | 26384 | 13 | Verified |
| bakhour.ca. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.bakhour.ca/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.bakhour.ca/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_dns_lookup ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| record_type | string | – | – |
No output schema declared.
No examples provided.
get_domain_intelligence ~54
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
get_jwt_decode ~25
Decode a JWT payload without signature verification.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | – |
No output schema declared.
No examples provided.
get_security_headers ~50
Inspect HTTP security headers for ONE URL only. For headers combined with TLS and DNS, use /web/audit (raw) or /security/posture (scored).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
get_security_posture ~55
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
get_ssl_check ~51
Inspect the TLS certificate for ONE hostname only. For TLS combined with HTTP headers and DNS, use /web/audit (raw) or /security/posture (scored).
| Name | Type | Req | Description |
|---|---|---|---|
| hostname | string | yes | – |
No output schema declared.
No examples provided.
get_subnet_calculate ~27
Calculate subnet information from CIDR notation.
| Name | Type | Req | Description |
|---|---|---|---|
| cidr | string | yes | – |
No output schema declared.
No examples provided.
get_timestamp_convert ~27
Convert a Unix timestamp to UTC ISO-8601.
| Name | Type | Req | Description |
|---|---|---|---|
| timestamp | number | yes | – |
No output schema declared.
No examples provided.
get_url_parse ~23
Parse a URL into structured components.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
get_uuid_generate ~24
Generate a random UUID version 4.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
No output schema declared.
No examples provided.
get_web_audit ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
post_base64_decode ~26
Decode Base64 to UTF-8 text.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
post_base64_encode ~26
Encode UTF-8 text using Base64.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
post_data_transform ~31
Normalize and transform common structured text automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| operation | string | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
post_domain_due_diligence ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Public domain name to assess |
No output schema declared.
No examples provided.
post_freshdep_scan ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | – | Optional branch/tag to check out instead of the default branch. |
| repo_url | string | yes | 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. |
No output schema declared.
No examples provided.
post_hash_sha256 ~25
Generate SHA-256 digest from text.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
post_hash_sha512 ~25
Generate SHA-512 digest from text.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
post_json_minify ~23
Minify valid JSON text.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
post_json_pretty ~23
Pretty-print valid JSON text.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
post_json_repair ~24
Repair common malformed JSON formatting issues.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
post_json_validate ~24
Validate JSON text and return parsing details.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
post_media_image_convert ~34
Convert an image between common formats (e.g. PNG/JPEG/WebP) from a URL or base64 payload.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
post_quebec_invoice_compliance_check ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | GST amount as shown on the invoice. |
| qst_amount | number | yes | QST amount as shown on the invoice. |
| subtotal | number | yes | Pre-tax subtotal in CAD. |
No output schema declared.
No examples provided.
post_quebec_invoice_generate ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_number | string | yes | Your own invoice number/reference. |
| line_items | array | yes | 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 | yes | Seller/business name to display. |
| seller_qst_number | string | – | QST registration number, optional. |
No output schema declared.
No examples provided.
post_security_repo_risk_report_deep ~79
Everything in the standard report, plus a repo-wide secret/credential exposure scan (matched values are never returned).
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | – | Optional branch/tag to analyze. Defaults to the repository's default branch. |
| repo_url | string | yes | Public https://github.com/... or https://gitlab.com/... repository URL. |
No output schema declared.
No examples provided.
post_security_repo_risk_report_due_diligence ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | – | Optional branch/tag to analyze. Defaults to the repository's default branch. |
| repo_url | string | yes | Public https://github.com/... or https://gitlab.com/... repository URL. |
No output schema declared.
No examples provided.
post_security_repo_risk_report_standard ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | – | Optional branch/tag to analyze. Defaults to the repository's default branch. |
| repo_url | string | yes | Public https://github.com/... or https://gitlab.com/... repository URL. |
No output schema declared.
No examples provided.
post_text_dedupe_lines ~27
Remove duplicate lines while preserving original order.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
post_text_stats ~26
Calculate character, word, line and byte statistics.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
post_x402_service_trust_report ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The full https:// URL of the x402-protected endpoint to evaluate. |
No output schema declared.
No examples provided.
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.
remote · mcp.bakhour.ca
claude mcp add --transport http ca-bakhour-profitcollector 'https://mcp.bakhour.ca/mcp'
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 71 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the ProfitCollector MCP server?
VerifyMCP ran 11 checks on ProfitCollector, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about ProfitCollector: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.