DeployIt Product Expert
ai.deployit/product-expertVersion 1.0.0AI product expert answering from live source code, with sources and a verification status.
Status
Responds222 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:28 UTC
- Latency
- 222 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://mcp.deployit.ai/demoResponds222 msNo sign-in
Claude Code
claude mcp add --transport http product-expert https://mcp.deployit.ai/demoClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: product-expert
Remote MCP server URL: https://mcp.deployit.ai/demoCursor
{
"mcpServers": {
"product-expert": {
"url": "https://mcp.deployit.ai/demo"
}
}
}VS Code
code --add-mcp '{"name":"product-expert","type":"http","url":"https://mcp.deployit.ai/demo"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
3 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
ask_product_expertAsk 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. | Not declared | Not declared | Not declared | Not declared |
get_recent_changesInstant 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. | Not declared | Not declared | Not declared | Not declared |
server_infoDescribe 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. | Not declared | Not declared | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Aug 31, 2026
- Updated
- Aug 31, 2026
- Repository
- Not given
- Categories (suggested)
- SecuritySuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared