Call Me
REMOTE · SERDAROZTETIK.COM · SCANNED AUG 8
Your AI rings your iPhone, speaks its question, and gets your spoken answer back as text.
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 709 tokens (~141/item across 5 items; 5 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · serdaroztetik.com
claude mcp add --transport http com-serdaroztetik-call-me https://serdaroztetik.com/aiphone/mcp
[mcp_servers.com-serdaroztetik-call-me] url = "https://serdaroztetik.com/aiphone/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-serdaroztetik-call-me": {
"type": "remote",
"url": "https://serdaroztetik.com/aiphone/mcp",
"enabled": true
}
}
} openclaw mcp add com-serdaroztetik-call-me --url https://serdaroztetik.com/aiphone/mcp --transport streamable-http
mcp_servers:
com-serdaroztetik-call-me:
url: "https://serdaroztetik.com/aiphone/mcp" {
"mcpServers": {
"com-serdaroztetik-call-me": {
"type": "http",
"url": "https://serdaroztetik.com/aiphone/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 8 Aug 26 58
First indexed and scored.
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 8 Aug 2026 · Probed https://serdaroztetik.com/aiphone/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=serdaroztetik.com | CN=YE1,O=Let's Encrypt,C=US | 4 Jul 2026 | 2 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5a1e6ff0f938f520e4dec71c9b9228015f9 |
| SANs: serdaroztetik.com, www.serdaroztetik.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of serdaroztetik.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| serdaroztetik.com. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://serdaroztetik.com/aiphone/mcp | Verified | 200 | |
| http (plaintext) | http://serdaroztetik.com/aiphone/mcp | HTTPS enforced | 301 | https://serdaroztetik.com/aiphone/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.
call ~126
Ring the human's iPhone, speak the question aloud, and return what they say. Waits up to ~30s; if the result comes back status "ringing", follow up with poll_result. `to` is their 10-digit Call Me number (from the Call Me iOS app — not a real phone number). Pass a previous session_token to stay in the same thread on their phone.
| Name | Type | Req | Description |
|---|---|---|---|
| from_label | string | – | – |
| question | string | yes | – |
| session_token | – | – | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
poll_result ~70
Check on a call that was still ringing. Waits up to ~25s for it to settle; returns the final status and transcript once the human answers, declines, or the ring times out ("missed").
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | integer | yes | – |
| session_token | string | yes | – |
No output schema declared.
No examples provided.
set_thread_title ~60
Name this session's conversation thread on the human's phone (e.g. the project or task you are working on). Shown as the thread title in the app.
| Name | Type | Req | Description |
|---|---|---|---|
| session_token | string | yes | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
text ~79
Send a one-way text to the human's phone (push notification, no ring). `to` is their 10-digit Call Me number. Pass a previous session_token to stay in the same thread.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| from_label | string | – | – |
| session_token | – | – | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
wait_for_reply ~106
Wait for the human to send something back to this session — texts and voicemail transcripts arrive here. Long-polls up to wait_s (max 30s); returns {events, cursor}. Pass the returned cursor next time to only see new events. An empty events list just means nothing yet — poll again if you are still waiting.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | integer | – | – |
| session_token | string | yes | – |
| wait_s | integer | – | – |
No output schema declared.
No examples provided.