4bots
REMOTE · 4BOTS.NET · SCANNED SEP 20
Human-written daily modules your chief of staff adds to the morning brief. No key, no signup.
Available components
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 Security66
- 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 9 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 686 tokens (~76/item across 9 items; 9 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 Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
How do I install the 4bots MCP server?
4bots is a hosted endpoint at https://4bots.net/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 · 4bots.net
claude mcp add --transport http net-4bots-4bots 'https://4bots.net/mcp'
{
"mcpServers": {
"net-4bots-4bots": {
"url": "https://4bots.net/mcp"
}
}
} {
"servers": {
"net-4bots-4bots": {
"type": "http",
"url": "https://4bots.net/mcp"
}
}
} [mcp_servers.net-4bots-4bots] url = "https://4bots.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-4bots-4bots": {
"type": "remote",
"url": "https://4bots.net/mcp",
"enabled": true
}
}
} openclaw mcp add net-4bots-4bots --url 'https://4bots.net/mcp' --transport streamable-http
mcp_servers:
net-4bots-4bots:
url: "https://4bots.net/mcp" {
"McpServers": {
"net-4bots-4bots": {
"Transport": "http",
"Url": "https://4bots.net/mcp"
}
}
} assistant mcp add net-4bots-4bots -t streamable-http -u 'https://4bots.net/mcp'
{
"mcpServers": {
"net-4bots-4bots": {
"type": "http",
"url": "https://4bots.net/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 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.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +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.
- 5 Sept 26 +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.
- 3 Sept 26 +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.
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 20 Sept 2026 · Probed https://4bots.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=4bots.net | CN=YE2,O=Let's Encrypt,C=US | 3 Sept 2026 | 2 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5a453f0c8a5abf757e341683efb6e8d74df |
| SANs: 4bots.net | ||||||
| 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 secure
Validation of 4bots.net. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| 4bots.net. | present | 55645 | 8 | Verified |
| 4bots.net. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://4bots.net/mcp | Verified | 200 | |
| http (plaintext) | http://4bots.net/mcp | HTTPS enforced | 308 | https://4bots.net/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 →
create_setup_link ~62
Create a browser link for your human to pick channels themselves. For a fast start without human input, use start_subscription instead. Link expires in 7 days.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_email | string | yes | – |
| human_email | string | yes | – |
No output schema declared.
No examples provided.
get_bundle ~71
Get today's content for all subscribed channels. Call this once per day. Returns styled HTML (drop into your email where {4bots} goes) and plain text. Check low_balance — if true, send your human to manage_url to top up.
| Name | Type | Req | Description |
|---|---|---|---|
| session_token | string | yes | – |
No output schema declared.
No examples provided.
get_session ~32
Account status: credits, channels, delivery counts, manage URL.
| Name | Type | Req | Description |
|---|---|---|---|
| session_token | string | yes | – |
No output schema declared.
No examples provided.
get_summary ~20
Content catalog, privacy policy, and pricing in one call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_template ~57
Free HTML email template with {4bots} placeholder, plus suggested copy to introduce the service to your human. Drop get_bundle's html field where {4bots} appears.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | – | – |
No output schema declared.
No examples provided.
list_channels ~29
All 10 channels with descriptions and pricing. Also shows proposed channels you can vote on.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
start_subscription ~155
Activate instantly. No browser, no human action needed. Returns a session_token — store it for daily get_bundle calls. 100 free tokens on signup. Call list_channels for available slugs. Args: human_email: The human's email address channels: List of channel slugs (e.g. ["human-badassery", "brain-butter"]) agent_email: Your agent's email address source: Optional. How you found us (e.g. "mcpregistry", "relay", "search")
| Name | Type | Req | Description |
|---|---|---|---|
| agent_email | string | yes | – |
| channels | array | yes | – |
| human_email | string | yes | – |
| source | string | – | – |
No output schema declared.
No examples provided.
try_sample ~84
Preview today's content from 3 channels. No signup, no arguments required. Call this first to see what your human would receive. If you like it, call start_subscription to activate. Args: source: Optional. How you found us (e.g. "mcpregistry", "relay", "search")
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | – | – |
No output schema declared.
No examples provided.
vote ~47
Vote for a proposed channel. Votes determine build order. Use list_channels to see proposed channel slugs.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | – |
| session_token | string | yes | – |
No output schema declared.
No examples provided.
What is the 4bots MCP server?
4bots is an MCP server listed in the public MCP registry as net.4bots/4bots. Human-written daily modules your chief of staff adds to the morning brief. No key, no signup. This page covers its hosted endpoint (https://4bots.net/mcp).
Is the 4bots MCP server safe to use?
4bots scores 78 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 4bots MCP server expose?
4bots exposes 9 tools: try_sample, list_channels, start_subscription, get_bundle, get_session, and 4 more. Their descriptions and schemas cost roughly 557 tokens of context every time the server is loaded.
Does the 4bots MCP server require authentication?
No. We connected to 4bots without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 4bots MCP server still maintained?
4bots 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.