md.install/try
REMOTE · INSTALL.MD · SCANNED SEP 25
Create guides as MCP servers to instruct coding agents to use your software (library, API, etc).
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 Security57
- 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 13 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
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 925 tokens (~71/item across 13 items; 13 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 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_project" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the md.install/try MCP server?
md.install/try is a hosted endpoint at https://install.md/mcp/try, 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 · install.md
claude mcp add --transport http md-install-try 'https://install.md/mcp/try'
{
"mcpServers": {
"md-install-try": {
"url": "https://install.md/mcp/try"
}
}
} {
"servers": {
"md-install-try": {
"type": "http",
"url": "https://install.md/mcp/try"
}
}
} [mcp_servers.md-install-try] url = "https://install.md/mcp/try"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"md-install-try": {
"type": "remote",
"url": "https://install.md/mcp/try",
"enabled": true
}
}
} openclaw mcp add md-install-try --url 'https://install.md/mcp/try' --transport streamable-http
mcp_servers:
md-install-try:
url: "https://install.md/mcp/try" {
"McpServers": {
"md-install-try": {
"Transport": "http",
"Url": "https://install.md/mcp/try"
}
}
} assistant mcp add md-install-try -t streamable-http -u 'https://install.md/mcp/try'
{
"mcpServers": {
"md-install-try": {
"type": "http",
"url": "https://install.md/mcp/try"
}
}
} 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.
- 25 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
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 6 Aug 26 0
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → fair ▲ functional
- Schema quality: unverified → pass ▲ functional
- First check of Schema quality: 100 functional
- First check of Tool coverage: 100 functional
- New prompt “create_project_guide” functional
- New tool “add_data_source” functional
- New tool “add_tool” functional
- New tool “create_project” functional
- New tool “create_session” functional
- New tool “delete_data_source” functional
- New tool “delete_project” functional
- New tool “delete_tool” functional
- New tool “get_project_details” functional
- New tool “list_projects” functional
- New tool “reorder_steps” functional
- New tool “toggle_tool” functional
- New tool “update_project” functional
- New tool “update_tool” functional
- 31 Jul 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
- 30 Jul 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 Jul 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
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 25 Sept 2026 · Probed https://install.md/mcp/try
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=install.md | CN=WE1,O=Google Trust Services,C=US | 23 Aug 2026 | 21 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 60ce8dbdca609fed139401af0ab7e390 |
| SANs: install.md | ||||||
| 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 install.md. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| md. | present | 127 | 14 | Verified |
| install.md. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://install.md/mcp/try | Verified | 200 | |
| http (plaintext) | http://install.md/mcp/try | HTTPS enforced | 301 | https://install.md/mcp/try |
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 →
add_data_source ~74
Add a new data source to a project
| Name | Type | Req | Description |
|---|---|---|---|
| project_slug | string | yes | The slug of the project to add the data source to |
| session_id | string | yes | The anonymous session ID |
| type | string | yes | The type of data source |
| url | string | yes | The URL of the data source |
No output schema declared.
No examples provided.
add_tool ~168
Add a new tool/step to a project
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Description of what the tool does |
| display_name | string | yes | The human-readable display name of the tool |
| is_enabled | boolean | – | Whether the tool is enabled |
| name | string | yes | The unique name of the tool (used as identifier) |
| project_slug | string | yes | The slug of the project to add the tool to |
| response_template | string | – | Markdown template for tool response |
| session_id | string | yes | The anonymous session ID |
| step_order | number | – | The order of this step in the project workflow |
| tool_schema | string | – | JSON schema for tool parameters |
| tool_type | string | – | The type of tool (step, builtin, tip) |
No output schema declared.
No examples provided.
create_project ~88
Create a new project in the anonymous session
| Name | Type | Req | Description |
|---|---|---|---|
| is_public | boolean | – | Whether the project is public or private |
| name | string | yes | The display name of the project |
| overview_content | string | – | Markdown content for the project overview |
| session_id | string | yes | The anonymous session ID |
| slug | string | yes | The URL slug for the project (used in URLs) |
No output schema declared.
No examples provided.
create_session ~17
Create a new anonymous session for managing projects
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
delete_data_source ~46
Delete a data source from a project
| Name | Type | Req | Description |
|---|---|---|---|
| data_source_id | string | yes | The ID of the data source to delete |
| session_id | string | yes | The anonymous session ID |
No output schema declared.
No examples provided.
delete_project ~43
Delete a project from the anonymous session
| Name | Type | Req | Description |
|---|---|---|---|
| project_slug | string | yes | The slug of the project to delete |
| session_id | string | yes | The anonymous session ID |
No output schema declared.
No examples provided.
delete_tool ~42
Delete a tool from a project
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | The anonymous session ID |
| tool_id | string | yes | The ID of the tool to delete |
No output schema declared.
No examples provided.
get_project_details ~49
Get detailed information about a specific project in the session
| Name | Type | Req | Description |
|---|---|---|---|
| project_slug | string | yes | The slug of the project to get details for |
| session_id | string | yes | The anonymous session ID |
No output schema declared.
No examples provided.
list_projects ~28
List all projects in the anonymous session
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | The anonymous session ID |
No output schema declared.
No examples provided.
reorder_steps ~63
Reorder tools/steps in a project
| Name | Type | Req | Description |
|---|---|---|---|
| project_slug | string | yes | The slug of the project to reorder tools in |
| session_id | string | yes | The anonymous session ID |
| tool_orders | array | yes | Array of tool IDs and their new step orders |
No output schema declared.
No examples provided.
toggle_tool ~44
Toggle a tool's enabled/disabled state
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | The anonymous session ID |
| tool_id | string | yes | The ID of the tool to toggle |
No output schema declared.
No examples provided.
update_project ~103
Update an existing project in the anonymous session
| Name | Type | Req | Description |
|---|---|---|---|
| is_public | boolean | – | Whether the project is public or private |
| name | string | – | The display name of the project |
| overview_content | string | – | Markdown content for the project overview |
| project_slug | string | yes | The slug of the project to update |
| session_id | string | yes | The anonymous session ID |
| slug | string | – | The URL slug for the project (used in URLs) |
No output schema declared.
No examples provided.
update_tool ~160
Update an existing tool
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Description of what the tool does |
| display_name | string | – | The human-readable display name of the tool |
| is_enabled | boolean | – | Whether the tool is enabled |
| name | string | – | The unique name of the tool (used as identifier) |
| response_template | string | – | Markdown template for tool response |
| session_id | string | yes | The anonymous session ID |
| step_order | number | – | The order of this step in the project workflow |
| tool_id | string | yes | The ID of the tool to update |
| tool_schema | string | – | JSON schema for tool parameters |
| tool_type | string | – | The type of tool (step, builtin, tip) |
No output schema declared.
No examples provided.
What is the md.install/try MCP server?
md.install/try is an MCP server listed in the public MCP registry as md.install/try. Create guides as MCP servers to instruct coding agents to use your software (library, API, etc). This page covers its hosted endpoint (https://install.md/mcp/try).
Is the md.install/try MCP server safe to use?
md.install/try scores 77 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 md.install/try MCP server expose?
md.install/try exposes 13 tools: create_session, list_projects, get_project_details, create_project, update_project, and 8 more. Their descriptions and schemas cost roughly 925 tokens of context every time the server is loaded.
Does the md.install/try MCP server require authentication?
No. We connected to md.install/try without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the md.install/try MCP server still maintained?
md.install/try is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.