Mash Prime
REMOTE · MASHPRIME.DEV · SCANNED OCT 15
Read Mash Prime's essays and build notes on agentic systems, memory, approvals, and workflows.
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 Security63
- 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 5 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 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 Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 287 tokens (~57/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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
How do I install the Mash Prime MCP server?
Mash Prime is a hosted endpoint at https://mashprime.dev/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 · mashprime.dev
claude mcp add --transport http dev-mashprime-mashprime 'https://mashprime.dev/mcp'
{
"mcpServers": {
"dev-mashprime-mashprime": {
"url": "https://mashprime.dev/mcp"
}
}
} {
"servers": {
"dev-mashprime-mashprime": {
"type": "http",
"url": "https://mashprime.dev/mcp"
}
}
} [mcp_servers.dev-mashprime-mashprime] url = "https://mashprime.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-mashprime-mashprime": {
"type": "remote",
"url": "https://mashprime.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-mashprime-mashprime --url 'https://mashprime.dev/mcp' --transport streamable-http
mcp_servers:
dev-mashprime-mashprime:
url: "https://mashprime.dev/mcp" {
"McpServers": {
"dev-mashprime-mashprime": {
"Transport": "http",
"Url": "https://mashprime.dev/mcp"
}
}
} assistant mcp add dev-mashprime-mashprime -t streamable-http -u 'https://mashprime.dev/mcp'
{
"mcpServers": {
"dev-mashprime-mashprime": {
"type": "http",
"url": "https://mashprime.dev/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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 47. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_posts” rewrote its description, which is the text the model reads security
- Schema quality: 217 → 287 ▼ functional
- Schema quality: excellent → good functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “related_posts” functional
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 30. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 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.
- 2 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.
- 30 Sept 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.
- 29 Sept 26 0
- Stability: unverified → 0.03 ▲ 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 15 Oct 2026 · Probed https://mashprime.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mashprime.dev | CN=YE1,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6a41f1638688c6362db701a62b84dd952d1 |
| SANs: mashprime.dev, www.mashprime.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 mashprime.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| mashprime.dev. | 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 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mashprime.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mashprime.dev/mcp | HTTPS enforced | 301 | https://mashprime.dev/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 →
list_posts ~27
List all published blog posts with slug, title, description, and publication date, newest first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_post ~46
Read the full markdown text of one blog post by slug (get slugs from list_posts).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Post slug, e.g. 'one-folder-to-autonomy' |
No output schema declared.
No examples provided.
related_posts ~77
Posts closest in meaning to a given post, by similarity of their text embeddings, most similar first. Use to follow a thread of ideas from one post to the next.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many posts to return (default 3) |
| slug | string | yes | Post slug, e.g. 'one-folder-to-autonomy' |
No output schema declared.
No examples provided.
search_posts ~50
Search blog posts across titles, descriptions, and full text, ranked best match first. Returns matching posts with the most relevant passage as a snippet.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Keyword or phrase to search for |
No output schema declared.
No examples provided.
site_info ~39
Orientation: who Mash Prime is, what the site covers, when to use it, and every page — returned as markdown (the site's llms.txt).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Mash Prime MCP server?
Mash Prime is an MCP server listed in the public MCP registry as dev.mashprime/mashprime. Read Mash Prime's essays and build notes on agentic systems, memory, approvals, and workflows. This page covers its hosted endpoint (https://mashprime.dev/mcp).
Is the Mash Prime MCP server safe to use?
Mash Prime 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 Mash Prime MCP server expose?
Mash Prime exposes 5 tools: site_info, list_posts, read_post, search_posts, related_posts. Their descriptions and schemas cost roughly 239 tokens of context every time the server is loaded.
Does the Mash Prime MCP server require authentication?
No. We connected to Mash Prime without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Mash Prime MCP server still maintained?
Mash Prime is still listed as active in the MCP registry. We last reached this channel on 15 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.