INITE AI Visibility
MCP server · inite.ai · found in a public registry · checked since 2026-10-17
Client error (4xx) · latest check
GET https://inite.ai/api/mcpThe name is the registry's label, not ours. Not reviewed by a person. See 3 endpoints from inite.ai.
Our checks
An unpaid request daily, from eastern North AmericaLast 2 checks, oldest to newest; room for 28 more
1 passed, 1 failed, 28 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Details
Listing
In the capability tree: Web access and automation / Website analysis / Brand visibility in AI answers (primary); Web access and automation / Website analysis / Check whether AI agents can read a site. Placed by a small AI model, where agents with the tasks it serves would look first (placement-ai/2, tree/3) on 2026-10-18. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/3): ✗ what it does is unclear to our placement; ✗ its latest check did not pass.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:MIA |
Client error (4xx) HTTP 404 not an answer an MCP endpoint gives to a plain request |
316 ms |
cloudflare:MIA |
Live, MCP endpoint answered HTTP 405 | 656 ms |
What these figures do not show
- A passing check means the endpoint answered a plain request the way an MCP endpoint does (mcp-reach/1): it is reachable. It does not show that the server's tools work, what they return, or whether they need an account.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. The registry's description is not republished.
- Limited evidence: monitored for 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_088f33f13a68f769