Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Brahim Bousnguar — portfolio

REMOTE · API.HEYBRAHIM.COM

Brahim Bousnguar's portfolio: profile, availability, case studies, notes, CV requests.

0 this week 79 Trust /100

Last scanned (22 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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 Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, 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
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 538 tokens (~89/item across 6 items; 6 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 Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 42% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

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.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, 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 →

Changelog

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.

  • 19 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “list_items” rewrote its description, which is the text the model reads security
    • Tool “request_cv” rewrote its description, which is the text the model reads security
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 27 Oct 26 0
    • Stability: 0.97 → pass security
  • 26 Oct 26 +1

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

  • 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
  • 27 Sept 26 0

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://api.heybrahim.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=heybrahim.com CN=WE1,O=Google Trust Services,C=US 23 Sept 2026 22 Dec 2026 ECDSA 256 ECDSA-SHA256 bf68c9737fe69f30e7c4409bffb8f05
SANs: heybrahim.com, api.heybrahim.com, *.api.heybrahim.com
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 api.heybrahim.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
heybrahim.com. 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://api.heybrahim.com/mcp Verified 200
http (plaintext) http://api.heybrahim.com/mcp Inconclusive 405
MCP tools · 6 exposed · ~447 tokens

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 →

Tool Tokens
get_availability ~31

Whether Brahim is open to new roles right now, what kind, from when, and where (dated).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_item ~74

Full text (Markdown) of one case study, project or note by its slug, as listed by list_items. Case studies and projects also exist in French.

NameTypeReqDescription
kindstringyes–
langstring––
slugstringyese.g. api-led-luxury-retail, mulewatch

No output schema declared.

No examples provided.

get_profile ~32

Brahim's headline, summary, location, languages, certifications (with verification links), skills and links. Start here.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_items ~50

List the client case studies (work), side projects (projects) or technical notes (notes), newest first, with a one-line summary and URL.

NameTypeReqDescription
kindstringyeswork, projects or notes

No output schema declared.

No examples provided.

request_cv ~194

File a request for Brahim's full CV, exactly like the form on heybrahim.com/cv.html. Brahim reads every request and sends the CV himself by email, usually the same day; nothing is sent automatically. Only call this when the user explicitly asked for the CV and gave their own name and email. Limited to a few requests per day. Tell your user before sending: their name and email go to Brahim Bousnguar (Nantes, France), are used only to send the CV and reply, and are kept 12 months; privacy and rights: https://heybrahim.com/privacy.html

NameTypeReqDescription
companystring––
emailstringyesWhere Brahim should send the CV
langstring––
messagestring––
namestringyesThe requester's own name
rolestring–The role or mission, if any

No output schema declared.

No examples provided.

search ~66

Keyword search across every case study, project and note (e.g. "DataWeave", "CCv2 migration", "MCP"). Returns titles, URLs and a snippet; use get_item for the full text.

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

Install

How do I install the Brahim Bousnguar — portfolio MCP server?

Brahim Bousnguar — portfolio is a hosted endpoint at https://api.heybrahim.com/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 · api.heybrahim.com

# add to Claude Code
claude mcp add --transport http com-heybrahim-portfolio 'https://api.heybrahim.com/mcp'
Common questions

What is the Brahim Bousnguar — portfolio MCP server?

Brahim Bousnguar — portfolio is an MCP server listed in the public MCP registry as com.heybrahim/portfolio. Brahim Bousnguar's portfolio: profile, availability, case studies, notes, CV requests. This page covers its hosted endpoint (https://api.heybrahim.com/mcp).

Is the Brahim Bousnguar — portfolio MCP server safe to use?

Brahim Bousnguar — portfolio scores 79 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 Brahim Bousnguar — portfolio MCP server expose?

Brahim Bousnguar — portfolio exposes 6 tools: get_profile, get_availability, list_items, get_item, search, request_cv. Their descriptions and schemas cost roughly 447 tokens of context every time the server is loaded.

Does the Brahim Bousnguar — portfolio MCP server require authentication?

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

Is the Brahim Bousnguar — portfolio MCP server still maintained?

Brahim Bousnguar — portfolio is still listed as active in the MCP registry. We last reached this channel on 21 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 Brahim Bousnguar — portfolio MCP server?

VerifyMCP ran 12 checks on Brahim Bousnguar — portfolio, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Brahim Bousnguar — portfolio: 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.