API Tools
heypage.io
Provides Heypage developer resources, billing plan details, sandbox analytics, and API usage guidance for agents.
ENDPOINT 1
https://heypage.io/mcp
MCP server metadata
- Name
- heypage
- Version
- 1.0.0
Heypage MCP: privacy-friendly analytics. Use tools for plans, sandbox stats, and developer resource URLs. Live customer stats require a signed-in Heypage workspace.
Known tools 4
heypage_get_plansList published Heypage billing plans (EUR), trial length, and yearly discount.
Inferred read-onlyheypage_get_sandbox_statsReturn deterministic Heypage sandbox analytics for agent tests.
Inferred read-onlyheypage_get_developer_resourcesHeypage developer entry points: OpenAPI, llms.txt, MCP, OAuth metadata, docs, sandbox, when-to-use guidance.
Inferred read-onlyheypage_search_when_to_useReturn Heypage when-to-use guidance and how an agent should call the product (REST, OpenAPI, MCP).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.heypage]
url = "https://heypage.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"heypage": {
"type": "http",
"url": "https://heypage.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: heypage
Remote MCP URL: https://heypage.io/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"heypage": {
"url": "https://heypage.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"heypage": {
"type": "http",
"url": "https://heypage.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "heypage",
"transport": "streamable-http",
"url": "https://heypage.io/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.