mcpgate

mcpgate User Info API

The User Info API from mcpgate — 1 operation(s) for user info.

GitHub OpenAPI

Operations 2

GET /userinfo Userinfo #
POST /userinfo Userinfo #

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/mcpgate/refs/heads/main/openapi/mcpgate-user-info-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/mcpgate/refs/heads/main/json-schema/mcpgate-subscription-row-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/mcpgate/refs/heads/main/json-schema/mcpgate-issue-request-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/mcpgate/refs/heads/main/json-schema/mcpgate-customer-update-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/mcpgate/refs/heads/main/json-schema/mcpgate-message-out-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/mcpgate/refs/heads/main/json-schema/mcpgate-report-request-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/mcpgate/refs/heads/main/json-schema/mcpgate-refresh-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/mcpgate/refs/heads/main/json-schema/mcpgate-tool-call-request-schema.json

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/mcpgate:mcpgate-user-info-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

mcpgate-user-info-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: AI Gateway MCP Server Userinfo API
  description: Universal MCP Gateway with OAuth integration - Modern Architecture
  version: 2.0.3290
tags:
- name: User Info
paths:
  /userinfo:
    get:
      summary: Userinfo
      description: 'OpenID Connect UserInfo for the Bearer token ``/mcp`` accepts.


        The token is validated by the same ``validate_mcp_token`` the MCP

        route uses, but WITHOUT the request headers: a delegation grant

        swaps the resolved identity for a tool call, and a UserInfo answer

        that changed with a header would make one token name two subjects.

        UserInfo states the token''s owner. A rejected token is a 401 Bearer

        challenge (RFC 6750 §3), never a 404, because a relying party reads

        404 as "no such provider".'
      operationId: _userinfo_userinfo_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - User Info
    post:
      summary: Userinfo
      description: 'OpenID Connect UserInfo for the Bearer token ``/mcp`` accepts.


        The token is validated by the same ``validate_mcp_token`` the MCP

        route uses, but WITHOUT the request headers: a delegation grant

        swaps the resolved identity for a tool call, and a UserInfo answer

        that changed with a header would make one token name two subjects.

        UserInfo states the token''s owner. A rejected token is a 401 Bearer

        challenge (RFC 6750 §3), never a 404, because a relying party reads

        404 as "no such provider".'
      operationId: _userinfo_userinfo_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - User Info