# DeployIt Product Expert

> AI product expert answering from live source code, with sources and a verification status.

- name: ai.deployit/product-expert
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 79/100 flags: no-repository
- quality: 76/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/ai.deployit%2Fproduct-expert
- tools: https://api.protogrid.dev/v1/servers/ai.deployit%2Fproduct-expert/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "product-expert": {
      "type": "http",
      "url": "https://mcp.deployit.ai/demo"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 97
- freshness: 85
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-93% ~updated-50d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 76/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 64 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 1 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_recent_changes (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ask_product_expert (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); server_info (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
- pass `tools.token_cost`: about 895 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 3, about 895 tokens to load them all
- tool set hash: b1d631ac270cd683b26a80b643d66aa7
- badge: [![protogrid quality](https://protogrid.dev/badge/ai.deployit/product-expert.svg)](https://protogrid.dev/servers/ai.deployit/product-expert)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://mcp.deployit.ai/demo (streamable-http, auth none, reachable true, uptime30d 0.9279279)

## Packages

_none_

## Tools (3)

- `ask_product_expert`: 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.
- `get_recent_changes`: 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.
- `server_info`: 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.