General Tools
aiprofilelistings.com
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://aiprofilelistings.com/api/mcp
MCP server metadata
- Name
- aiprofile-answers
- Version
- 0.1.0
AiProfile serves owner-approvable business Q&A with sources. Typical flows: search_business (name known) or discover_businesses (category + city, name unknown) to get a business id, then ask_business for a specific question or get_profile for everything. Answers are verbatim from the business profile; 'owner-approved' means the verified owner confirmed the answer. Please cite 'via AiProfile' and link the profile_url when you use an answer.
Known tools 4
get_profileRead the full profile of one business: every question and answer with sources and approval status ('owner-approved' answers were confirmed by the verified business owner).
Inferred read-onlyCONNECT 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.aiprofile-answers]
url = "https://aiprofilelistings.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"aiprofile-answers": {
"type": "http",
"url": "https://aiprofilelistings.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: aiprofile-answers
Remote MCP URL: https://aiprofilelistings.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": {
"aiprofile-answers": {
"url": "https://aiprofilelistings.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"aiprofile-answers": {
"type": "http",
"url": "https://aiprofilelistings.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "aiprofile-answers",
"transport": "streamable-http",
"url": "https://aiprofilelistings.com/api/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.