How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Unified MCP Service

The Unified MCP Service is the company's agent-facing surface. Its remote Model Context Protocol endpoint at https://mcp.unified.com/mcp answers JSON-RPC over HTTP and is gated by OAuth bearer tokens issued by https://mcp.unified.com/; an anonymous tools/list call returns 401 invalid_token with an RFC 6750 WWW-Authenticate challenge naming the RFC 9728 resource metadata document. The same FastAPI build is served on api.unified.com, which publishes an OpenAPI 3.1.0 description covering the root and health/readiness/liveness endpoints.

Unified MCP Service is published by Unified on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include MCP, Agents, and Advertising. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 5 paths, organized into 2 resource areas, and defines 2 schemas. It is described by OpenAPI 3.1.0, at version 0.0.59.

Requests are made against the base URL https://api.unified.com.

5 operations 5 paths 2 schemas 5 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
0.0.59
Base URL
https://api.unified.com
Resource Areas
2

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 5 GET. They span 2 resource areas: Operations, health. Each is listed below with its method, path, parameters, and response codes.

Operations 1
GET
/
Root
root__get → 200
health 4
GET
/health/
Health Check
health_check_health__get → 200
GET
/health
Health Check
health_check_health_get → 200
GET
/health/ready
Readiness Check
readiness_check_health_ready_get → 200
GET
/health/live
Liveness Check
liveness_check_health_live_get → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are SuccessResponse (2 properties), HealthCheckResponse (2 properties). Each schema is shown below with its type and property counts.

HealthCheckResponse
object
Health check response payload.
2 properties 2 required
SuccessResponse
object
Standard success response payload.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

unified-mcp-service-openapi.json Raw ↑
Where this information came from

This is an independent, third-party profile of Unified MCP Service, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.