General Tools
saqibali.me
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://saqibali.me/mcp
MCP server metadata
- Name
- saqib-ali-portfolio
- Version
- 1.0.0
Use these read-only tools to find public professional evidence, projects, articles, skills, and expertise. No authentication is required.
Known tools 4
get_profileReturn Saqib Ali's public professional profile, contact routes, and evidence boundaries.
Inferred read-onlysearch_portfolioSearch public project case studies, technical articles, and expertise pages.
Inferred read-onlylist_projectsList public project case studies, optionally filtered by a category or technology.
Inferred read-onlylist_articlesList public technical articles, optionally filtered by a category, tag, or keyword.
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.saqib-ali-portfolio]
url = "https://saqibali.me/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"saqib-ali-portfolio": {
"type": "http",
"url": "https://saqibali.me/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: saqib-ali-portfolio
Remote MCP URL: https://saqibali.me/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": {
"saqib-ali-portfolio": {
"url": "https://saqibali.me/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"saqib-ali-portfolio": {
"type": "http",
"url": "https://saqibali.me/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "saqib-ali-portfolio",
"transport": "streamable-http",
"url": "https://saqibali.me/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.