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.

BoardroomList

REMOTE · BOARDROOMLIST.COM

Search open senior roles, Manager to CEO, at the 500 largest US companies.

+3 this week 76 Trust /100

Last scanned (4 hours ago)

Scores higher than 66% of remote servers

Reachable. Last reached 5 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 Security80
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 674 tokens (~134/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 86% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
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.

  • 4 Nov 26 +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.

  • 2 Nov 26 +1

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

  • 31 Oct 26 +1

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

  • 29 Oct 26 +1

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

  • 28 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 27 Oct 26 72

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

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=boardroomlist.com CN=YE2,O=Let's Encrypt,C=US 24 Sept 2026 23 Dec 2026 ECDSA 256 ECDSA-SHA384 5ffae32a3172cabb02841ddcd23a173f7e3
SANs: *.boardroomlist.com, boardroomlist.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of boardroomlist.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
boardroomlist.com. absent 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://boardroomlist.com/api/mcp Verified 200
http (plaintext) http://boardroomlist.com/api/mcp HTTPS enforced 301 https://boardroomlist.com/api/mcp
MCP tools · 5 exposed · ~561 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
fetch ~32

Connector-style fetch of one role by the id from search. Same fields as get_role.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_role ~105

One role by id (the number at the end of its URL): title, level, function, location, work mode, posted pay, date, industry, a short redacted summary and scope, plus four similar open roles. Use it after search_roles when the user wants more on one result. Limitation: the company, full description and apply link are for members and are on the linked page.

NameTypeReqDescription
idstringyesRole id from search_roles or the role URL.

No output schema declared.

No examples provided.

list_filters ~61

The job functions, seniority bands, industries, top cities and work modes you can filter search_roles by, each with its count of open roles. Use it to resolve a function name or to answer "how many open VP roles are there". Returns no roles.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search ~35

Connector-style search over open senior roles. Returns ids for fetch. Prefer search_roles when you can filter.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

search_roles ~328

Search open senior roles (Manager to C-suite) at the 500 largest US companies by words, seniority band, function, work mode, region, city or state, minimum salary and recency. Returns up to 25 roles a page with title, level, location, posted pay range, date and a link. Use it for "VP finance roles in Texas", "remote director of engineering jobs", "what CFO roles are open". Limitation: no company names; the role page shows them to members.

NameTypeReqDescription
bandarray–Seniority: csuite, svp, vp, director, manager.
functionarray–Job functions, e.g. Finance, Technology. Call list_filters for the full list.
locationstring–A city or a US state, by name or code, e.g. Chicago, Texas, TX.
min_compinteger–Minimum posted salary in USD.
modearray–Work mode.
pageinteger–Page number, 25 roles a page.
posted_within_daysinteger–Only roles first seen in the last N days.
qstring–Words to search titles, e.g. "CFO" or "VP supply chain".
regionstring–us = United States only, intl = outside the US.
sortstring–senior (default), newest, or comp (highest pay first).
statusstring–open (default), new (7 days), today (24 hours), filled (last 30 days).

No output schema declared.

No examples provided.

Install

How do I install the BoardroomList MCP server?

BoardroomList is a hosted endpoint at https://boardroomlist.com/api/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 · boardroomlist.com

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

What is the BoardroomList MCP server?

BoardroomList is an MCP server listed in the public MCP registry as com.boardroomlist/mcp. Search open senior roles, Manager to CEO, at the 500 largest US companies. This page covers its hosted endpoint (https://boardroomlist.com/api/mcp).

Is the BoardroomList MCP server safe to use?

BoardroomList scores 76 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 BoardroomList MCP server expose?

BoardroomList exposes 5 tools: search_roles, get_role, list_filters, search, fetch. Their descriptions and schemas cost roughly 561 tokens of context every time the server is loaded.

Does the BoardroomList MCP server require authentication?

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

Is the BoardroomList MCP server still maintained?

BoardroomList 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.