← Registry

Marketing

ampliflow.com

An MCP server that lets users book an AmpliFlow demo and subscribe to the AmpliFlow newsletter.

WebMCP1 endpoint2 known toolsFirst detected September 28, 2026Last detected September 28, 2026

ENDPOINT 1

https://www.ampliflow.com

No auth detected

MCP server metadata

Name
WebMCP
Capabilities
declarative

Known tools 2

book-demo

Book an AmpliFlow demo. Requires email and privacy policy acceptance; company and message are optional. The user reviews and submits manually.

Potential side effects
newsletter

Subscribe to the AmpliFlow newsletter with an email. Submits automatically.

Potential side effects

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://www.ampliflow.com"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "webmcp": {
      "type": "http",
      "url": "https://www.ampliflow.com"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: webmcp
Remote MCP URL: https://www.ampliflow.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://www.ampliflow.com"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "webmcp": {
      "type": "http",
      "url": "https://www.ampliflow.com"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "webmcp",
  "transport": "streamable-http",
  "url": "https://www.ampliflow.com"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for ampliflow.com was fetched 2026-10-03T06:35:07.647Z.

Trust status Trusted

ampliflow.com is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.