Marketing
star-chase.com
Provides access to StarChase Network's marketing agency information, including company details, service offerings, case studies, and developer integration documentation.
ENDPOINT 1
https://www.star-chase.com/mcp
MCP server metadata
- Name
- starchase-official
- Version
- 2.0.0
StarChase Official MCP Server for marketing services, client case studies, and consultation booking.
Known tools 4
CONNECT 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.starchase-official]
url = "https://www.star-chase.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"starchase-official": {
"type": "http",
"url": "https://www.star-chase.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: starchase-official
Remote MCP URL: https://www.star-chase.com/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": {
"starchase-official": {
"url": "https://www.star-chase.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"starchase-official": {
"type": "http",
"url": "https://www.star-chase.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "starchase-official",
"transport": "streamable-http",
"url": "https://www.star-chase.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://www.star-chase.com/api/mcp
MCP server metadata
- Name
- starchase-official
- Version
- 2.0.0
StarChase Official MCP Server for marketing services, client case studies, and consultation booking.
Known tools 4
CONNECT 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.starchase-official]
url = "https://www.star-chase.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"starchase-official": {
"type": "http",
"url": "https://www.star-chase.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: starchase-official
Remote MCP URL: https://www.star-chase.com/api/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": {
"starchase-official": {
"url": "https://www.star-chase.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"starchase-official": {
"type": "http",
"url": "https://www.star-chase.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "starchase-official",
"transport": "streamable-http",
"url": "https://www.star-chase.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 3
https://star-chase.com
MCP server metadata
- Name
- WebMCP
Known tools 1
CONNECT 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.webmcp]
url = "https://star-chase.com"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"webmcp": {
"type": "http",
"url": "https://star-chase.com"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: webmcp
Remote MCP URL: https://star-chase.com
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": {
"webmcp": {
"url": "https://star-chase.com"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"webmcp": {
"type": "http",
"url": "https://star-chase.com"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "webmcp",
"transport": "streamable-http",
"url": "https://star-chase.com"
}
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.