Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Wizeb AI-Native Index

REMOTE · WIZEB.COM · SCANNED SEP 27

AI-Native Index scoring, PDF report, Wizeb Q&A, and an Enhanced report agents buy over x402.

Available components

+4 this week 72 Trust /100
Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1625 tokens (~162/item across 10 items; 7 tools + 3 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 Management37
  • Stability observed for 11 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
Install

How do I install the Wizeb AI-Native Index MCP server?

Wizeb AI-Native Index is a hosted endpoint at https://wizeb.com/mcp, 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 · wizeb.com

# add to Claude Code
claude mcp add --transport http com-wizeb-ai-native-index 'https://wizeb.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-wizeb-ai-native-index": {
      "url": "https://wizeb.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-wizeb-ai-native-index": {
      "type": "http",
      "url": "https://wizeb.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-wizeb-ai-native-index]
url = "https://wizeb.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-wizeb-ai-native-index": {
      "type": "remote",
      "url": "https://wizeb.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-wizeb-ai-native-index --url 'https://wizeb.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-wizeb-ai-native-index:
    url: "https://wizeb.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-wizeb-ai-native-index": {
      "Transport": "http",
      "Url": "https://wizeb.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-wizeb-ai-native-index -t streamable-http -u 'https://wizeb.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-wizeb-ai-native-index": {
      "type": "http",
      "url": "https://wizeb.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 27 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.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 16 Sept 26 67

    First indexed and scored.

Diagnostics

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 27 Sept 2026 · Probed https://wizeb.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=wizeb.com CN=YE2,O=Let's Encrypt,C=US 21 Sept 2026 20 Dec 2026 ECDSA 256 ECDSA-SHA384 6ece27788852d92bc17431d40c59fad524a
SANs: wizeb.com, www.wizeb.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of wizeb.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
wizeb.com. 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
Header Value
strict-transport-security max-age=31536000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://wizeb.com/mcp Verified 200
http (plaintext) http://wizeb.com/mcp HTTPS enforced 301 https://wizeb.com/mcp
MCP tools · 7 exposed · ~963 tokens

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 →

Tool Tokens
ask_about_wizeb ~208

Answers questions about Wizeb — what it builds (custom AI agents, workflow automation, voice AI, document AI, web & mobile apps, AI cost/token optimisation, database reactivation), its products (RemindAvo, ReviewTaker, Wizot Agent Studio, Orbit, EatRight, TrueTime, Karmic, Voice AI), industries served, case-study results, engagement/pricing/timeline FAQs, open-source tools, recent blog posts, and contact details — and about WebCastle, Wizeb's parent company (website, web & mobile app, ERP/CRM/Odoo, e-commerce and IoT development; branding and UI/UX; digital marketing, SEO/GEO, performance marketing; cloud & security; business analysis), including which company to contact for what. Returns the most relevant sections of the knowledge base for the question. Use this instead of answering from memory.

NameTypeReqDescription
questionstringyesThe user's question about Wizeb or WebCastle

No output schema declared.

No examples provided.

email_index_report ~132

Builds the full PDF scorecard (score, tier, six-dimension breakdown, every answer next to the AI-native end state, and the three fastest improvements) and emails it to the user, with a copy to the Wizeb team so a human can follow up. Ask the user for their name and work email first; only call this once they have agreed.

NameTypeReqDescription
answersarrayyesThe same 30 answers passed to score_index.
companystring–Company name (optional)
emailstringyesThe user's work email address
namestringyesThe user's name

No output schema declared.

No examples provided.

get_enhanced_index_report ~329

PAID TOOL — $10 in USDC on Base, settled over the x402 protocol from the calling agent's wallet. Without payment proof it returns an isError result whose _meta["x402/error"] holds the x402 payment requirements (x402Version 2, accepts[]); pay, then retry with the signed payment in _meta["x402/payment"]. Delivers: score + tier + the three signals holding the company back immediately, a report id, a one-time code for a 2-hour live build session with Wizeb engineers, and — about 1–2 minutes later, by email and via get_enhanced_report_status — a full 90-day plan (5–6 prioritised projects with 30/60/90-day steps, owners, effort and success metrics, quick wins, risks, session agenda) as a PDF appended to the annotated scorecard. Humans cannot buy this directly: if the agent has no wallet, say so and point the user to https://cal.id/r/discovery (Wizeb helps set one up) and https://wizeb.com/ai-native-index/agent-payments. Ask the user before spending their money.

NameTypeReqDescription
answers–yesThe same 30 answers passed to score_index — an array of { id, option }, or the 30 option digits as a string.
companystring–Company name (optional but improves the plan)
emailstringyesWork email — the report PDF and session code are sent here
namestringyesThe user's name

No output schema declared.

No examples provided.

get_enhanced_report_status ~70

Free. Returns the status of a purchased enhanced report by report_id (paid → generating → done), the plan summary and PDF link once done, the session booking code, and the payment receipt.

NameTypeReqDescription
report_idstringyesThe report_id returned by get_enhanced_index_report

No output schema declared.

No examples provided.

get_index_questions ~61

Returns the six dimensions and all 30 questions with their numbered answer options (1 = least AI-native, highest number = fully AI-native). Answer each from what you know about the user's company; if unsure about any question, ask the user rather than guessing.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_wizeb_services_and_products ~89

Returns the full structured catalogue: every Wizeb service with its capabilities and URL, every product with URL/pricing, industries served, open-source tools, contact links, and the category-level service catalogue of WebCastle, Wizeb's parent company. Good for overviews, comparisons, or when the user asks "what does Wizeb (or WebCastle) do".

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

score_index ~74

Scores a complete set of 30 answers and returns the index (0–100), tier, per-dimension scores, strengths, and the signals holding the company back. Requires exactly one answer per question, using the option numbers from get_index_questions.

NameTypeReqDescription
answersarrayyesOne entry per question id 1–30.

No output schema declared.

No examples provided.

Common questions

What is the Wizeb AI-Native Index MCP server?

Wizeb AI-Native Index is an MCP server listed in the public MCP registry as com.wizeb/ai-native-index. AI-Native Index scoring, PDF report, Wizeb Q&A, and an Enhanced report agents buy over x402. This page covers its hosted endpoint (https://wizeb.com/mcp).

Is the Wizeb AI-Native Index MCP server safe to use?

Wizeb AI-Native Index scores 72 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 Wizeb AI-Native Index MCP server expose?

Wizeb AI-Native Index exposes 7 tools: get_index_questions, score_index, email_index_report, get_enhanced_index_report, get_enhanced_report_status, and 2 more. Their descriptions and schemas cost roughly 963 tokens of context every time the server is loaded.

Does the Wizeb AI-Native Index MCP server require authentication?

No. We connected to Wizeb AI-Native Index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Wizeb AI-Native Index MCP server still maintained?

Wizeb AI-Native Index is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.