Rinkel MCP by usefulapi
REMOTE · RINKEL.USEFULAPI.IO
Read Rinkel calls, voicemails, contacts and numbers; add call notes, edit contacts, block numbers.
Available components
Last scanned (13 minutes ago)
Scores higher than 47% of remote servers
Reachable. Last reached 25 Oct 2026.
Category Communication
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3532 tokens (~130/item across 27 items; 27 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 Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 28 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; 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.
- 25 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.0.3 functional
- 24 Oct 26 62
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 25 Oct 2026 · Probed https://rinkel.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| 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 rinkel.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://rinkel.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://rinkel.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://rinkel.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://rinkel.usefulapi.io/mcp |
| Authorisation server | https://rinkel.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rinkel.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/rinkel/ |
| http (plaintext) | http://rinkel.usefulapi.io/mcp | Inconclusive | 302 | http://rinkel.usefulapi.io/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 →
rinkel_add_call_note Add a call note ~105
WRITE: add a note to a call record (visible to everyone in the account who sees the call). The id is the call record's `id`; if Rinkel answers 404, retry with the record's `callId`. Rinkel API: PUT /call-detail-records/{callId}/note.
| Name | Type | Req | Description |
|---|---|---|---|
| call_record_id | string | yes | The call record id (`id` of rinkel_list_calls). |
| content | string | yes | The note text. |
No output schema declared.
No examples provided.
rinkel_block_number Block a number ~130
WRITE: block a number from calling ANY of the account's numbers. Accepts an E.164 number, 'anonymous', or a prefix wildcard such as '+31*' (a wildcard must end the value and include a country code; a broad wildcard blocks every caller from that country). Undo with rinkel_unblock_number. Rinkel API: POST /privacy/block-number.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | E.164 number (+31612345678), 'anonymous', or a prefix wildcard like '+3161*'. |
| reason | string | – | Why it is blocked (for example Spam). |
No output schema declared.
No examples provided.
rinkel_count_new_voicemails Count new voicemails ~37
Number of voicemails that have not been played yet. Rinkel API: GET /voicemails/new-count.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rinkel_create_contact Create a contact ~125
WRITE: create a contact. It is shared with everyone in the Rinkel account (all users see it and calls from its numbers show its name). Rinkel API: POST /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | – | – |
| default_outbound_number_id | string | – | Id of the Rinkel number to call this contact from (rinkel_list_numbers). |
| string | – | – | |
| first_name | string | – | – |
| last_name | string | – | – |
| numbers | array | yes | Phone numbers of the contact (Rinkel requires at least one). |
No output schema declared.
No examples provided.
rinkel_delete_call_note Delete a call note ~104
WRITE, irreversible: delete one note from a call record. Needs confirm=true after the user approved it. Rinkel API: DELETE /call-detail-records/{callId}/note/{noteId}.
| Name | Type | Req | Description |
|---|---|---|---|
| call_record_id | string | yes | The call record id (`id`). |
| confirm | boolean | – | Must be true, set only after the user explicitly approved this exact action. |
| note_id | string | yes | The note id (`notes[].id`). |
No output schema declared.
No examples provided.
rinkel_delete_contact Delete a contact ~82
WRITE, irreversible: delete a contact for the whole account. Needs confirm=true after the user approved it. The Rinkel system contact cannot be deleted. Rinkel API: DELETE /contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true, set only after the user explicitly approved this exact action. |
| contact_id | string | yes | The contact id. |
No output schema declared.
No examples provided.
rinkel_find_contact_by_number Find a contact by phone number ~77
Find the contact that owns a phone number (E.164 such as +31612345678 works best). 404 when there is none. Rinkel API: GET /contacts/find-by-number/{number}.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_number | string | yes | The phone number, preferably in E.164 format (+31612345678). |
No output schema declared.
No examples provided.
rinkel_get_call Get a call ~82
Get one call detail record by its Rinkel id (the `id` field of rinkel_list_calls): numbers, users, status, duration, notes, voicemail and call-recording ids, AI insights. Rinkel API: GET /call-detail-records/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| call_record_id | string | yes | The call detail record id (`id`). |
No output schema declared.
No examples provided.
rinkel_get_call_by_network_id Get a call by network call id ~88
Get one call detail record by its network `callId` (the id Rinkel sends in webhook events), optionally with insights and notes. Rinkel API: GET /call-detail-records/by-call-id/{callId}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_details | boolean | – | Include insights and notes. |
| network_call_id | string | yes | The network call id (`callId` field). |
No output schema declared.
No examples provided.
rinkel_get_call_recording_url Get a call recording URL ~98
Get a temporary URL (valid 3 hours) to stream or download a call recording. The id is `callRecording.id` of a call record. Append `download` as a query parameter to the URL to download instead of stream. Rinkel API: GET /call-recordings/{id}/stream.
| Name | Type | Req | Description |
|---|---|---|---|
| call_recording_id | string | yes | The call recording id (`callRecording.id` of a call record). |
No output schema declared.
No examples provided.
rinkel_get_call_transcription Get a call transcription ~86
Get the raw transcription of a call by its network `callId` (needs Rinkel AI insights on the account; 404 when the call has none). Rinkel API: GET /call-detail-records/by-call-id/{callId}/transcription.
| Name | Type | Req | Description |
|---|---|---|---|
| network_call_id | string | yes | The network call id (`callId` field of the call record). |
No output schema declared.
No examples provided.
rinkel_get_contact Get a contact ~37
Get one contact by id. Rinkel API: GET /contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The contact id. |
No output schema declared.
No examples provided.
rinkel_get_number Get a phone number ~70
Get one Rinkel number with its full dial plan: greeting, business hours schedule, call forwarding targets and ring logic, voice menu, call recording and caller-id settings. Rinkel API: GET /numbers/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| number_id | string | yes | The number id (rinkel_list_numbers). |
No output schema declared.
No examples provided.
rinkel_get_user Get a user ~65
Get one user by id, including preferences, notification settings, schedule and `deviceId`. Rinkel API: GET /users/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_avatar | boolean | – | Include avatar URLs. |
| user_id | string | yes | The user id (rinkel_list_users). |
No output schema declared.
No examples provided.
rinkel_get_voicemail_url Get a voicemail URL ~74
Get a temporary URL (valid 3 hours) to stream or download a voicemail. The id is `voicemail.id` of a call or voicemail record. Rinkel API: GET /voicemails/{id}/stream.
| Name | Type | Req | Description |
|---|---|---|---|
| voicemail_id | string | yes | The voicemail id (`voicemail.id`). |
No output schema declared.
No examples provided.
rinkel_list_calls List calls ~554
List call detail records (inbound and outbound calls) with date, direction, status (ANSWERED, MISSED, VOICEMAIL, ANSWERING_SERVICE), duration, external and internal number, the users involved, notes, and (when the account has Rinkel AI insights) the AI summary and sentiment. Use for 'who called today', 'which calls did we miss this week', 'calls longer than 5 minutes'. Newest first by default. Rinkel API: GET /call-detail-records.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | Only calls with this contact (id). |
| contact_lookup | boolean | – | Include the matching contact in each record. |
| date_preset | string | – | A relative period. It overrides start_date and end_date. |
| directions | array | – | Only these directions. |
| duration_preset | array | – | Duration buckets in minutes ('30-0' = 30 minutes or more). Overrides min/max duration. |
| end_date | string | – | Only calls on or before this date (yyyy-mm-dd = end of that day UTC, or an ISO date-time with timezone). |
| external_number | string | – | Only calls with this external (caller or callee) number. |
| filter | string | – | Free-text search over calls. |
| has_insights | boolean | – | Only calls that have AI insights. |
| has_notes | boolean | – | Only calls that have (true) or lack (false) notes. |
| has_transcription | boolean | – | Only calls that have a transcription. |
| include_details | boolean | – | Include insights and notes in each record. |
| internal_numbers | array | – | Only calls on these internal (Rinkel) numbers, as listed by rinkel_list_numbers. |
| is_anonymous | boolean | – | Only calls from a hidden number (true) or not (false). |
| max_duration_seconds | integer | – | Maximum duration in seconds (ignored with duration_preset). |
| min_duration_seconds | integer | – | Minimum duration in seconds (ignored with duration_preset). |
| page | integer | – | Page number (default 1). |
| per_page | integer | – | Items per page (default 10, max 50). |
| sentiments | array | – | Only calls with this AI-insights sentiment. |
| sort | string | – | Sort field (default date). |
| sort_order | string | – | Sort order (default DESC). |
| start_date | string | – | Only calls on or after this date (yyyy-mm-dd, or an ISO date-time with timezone). Sent as a Unix timestamp. |
| statuses | array | – | Only these call outcomes. |
| user_ids | array | – | Only calls handled by these user ids (rinkel_list_users). |
No output schema declared.
No examples provided.
rinkel_list_contacts List contacts ~109
List the contacts shared with everyone in the account (plus the Rinkel system contact, tag 'system'): names, company, phone numbers, email. Rinkel API: GET /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Search by name, company or number. |
| letter | string | – | Only contacts whose name starts with this letter. |
| page | integer | – | Page number (default 1). |
| per_page | integer | – | Items per page (default 10, max 50). |
No output schema declared.
No examples provided.
rinkel_list_numbers List phone numbers ~55
List the account's Rinkel phone numbers: id, label, number, status (ACTIVE, SUSPENDED, PENDING_PORTING_IN ...), activation date and the users assigned. Rinkel API: GET /numbers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rinkel_list_recordings List greeting recordings ~112
List the uploaded audio recordings used in the dial plan (greetings, announcements, voice-over scripts): name, description, duration and where each is used. Not call recordings. Rinkel API: GET /recordings.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1). |
| per_page | integer | – | Items per page (default 10, max 999). |
| sort | string | – | Sort field (default date). |
| sort_order | string | – | Sort order (default DESC). |
No output schema declared.
No examples provided.
rinkel_list_users List users ~77
List the account's users: name, email, phone number, role (ADMIN, USER, ANSWERINGSERVICE), availability schedule and status, and `fixed`/device info (`deviceId` is needed to start a call). Rinkel API: GET /users.
| Name | Type | Req | Description |
|---|---|---|---|
| include_avatars | boolean | – | Include avatar URLs. |
No output schema declared.
No examples provided.
rinkel_list_voicemails List voicemails ~359
List voicemail messages (call records with status VOICEMAIL): caller, date, duration, whether new, and the voicemail id. Newest first. With is_new=true Rinkel ignores every other filter and returns only unplayed voicemails. Rinkel API: GET /voicemails.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_lookup | boolean | – | Include the matching contact in each record. |
| date_preset | string | – | A relative period (overrides start_date and end_date). |
| end_date | string | – | Only calls on or before this date (yyyy-mm-dd = end of that day UTC, or an ISO date-time with timezone). |
| external_number | string | – | Only calls with this external (caller or callee) number. |
| filter | string | – | Free-text search over calls. |
| has_notes | boolean | – | Only calls that have (true) or lack (false) notes. |
| internal_numbers | array | – | Only calls on these internal (Rinkel) numbers, as listed by rinkel_list_numbers. |
| is_anonymous | boolean | – | Only calls from a hidden number (true) or not (false). |
| is_new | boolean | – | Only unplayed voicemails (true). All other filters are ignored then. |
| page | integer | – | Page number (default 1). |
| per_page | integer | – | Items per page (default 10, max 50). |
| sort_order | string | – | Sort order by date (default DESC). |
| start_date | string | – | Only calls on or after this date (yyyy-mm-dd, or an ISO date-time with timezone). Sent as a Unix timestamp. |
| topics | array | – | Only voicemails with these AI topic ids. |
No output schema declared.
No examples provided.
rinkel_list_webhooks List webhooks ~54
List the webhook subscriptions (events incomingCall, outgoingCall, callStart, callEnd, callInsights) with URL and active flag. Webhooks need the Expert plan. Rinkel API: GET /webhooks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rinkel_start_call Start an outgoing call ~227
WRITE, COSTS CALL MINUTES: starts a real phone call. Rinkel rings the given user device first and, once it is answered, dials `to` using the chosen Rinkel number as caller id, so call charges apply to the account and the person called sees the number. Needs confirm=true, set only after the user explicitly asked to place this call. Get device_id from rinkel_list_users (`fixed`/device info or `deviceId`) and number_id from rinkel_list_numbers. Rinkel API: POST /dial.
| Name | Type | Req | Description |
|---|---|---|---|
| anonymous | boolean | – | Hide the caller id (default false). |
| confirm | boolean | – | Must be true, set only after the user explicitly approved this exact action. |
| device_id | string | yes | The id of the user device that starts the call (`deviceId` of a user). |
| number_id | string | yes | The id of the Rinkel number used as caller id (rinkel_list_numbers). |
| to | string | yes | The number to call, in E.164 format (+31612345678). |
No output schema declared.
No examples provided.
rinkel_unblock_number Unblock a number ~62
WRITE: remove a number (or the same wildcard pattern that was blocked) from the block list so it can call again. Rinkel API: DELETE /privacy/unblock-number.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | The blocked entry exactly as it was blocked. |
No output schema declared.
No examples provided.
rinkel_update_call_note Update a call note ~102
WRITE: replace the text of an existing note on a call record (the note id is in `notes[].id` of the call record). Rinkel API: PATCH /call-detail-records/{callId}/note/{noteId}.
| Name | Type | Req | Description |
|---|---|---|---|
| call_record_id | string | yes | The call record id (`id`). |
| content | string | yes | The new note text. |
| note_id | string | yes | The note id (`notes[].id`). |
No output schema declared.
No examples provided.
rinkel_update_contact Update a contact ~191
WRITE: update a contact (PUT semantics). `numbers` is required and REPLACES all stored numbers, and an omitted default_outbound_number_id CLEARS it; omitted names, company and email keep their stored value. Read the contact first (rinkel_get_contact) and resend what must stay. The system contact cannot be changed. Rinkel API: PUT /contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | – | – |
| contact_id | string | yes | The contact id. |
| default_outbound_number_id | string | – | Resend the current value to keep it; omit to clear it. |
| string | – | – | |
| first_name | string | – | – |
| last_name | string | – | – |
| numbers | array | yes | The COMPLETE list of numbers (replaces the stored ones; Rinkel requires at least one, so read the contact first and resend the ones to keep). |
No output schema declared.
No examples provided.
rinkel_validate_phone_number Validate a phone number ~96
Check a phone number for a country and return its normalised form. With check_inventory=true Rinkel also checks whether the number is available to order. Rinkel API: GET /misc/validate-phone-number.
| Name | Type | Req | Description |
|---|---|---|---|
| check_inventory | boolean | – | Also check availability to order. |
| country_iso_code | string | yes | Country code such as NL or BE. |
| number | string | yes | The number without the country calling code. |
No output schema declared.
No examples provided.
How do I install the Rinkel MCP by usefulapi server?
Rinkel MCP by usefulapi is a hosted endpoint at https://rinkel.usefulapi.io/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 · rinkel.usefulapi.io
claude mcp add --transport http io-usefulapi-rinkel 'https://rinkel.usefulapi.io/mcp'
What is the Rinkel MCP by usefulapi server?
Rinkel MCP by usefulapi is listed in the public MCP registry as io.usefulapi/rinkel. Read Rinkel calls, voicemails, contacts and numbers; add call notes, edit contacts, block numbers. This page covers its hosted endpoint (https://rinkel.usefulapi.io/mcp).
Is the Rinkel MCP by usefulapi server safe to use?
Rinkel MCP by usefulapi scores 63 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 Rinkel MCP by usefulapi server expose?
Rinkel MCP by usefulapi exposes 27 tools: rinkel_list_calls, rinkel_get_call, rinkel_get_call_by_network_id, rinkel_get_call_transcription, rinkel_get_call_recording_url, and 22 more. Their descriptions and schemas cost roughly 3,258 tokens of context every time the server is loaded.
Does the Rinkel MCP by usefulapi server require authentication?
Yes. Rinkel MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Rinkel MCP by usefulapi server still maintained?
Rinkel MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.