Productivity
jobspiq.in
An MCP server that enables searching verified tech jobs, retrieving job details, listing engineering role hubs, and fetching platform statistics.
ENDPOINT 1
https://jobspiq.in/api/v1/mcp
MCP server metadata
- Name
- jobspiq-mcp
- Version
- 1.0.0
Known tools 4
search_jobsSearch verified tech jobs across India and remote teams with skill and location filters.
Inferred read-onlyget_job_detailsGet detailed job specification, salary range, tech stack, and verified application link for a specific job ID.
Inferred read-onlylist_role_hubsList curated engineering disciplines (Backend, Frontend, DevOps, ML, etc.) with core skill taxonomies.
Inferred read-onlyget_platform_statsRetrieve current live platform statistics (active verified jobs, tracked companies, supported roles).
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.jobspiq-mcp]
url = "https://jobspiq.in/api/v1/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"jobspiq-mcp": {
"type": "http",
"url": "https://jobspiq.in/api/v1/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: jobspiq-mcp
Remote MCP URL: https://jobspiq.in/api/v1/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": {
"jobspiq-mcp": {
"url": "https://jobspiq.in/api/v1/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"jobspiq-mcp": {
"type": "http",
"url": "https://jobspiq.in/api/v1/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "jobspiq-mcp",
"transport": "streamable-http",
"url": "https://jobspiq.in/api/v1/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.