{
  "markdown": "# Hitsteps MCP Server\n\nPublic metadata and setup notes for the Hitsteps remote Model Context Protocol\nserver.\n\nHitsteps exposes a hosted MCP server for analytics and website operations:\n\n```text\nhttps://www.hitsteps.com/mcp/\n```\n\nThe current registry metadata release is `1.1.6`. This repository is\nintentionally small: it contains public registry metadata and setup notes, not\nthe production Hitsteps PHP service, private OAuth keys, reviewer accounts,\ncustomer data, or deployment credentials.\n\n## Install\n\nUse the full Hitsteps setup and security guide:\n\n```text\nhttps://www.hitsteps.com/plugin/?type=mcp\n```\n\nAvailable client paths:\n\n- VS Code and GitHub Copilot: use the [GitHub MCP Registry](https://github.com/mcp).\n- Cursor: use the [Hitsteps Cursor Directory listing](https://cursor.directory/plugins/hitsteps-web-analytics).\n- Claude: use the [Claude Connector Directory listing](https://claude.ai/directory/connectors/hitsteps-web-analytics).\n- ChatGPT: the directory listing is coming soon; add `https://www.hitsteps.com/mcp/` as a custom MCP server for now.\n- Google Antigravity and other clients: add the remote Streamable HTTP endpoint below and complete Hitsteps OAuth.\n\nGoogle Antigravity configuration:\n\n```json\n{\n  \"mcpServers\": {\n    \"Hitsteps\": {\n      \"serverUrl\": \"https://www.hitsteps.com/mcp/\"\n    }\n  }\n}\n```\n\nThe same managed endpoint is used by every client. There is no local package,\nNode.js process, desktop bridge, SSE worker, or separate customer-hosted\nservice to install.\n\n## Registry Metadata\n\nThe root [`server.json`](server.json) file is the canonical public metadata for\nMCP registries and galleries. It declares:\n\n- registry name: `com.hitsteps/analytics-operations`\n- display title: `Hitsteps Analytics and Operations`\n- transport: Streamable HTTP\n- remote endpoint: `https://www.hitsteps.com/mcp/`\n- icon: `https://www.hitsteps.com/favicon.png`\n- documentation: `https://www.hitsteps.com/plugin/?type=mcp`\n- current metadata version: `1.1.6`\n\nThe `com.hitsteps/analytics-operations` name is domain-authenticated. Keep\nthis identity unless Hitsteps intentionally publishes a second\nGitHub-namespaced entry such as `io.github.Hitsteps/...`.\n\n## Authentication and Safety\n\nHitsteps uses OAuth for public MCP access. Users sign in on Hitsteps and\napprove the requested scopes before the client receives a token. The client\nconfiguration contains only the endpoint URL; never paste a Hitsteps password,\ntracking API key, OAuth token, private key, or reviewer credential into a\nclient configuration or this repository.\n\nThe server rechecks the signed-in account, sub-user permissions, visible\nwebsites, license state, feature limits, and granted OAuth scopes on every\nrequest. Write operations require their specific scope, explicit confirmation,\nand an idempotency key. Results are privacy-shaped and do not expose raw SQL,\nprivate keys, raw visitor-profile dumps, or session-replay video.\n\n## Validation\n\nValidate metadata before publishing:\n\n```sh\nmcp-publisher validate\n```\n\nPublish from this repository only after domain authentication is available to\nthe publisher environment. Private signing keys and domain-authentication\nmaterial must stay outside this repository.\n\n## Security Reports\n\nPlease report suspected vulnerabilities through the [Hitsteps contact\npage](https://www.hitsteps.com/contact.php). Do not open public issues\ncontaining OAuth tokens, customer analytics data, account credentials, private\nkeys, reviewer credentials, or raw request logs with sensitive values.\n",
  "bytes": 3524,
  "sha": "76a082eee639aa88af5ab0f18579e0a5258f002b6ecf0f1639f0013f5abdfa92",
  "repo_slug": "hitsteps/mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_com_hitsteps_analytics_operations_3a211422/readme"
}