Marketing
askline.app
An MCP server that finds and scores social media posts with buying intent, then stores and drafts replies for sales lead generation.
ENDPOINT 1
https://askline.app/mcp
MCP server metadata
- Name
- askline
- Version
- 1.0.0
Askline reads X for people expressing buying intent. demand_index and score_post work without an account. search_buyers and list_leads need an API key: create one at https://askline.app/app under Settings, then send it as an Authorization Bearer header.
Known tools 4
demand_indexReal, dated posts from people publicly asking to buy software, by category.
Inferred read-onlyscore_postScore a single post 0-100 for buying intent and explain the reasoning: is this person asking for a recommendation, leaving a tool, complaining, comparing, naming a budget?
Potential side effectssearch_buyersSearch X for people expressing buying intent for what you sell, score them, and draft a reply for each.
Inferred read-onlylist_leadsRead contacts already found, newest first, with their score, the original post and the drafted reply.
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.askline]
url = "https://askline.app/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"askline": {
"type": "http",
"url": "https://askline.app/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: askline
Remote MCP URL: https://askline.app/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": {
"askline": {
"url": "https://askline.app/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"askline": {
"type": "http",
"url": "https://askline.app/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "askline",
"transport": "streamable-http",
"url": "https://askline.app/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.