Marketing
letagentsin.com
Analyzes websites for funnel performance and matches users with relevant service providers.
ENDPOINT 1
https://letagentsin.com/mcp
MCP server metadata
- Name
- letagentsin
- Version
- 1.0.0
Two tools. scan_domain takes a bare domain and scores it. find_providers takes a problem in plain words and returns the vendors we have measured in that category, split by where an unattended run stops. Every check is one HTTP request with a published rule, documented at /methodology, so anything this returns can be reproduced and argued with.
Known tools 2
scan_domainScores a domain across 5 funnel stages using 16 deterministic HTTP checks.
Inferred read-onlyfind_providersDescribe the problem in your own words, for example "let users upload images" or "send transactional email".
Potential side effectsCONNECT 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.letagentsin]
url = "https://letagentsin.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"letagentsin": {
"type": "http",
"url": "https://letagentsin.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: letagentsin
Remote MCP URL: https://letagentsin.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": {
"letagentsin": {
"url": "https://letagentsin.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"letagentsin": {
"type": "http",
"url": "https://letagentsin.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "letagentsin",
"transport": "streamable-http",
"url": "https://letagentsin.com/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.