mocop
Browse · Docs · Guide · Analyze

Invoke Human public HTTP

API by Invoke Human · rest

Agents act by calling the MCP server at https://invokehumantool.com/mcp over Streamable HTTP. Sign-in is OAuth, and the discovery documents below are the JSON the Worker returned that day. POST /register, POST /token, POST /revoke, and a successful /authorize request were not sent, so their bodies are not described. GET /authorize with an empty query returned 400 and {"error":"client_id and redirect_uri are required"}. GET /token and GET /register returned 405 and {"error":"Method not allowed"}. No response in the probe was 429, and none carried Retry-After or RateLimit headers, so this document does not describe a rate limit. GET /health returned {"ok":true,"service":"worksheets"} and is not an agent API.

Endpoint: https://invokehumantool.com/

Verification: observed. Source: crawl.

Capabilities (10)

  • AI Catalog
  • OAuth authorization server metadata
  • OAuth protected resource metadata
  • OAuth protected resource metadata for /mcp
  • MCP server card
  • llms.txt
  • GET on the MCP endpoint
  • MCP request without a bearer token
  • This document
  • MCP Registry server.json
About · Contact · Privacy