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.

iTechSmart UAIO

REMOTE · MCP.ITECHSMART.DEV · 2 COMPONENTS · SCANNED SEP 21

Connect AI agents to iTechSmart UAIO, ProofLink verification, and autonomous IT operations.

Available components

remote · mcp.itechsmart.dev 0 npm · @itechsmart/mcp-server 82
−25 this week 0 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 Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the iTechSmart UAIO MCP server?

iTechSmart UAIO is a hosted endpoint at https://mcp.itechsmart.dev/sse, 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.itechsmart.dev

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

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.

  • 16 Sept 26 −5

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 15 Sept 26 −5

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 14 Sept 26 −5

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 13 Sept 26 −5

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 12 Sept 26 −5

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 10 Sept 26 0
    • Transport: unverified → fail ▼ security
    • HSTS header: pass → unverified ▼ security
    • Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools. security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools. functional
    • Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
    • Schema quality: Schema not yet verified: we couldn't read the endpoint's schema. functional
  • 26 Aug 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
  • 11 Aug 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
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 16 Sept 2026 · Probed https://mcp.itechsmart.dev/sse

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=itechsmart.dev CN=YE2,O=Let's Encrypt,C=US 21 Jul 2026 19 Oct 2026 ECDSA 256 ECDSA-SHA384 52b6fe90b5481075a7174ac4391442909a0
SANs: *.itechsmart.dev, itechsmart.dev
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 mcp.itechsmart.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
itechsmart.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

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

Transports 2 probes
Transport URL Outcome Status Location
sse https://mcp.itechsmart.dev/sse Unreachable
http (plaintext) http://mcp.itechsmart.dev/sse HTTPS enforced
MCP tools

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 →

No tool schema has been captured from this endpoint yet.

Common questions

What is the iTechSmart UAIO MCP server?

iTechSmart UAIO is an MCP server listed in the public MCP registry as io.github.Iteksmart/mcp-server. Connect AI agents to iTechSmart UAIO, ProofLink verification, and autonomous IT operations. This page covers its hosted endpoint (https://mcp.itechsmart.dev/sse).

Is the iTechSmart UAIO MCP server safe to use?

iTechSmart UAIO scores 0 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.

Does the iTechSmart UAIO MCP server require authentication?

Its publisher declares that iTechSmart UAIO requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.

Is the iTechSmart UAIO MCP server still maintained?

iTechSmart UAIO has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 9 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.