INDIVIDUAL MCP TOOL
get_post_brief
Everything an AI needs to draft social posts that move AI visibility, assembled from this week's measured data: fresh third-party mentions to anchor on, the exact buyer questions the engines answer without naming the business (and who they name instead), the domains the engines actually read, and the entity rules that make a post retrievable.
LIVE ENDPOINT
https://areyoufoundbyai.com/mcp/demo
Connect to this endpoint to inspect the live schema for get_post_brief and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Potential side effects detected · medium confidence · heuristic, not a guarantee.
- A tool name or description contains a write-action term.
Parent server
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.found-by-ai-monitor]
url = "https://areyoufoundbyai.com/mcp/demo"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"found-by-ai-monitor": {
"type": "http",
"url": "https://areyoufoundbyai.com/mcp/demo"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: found-by-ai-monitor
Remote MCP URL: https://areyoufoundbyai.com/mcp/demo
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": {
"found-by-ai-monitor": {
"url": "https://areyoufoundbyai.com/mcp/demo"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"found-by-ai-monitor": {
"type": "http",
"url": "https://areyoufoundbyai.com/mcp/demo"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "found-by-ai-monitor",
"transport": "streamable-http",
"url": "https://areyoufoundbyai.com/mcp/demo"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
get_visibility— The latest AI Visibility and AI Readiness scores (each /100) for areyoufoundbyai.get_question_trajectories— Every tracked buyer question with its measured history: how many of the 7 engines named the business on each measured day.get_personas— The 2-4 buyer personas inferred from this business's measured questions, the way AI models would describe each buyer type, with the exact tracked questions each persona asks.get_mentions— New pages on the web that mention the business, from the daily sweep.get_rivals— The competitor names the answer engines actually gave in the latest scan when they did not name this business.get_cited_queries— Reverse lookup over every measurement we have already run: give a competitor's brand name or domain and get the buyer questions where the answer engines named them, which engines, how often, when they were last seen, and who else was named on those questions.get_schema_evidence— Initial HTML versus rendered JSON-LD evidence, with read dates, incomplete states, excerpts and limitations.get_regional_visibility— Saved areas, buyer questions and engine naming observations, retained samples and read coverage.