Other · Remote MCP server
ClutchCall Platform
Tenant-scoped control plane over the ClutchCall platform's full API surface.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.clutchcall/portal- Version
- 0.1.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-19
- Updated
- 2026-08-19
- Publisher
- dev.clutchcall
- Namespace
- Namespace verified by the MCP Registry via the domain clutchcall.dev · how
- Website
- docs.clutchcall.dev/concepts/coding-agents
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://portal.clutchcall.dev/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect ClutchCall Platform
ClutchCall Platform is a remote MCP server: there is nothing to install. Its endpoint is https://portal.clutchcall.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, docs.clutchcall.dev, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More other servers
| Server | Runs |
|---|---|
| Clpi Clp MCPManage simple context workflows with quick init and add actions. Access the 'Hello, World' origin… | Remote · HTTPLive check: ✗ no handshake |
| ClusterHackRun hackathons end to end: events, teams, submissions, judging and winners. | Remote · HTTPLive check: ✓ handshake |
| Clutch Agency ApiClutch.co B2B agency directory, profiles, and reviews as JSON, via an Apify Actor, hosted MCP. | Remote · HTTPLive check: sign-in required |
| Clutch.coTrusted B2B service providers with verified client reviews. | Remote · HTTPLive check: ✓ handshake |
| ClyptAI-native link intelligence - shorten, track, and manage links from any AI agent. | Local · stdio |
| CMDOP Machine CareRead-only health and storage diagnostics for an enrolled CMDOP machine fleet. | Local · stdio |
| cmdxrayOffline MCP server: explains shell commands token-by-token and flags destructive ones for AI agents. | Local · stdio |
| Cmp InspectorCompose Multiplatform UI as structured JSON for agents: trees, tokens, previews, diffs. No pixels. | Local · stdio |