API Tools
api.services
Provides tools to search and retrieve details, pricing, and vertical information about callable services in an API service catalog.
ENDPOINT 1
https://api.services/mcp
MCP server metadata
- Name
- api-services
- Version
- 0.1.0
Known tools 5
get_serviceOne catalog row in full: door URL, copy-pasteable curl, MCP tool name, gate, posted price, stamp, and the cure when the act is reserved.
Inferred read-onlyget_pricingThe aggregated posted rate card: live rows only, every price flat and posted by the owning door.
Inferred read-onlyget_verticalsThe family map: api.* demand and gigs.* supply pairs, every door stamped live | specimen | roadmap.
Inferred read-onlyget_stackThe six-term equation and its substrate mapping, each term carrying its rungs of the delivery ladder.
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.api-services]
url = "https://api.services/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"api-services": {
"type": "http",
"url": "https://api.services/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: api-services
Remote MCP URL: https://api.services/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": {
"api-services": {
"url": "https://api.services/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"api-services": {
"type": "http",
"url": "https://api.services/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "api-services",
"transport": "streamable-http",
"url": "https://api.services/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for api.services was fetched 2026-09-25T01:13:56.542Z.
api.services is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.