MCP server

A remote Model Context Protocol server over Streamable HTTP. Read-only, and the same data as the REST API.


URL	`https://people-api.arihaan.ai/mcp`
Transport	Streamable HTTP
Auth	OAuth 2.1 (AI apps) or `Authorization: Bearer <API key>`
Protected resource metadata	`https://people-api.arihaan.ai/.well-known/oauth-protected-resource/mcp`
Authorization server metadata	`https://people-api.arihaan.ai/.well-known/oauth-authorization-server`
Tools	4 tools, all marked read-only

Raw JSON-RPC#

Most people never see this layer, but it helps when debugging:

bash

curl -s https://people-api.arihaan.ai/mcp \
  -H "Authorization: Bearer $ARIHAAN_PEOPLE_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"count_people","arguments":{"title":["cto"],"countries":["GB"],"industry":["banking"]}}}'

Inspect it#

bash

npx @modelcontextprotocol/inspector
# Transport: Streamable HTTP · URL: https://people-api.arihaan.ai/mcp
# Header:    Authorization: Bearer YOUR_API_KEY

Every tool that reads people counts as one request. describe_catalog is free, so a model can read the manual as often as it likes.