BeeDirectory
REMOTE · BEE-DIRECTORY.COM
Find newsletters to sponsor: verified audience, sponsorship prices and sources from BeeDirectory.
Available components
Last scanned (13 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Marketing and SEO
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
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 375 tokens (~125/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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 (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
- Tool “search_newsletters” rewrote its description, which is the text the model reads security
- 17 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.1.0 functional
- 16 Nov 26 72
First indexed and scored.
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://bee-directory.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=bee-directory.com | CN=YR1,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | RSA 2048 | SHA256-RSA | 675b5ab0204aec03608c04775f87aedc85d |
| SANs: bee-directory.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bee-directory.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| bee-directory.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bee-directory.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://bee-directory.com/api/mcp | HTTPS enforced | 308 | https://bee-directory.com/api/mcp |
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_newsletter Get a newsletter's sponsorship details ~86
Get one BeeDirectory listing by id or name: audience and open rate with their source, sponsorship price per send, rate card, price per 1,000 subscribers, sponsor page, frequency and how to contact the creator.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | – | BeeDirectory listing id (from search results) |
| name | string | – | Newsletter name, e.g. 'Build What Matters' |
No output schema declared.
No examples provided.
list_niches List newsletter niches ~39
List BeeDirectory niches with how many newsletters each has (and how many have sourced numbers), plus the typical sponsorship price per 1,000 subscribers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_newsletters Search newsletters to sponsor ~192
Search BeeDirectory for newsletters to sponsor. Returns newsletters whose numbers have a source (verified via the beehiiv or Kit API or a public page, or published by the owner), with subscribers, open rate, sponsorship price per send, price per 1,000 subscribers, rate card and the listing URL. Verified newsletters come first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of results (default 10, max 20) |
| maxPricePerSend | integer | – | Budget per send in USD |
| maxSubscribers | integer | – | – |
| minSubscribers | integer | – | – |
| niche | string | – | Niche id (see list_niches), e.g. 'ai', 'marketing', 'personal-development' |
| query | string | – | Keywords matched against name and description, e.g. 'productivity' or 'devtools' |
| verifiedOnly | boolean | – | Only newsletters whose audience is verified |
No output schema declared.
No examples provided.
How do I install the BeeDirectory MCP server?
BeeDirectory is a hosted endpoint at https://bee-directory.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 · bee-directory.com
claude mcp add --transport http com-bee-directory-newsletter-sponsorship 'https://bee-directory.com/api/mcp'
What is the BeeDirectory MCP server?
BeeDirectory is an MCP server listed in the public MCP registry as com.bee-directory/newsletter-sponsorship. Find newsletters to sponsor: verified audience, sponsorship prices and sources from BeeDirectory. This page covers its hosted endpoint (https://bee-directory.com/api/mcp).
Is the BeeDirectory MCP server safe to use?
BeeDirectory scores 75 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 BeeDirectory MCP server expose?
BeeDirectory exposes 3 tools: search_newsletters, get_newsletter, list_niches. Their descriptions and schemas cost roughly 317 tokens of context every time the server is loaded.
Does the BeeDirectory MCP server require authentication?
No. We connected to BeeDirectory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BeeDirectory MCP server still maintained?
BeeDirectory 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 BeeDirectory MCP server?
VerifyMCP ran 13 checks on BeeDirectory, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.