What is the iTechSmart MCP Server and what can it do?

The iTechSmart MCP Server exposes 7 live tools that let any MCP-compatible agent framework — Claude, LangGraph, CrewAI, or AutoGen — directly invoke the full UAIO (Unified Autonomous IT Operations) pipeline. Every call is governed by The Arbiter policy engine and produces a cryptographic ProofLink receipt anchored to Bitcoin via OpenTimestamps.

What is the difference between the REST API, MCP Server, and A2A protocol?

All three reach the same UAIO pipeline. REST (api.itechsmart.dev/v1) works from any HTTP client — webhooks, CI pipelines, or custom scripts. MCP (mcp.itechsmart.dev) is purpose-built for agent frameworks that speak the Model Context Protocol. A2A follows the Linux Foundation Agent-to-Agent standard and allows fully autonomous agent-to-agent orchestration via a shared agent card schema.

Do I need an API key to verify a ProofLink receipt?

No. Receipt verification at api.itechsmart.dev/v1/verify/{receipt_id} is public and requires no authentication. It returns chain_status, anchored, and verified fields in a single JSON response. Over 30,000 receipts have been sealed to date.

Which agent frameworks are compatible with the iTechSmart MCP Server?

Any framework that implements the Model Context Protocol works out of the box, including Claude (Anthropic), LangGraph, CrewAI, and AutoGen. For agent-to-agent orchestration, any framework supporting the Linux Foundation A2A schema can connect via mcp.itechsmart.dev using the published agent card at /.well-known/agent.json.

How is every API action governed and auditable?

Every remediation decision routed through the API is validated by The Arbiter, iTechSmart's governance engine, before execution. The result is sealed as a SHA-256 hash-chained ProofLink receipt that is Bitcoin-anchored via OpenTimestamps and publicly verifiable at verify.itechsmart.dev — providing a tamper-evident audit trail for compliance purposes including HIPAA and FedRAMP.

Where can I find the MCP tool manifest and API documentation?

The live MCP tool manifest is at mcp.itechsmart.dev/mcp/tools. Full interactive API documentation is at api.itechsmart.dev/docs. The A2A agent card is published at mcp.itechsmart.dev/.well-known/agent.json. All endpoints are live with no authentication required for read operations.

Developer Integration · REST / MCP / A2A

Built for agents,
not just dashboards.

Three ways to invoke the full UAIO pipeline — REST for anything that speaks HTTP, MCP for agent frameworks, and the Linux Foundation A2A protocol for agent-to-agent orchestration. All governed. All receipted.

API Docs API Health — Live

Three doors, one pipeline

Pick your integration path.

LIVE

🌐

REST API

ProofLink verification, incident state, platform status — direct HTTPS. Use from webhooks, CI pipelines, or any tool that speaks HTTP.

api.itechsmart.dev/v1 →

7 TOOLS LIVE

🔌

MCP Server

7 MCP tools available — any MCP-compatible agent invokes the full UAIO pipeline directly. Connect Claude, LangGraph, CrewAI, or any agent framework.

Tool manifest →

NOW LIVE

🤝

A2A Protocol

Linux Foundation Agent-to-Agent protocol on the same endpoint as MCP. Any LangGraph, CrewAI, or AutoGen agent orchestrates Supreme through one standard schema.

View agent card →

Hello, pipeline

From zero to a verified receipt in one call.

verify a receipt — curl

# Verify any ProofLink receipt — no auth required
curl https://api.itechsmart.dev/v1/verify/f0b71cc0970c96e2

{
  "receipt_id": "f0b71cc0970c96e2",
  "chain_status": "intact",
  "anchored": true,
  "verified": true
}

Agents welcome

Wire your agent into governed, receipted execution.

Read the Docs Talk to Engineering