io.github.CCSTT-dev/callable
REMOTE · GETCALLABLE.DEV
API for AI agents to delegate tasks to real humans.
Available components
Last scanned (23 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 644 tokens (~214/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 20 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 0
- Stability: pass → 0.90 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 21 Aug 26 0
- Authorization: unverified → partial ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.87 ▲ functional
- 18 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Authorization: partial → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Stability: 0.73 → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://getcallable.dev/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=getcallable.dev | CN=WE1,O=Google Trust Services,C=US | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ff3325a78f9ff88e135d3f9398eaa203 |
| SANs: getcallable.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of getcallable.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| getcallable.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://getcallable.dev/api/mcp | Verified | 200 | |
| http (plaintext) | http://getcallable.dev/api/mcp | HTTPS enforced | 301 | https://getcallable.dev/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_task_status ~85
Poll the status and retrieve the result of a previously submitted task. Returns the current status (pending, in_progress, pending_review, completed, disputed), the result payload, and any output URLs (video, screenshot). Use this in a polling loop after submit_task if no callback_url was provided.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | The task ID returned when the task was submitted |
| Name | Type | Req | Description |
|---|---|---|---|
| completed_at | string | – | ISO timestamp of completion |
| operator | string | – | Name of the operator who completed the task |
| output_url | string | – | URL to download output file (video, screenshot, etc.) |
| result | object | – | Task result payload when completed |
| status | string | yes | – |
| task_id | string | yes | – |
No examples provided.
review_task ~179
Optional. Approve or dispute a task that is in `pending_review` status. Use this after get_task_status reports the operator has completed the work. Approving releases the operator payout. Disputing requires a reason and a description of what is needed for acceptance; the operator is then allowed to resubmit. If you never call review_task, tasks are auto-approved after the review window expires.
| Name | Type | Req | Description |
|---|---|---|---|
| decision | string | yes | approve to accept the result and release payment; dispute to reject it and request a resubmission. |
| dispute_reason | string | – | Required when decision = 'dispute'. What went wrong with the submission. |
| task_id | string | yes | The task ID returned by submit_task. |
| what_is_needed | string | – | Required when decision = 'dispute'. What the operator must do for the submission to be accepted. |
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | yes | – |
| success | boolean | yes | – |
No examples provided.
submit_task ~332
Submit an account verification task to a real human operator. Use this when your agent is blocked on something only a real person can complete — a KYC check, a platform sign-in or 2FA prompt, a CAPTCHA, an identity confirmation, or any verification step that requires a human. The task is charged automatically via Stripe ($39). A vetted operator claims it, performs the verification on real hardware, and returns the result (with optional screenshot) to your callback_url or via get_task_status. Typical completion: 30 minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| callback_url | string | – | Webhook URL to receive a POST request with the task result when completed. Recommended for async agent workflows. If omitted, poll get_task_status instead. |
| deadline_minutes | integer | yes | Time in minutes the operator has to complete the verification after claiming it. Minimum 20. Recommended: 30. |
| instructions | object | yes | Structured input for account_verification. Required fields: platform (e.g. 'gmail', 'stripe'), url (where to perform the verification), credentials (login info or how to obtain the code), what_to_ver… |
| payment_credential | object | – | Stripe Link Agent Wallet Single-use Payment Token (SPT) for fully autonomous agent payments with no human intervention required. Omit if the developer account has a saved card on file. |
| task_type | string | yes | account_verification — a real human verifies an account, KYC check, sign-in, or CAPTCHA on real hardware and returns structured proof ($39). |
| Name | Type | Req | Description |
|---|---|---|---|
| estimated_completion | string | – | Estimated completion time based on deadline_minutes |
| message | string | – | Confirmation or error message |
| status | string | yes | Current task status |
| task_id | string | yes | Unique identifier for the submitted task |
No examples provided.
How do I install the io.github.CCSTT-dev/callable MCP server?
io.github.CCSTT-dev/callable is a hosted endpoint at https://getcallable.dev/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · getcallable.dev
claude mcp add --transport http ccstt-dev-callable 'https://getcallable.dev/api/mcp'
What is the io.github.CCSTT-dev/callable MCP server?
io.github.CCSTT-dev/callable is an MCP server listed in the public MCP registry as io.github.CCSTT-dev/callable. API for AI agents to delegate tasks to real humans. This page covers its hosted endpoint (https://getcallable.dev/api/mcp).
Is the io.github.CCSTT-dev/callable MCP server safe to use?
io.github.CCSTT-dev/callable scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.CCSTT-dev/callable MCP server expose?
io.github.CCSTT-dev/callable exposes 3 tools: submit_task, get_task_status, review_task. Their descriptions and schemas cost roughly 596 tokens of context every time the server is loaded.
Does the io.github.CCSTT-dev/callable MCP server require authentication?
No. We connected to io.github.CCSTT-dev/callable without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.CCSTT-dev/callable MCP server still maintained?
io.github.CCSTT-dev/callable is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.