DeployIt Product Expert
REMOTE · MCP.DEPLOYIT.AI · SCANNED SEP 25
AI product expert answering from live source code, with sources and a verification status.
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 3 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 Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 678 tokens (~226/item across 3 items; 3 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 Management83
- Stability observed for 25 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 DeployIt Product Expert MCP server?
DeployIt Product Expert is a hosted endpoint at https://mcp.deployit.ai/demo, 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 · mcp.deployit.ai
claude mcp add --transport http ai-deployit-product-expert 'https://mcp.deployit.ai/demo'
{
"mcpServers": {
"ai-deployit-product-expert": {
"url": "https://mcp.deployit.ai/demo"
}
}
} {
"servers": {
"ai-deployit-product-expert": {
"type": "http",
"url": "https://mcp.deployit.ai/demo"
}
}
} [mcp_servers.ai-deployit-product-expert] url = "https://mcp.deployit.ai/demo"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-deployit-product-expert": {
"type": "remote",
"url": "https://mcp.deployit.ai/demo",
"enabled": true
}
}
} openclaw mcp add ai-deployit-product-expert --url 'https://mcp.deployit.ai/demo' --transport streamable-http
mcp_servers:
ai-deployit-product-expert:
url: "https://mcp.deployit.ai/demo" {
"McpServers": {
"ai-deployit-product-expert": {
"Transport": "http",
"Url": "https://mcp.deployit.ai/demo"
}
}
} assistant mcp add ai-deployit-product-expert -t streamable-http -u 'https://mcp.deployit.ai/demo'
{
"mcpServers": {
"ai-deployit-product-expert": {
"type": "http",
"url": "https://mcp.deployit.ai/demo"
}
}
} 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
- 24 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.
- 22 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.
- 20 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.
- 17 Sept 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.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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 25 Sept 2026 · Probed https://mcp.deployit.ai/demo
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.deployit.ai | CN=WE1,O=Google Trust Services,C=US | 31 Aug 2026 | 29 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | d1b427d198490f2a13ca566a2e0a5f08 |
| SANs: mcp.deployit.ai | ||||||
| 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 mcp.deployit.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| deployit.ai. | 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://mcp.deployit.ai/demo | Verified | 200 | |
| http (plaintext) | http://mcp.deployit.ai/demo | HTTPS enforced | 301 | https://mcp.deployit.ai/demo |
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 →
ask_product_expert Ask the product expert ~503
Ask a question about "deployit" and get an answer verified against its live source code and git history. Use it for anything about product behavior, features, settings, limits, error messages, or recent changes. HOW IT WORKS AND HOW LONG IT TAKES: the expert genuinely investigates — it searches and reads the product's real source code before answering. A fresh investigation takes 20-60 SECONDS. Do not give up early, and if a human is waiting, tell them the verified answer may take up to a minute. Repeated questions asked without `context` are served from cache in under a second; the cache resets whenever the product's code changes. IF IT TIMES OUT: you get an error saying the expert could not finish in time. The investigation KEEPS RUNNING in the background — re-ask the IDENTICAL question (same wording, no `context`) about a minute later and the finished answer is served instantly from cache. Retry with the same words; rephrasing restarts the investigation. READING THE ANSWER: it ends with a Sources block (the files and commits actually consulted) and a Verification status carrying both confidence and polarity: - verified: confirmed in the code — safe to relay. - backend_only: the capability exists server-side but has no visible UI path. - not_found: searched, and it does NOT exist — a factual "no", relayable as such. - unknown: the expert could not conclude — do NOT relay as fact; consider retrying with depth "thorough". LIMITS: strictly read-only — it can never change anything. Some topics may be refused by the project's policy. A monthly question quota may apply (the error message says so when reached; cached answers never count). At most 60 requests per minute per access key.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional context from your own conversation with the end user (symptoms, plan, what they tried…). Makes the answer more targeted, but context-carrying questions are never cached — omit it for generic… |
| depth | string | – | quick (default): up to ~1 minute of investigation, right for support questions. thorough: digs much deeper for hard questions — expect the timeout-then-retry-from-cache flow. |
| question | string | yes | The question about the product, as specific as possible. Identical wording hits the cache — when retrying after a timeout, repeat the question verbatim. |
No output schema declared.
No examples provided.
get_recent_changes Recent product changes ~101
Instant list of recent changes to "deployit" — the semantic changelog derived from its commits. No AI processing: responds in under a second, costs nothing, and never counts against any quota. Use this FIRST for "what changed", "what's new", "since when" questions; escalate to ask_product_expert only when you need an investigated answer.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | How many days back (default 14, max 90). |
No output schema declared.
No examples provided.
server_info Server info ~74
Describe this MCP server: which product it answers for, which repositories back it, and how fresh the underlying code index is. Instant (no AI). Call it once at the start of a session to confirm you are talking to the right product — if the index is stale or still building, say so instead of trusting deep answers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the DeployIt Product Expert MCP server?
DeployIt Product Expert is an MCP server listed in the public MCP registry as ai.deployit/product-expert. AI product expert answering from live source code, with sources and a verification status. This page covers its hosted endpoint (https://mcp.deployit.ai/demo).
Is the DeployIt Product Expert MCP server safe to use?
DeployIt Product Expert 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 DeployIt Product Expert MCP server expose?
DeployIt Product Expert exposes 3 tools: server_info, get_recent_changes, ask_product_expert. Their descriptions and schemas cost roughly 678 tokens of context every time the server is loaded.
Does the DeployIt Product Expert MCP server require authentication?
No. We connected to DeployIt Product Expert without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DeployIt Product Expert MCP server still maintained?
DeployIt Product Expert 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.