Placetel MCP by usefulapi
REMOTE · PLACETEL.USEFULAPI.IO
Read Placetel calls, recordings, numbers and routing; edit contacts, start calls, send SMS.
Available components
Last scanned (3 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
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 Usability81
- 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 3795 tokens (~135/item across 28 items; 28 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 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 29 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
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.
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 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://placetel.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 placetel.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://placetel.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://placetel.usefulapi.io/.well-known/oauth-protected-resource/mcp" Protected resource metadata
| Document | https://placetel.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://placetel.usefulapi.io/mcp |
| Authorisation server | https://placetel.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://placetel.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/placetel/ |
| http (plaintext) | http://placetel.usefulapi.io/mcp | Inconclusive | 302 | http://placetel.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 →
placetel_activate_number_profile Activate number profile ~90
WRITE: switch the active routing profile of a phone number (for example to Holiday or Night). This changes LIVE call handling for that number immediately: callers are routed differently. Find ids with placetel_list_number_profiles. PUT /numbers/{number_id}/profiles.
| Name | Type | Req | Description |
|---|---|---|---|
| number_id | integer | yes | Placetel number id. |
| profile_id | integer | yes | Id of the profile to activate. |
No output schema declared.
No examples provided.
placetel_create_contact Create contact ~224
WRITE: create a contact in the shared Placetel phone book. Give at least a name, company or number. Nothing is sent to the contact. POST /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Private address. |
| address_work | string | – | Work address. |
| blocked | boolean | – | true = calls from this contact are blocked. |
| company | string | – | Company. |
| string | – | Private email address. | |
| email_work | string | – | Work email address. |
| fax | string | – | Private fax number. |
| fax_work | string | – | Work fax number. |
| first_name | string | – | First name. |
| last_name | string | – | Last name. |
| mobile | string | – | Private mobile number. |
| mobile_work | string | – | Work mobile number. |
| phone | string | – | Private phone number. |
| phone_work | string | – | Work phone number. |
| speeddial | string | – | Speed-dial code. |
| tags | array | – | Tags (replaces the existing tags on update; [] clears them). |
No output schema declared.
No examples provided.
placetel_get_account Get account ~54
The Placetel account this API key belongs to: user id, name, email, company, platform (e.g. PROFI), primary SIP user id and the numbers the key may use. GET /me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
placetel_get_call Get call ~56
One incoming call by id: caller, called number, type, duration, contact, voicemail file URL. GET /calls/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | integer | yes | Placetel call id (from placetel_list_calls). |
No output schema declared.
No examples provided.
placetel_get_contact Get contact ~44
One contact by id with all its fields. GET /contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | Placetel contact id (from placetel_list_contacts). |
No output schema declared.
No examples provided.
placetel_get_fax Get fax ~59
One fax by id: numbers, status, status info, pages, retries, report and file URL. GET /faxes/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| fax_id | integer | yes | Placetel fax id (from placetel_list_faxes). |
No output schema declared.
No examples provided.
placetel_get_number Get phone number ~59
One phone number by id: number, E.164, name, site, carrier, activation state and routing id. GET /numbers/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| number_id | integer | yes | Placetel number id (from placetel_list_numbers). |
No output schema declared.
No examples provided.
placetel_get_routing Get routing ~68
One routing object by its id or by the phone number it answers. GET /routings/{number_or_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| number_or_id | string | yes | A routing id (e.g. 4711) or a phone number (e.g. 022112345678). |
No output schema declared.
No examples provided.
placetel_get_sip_user Get SIP user ~81
One SIP user (extension) by id: sipuid, extension, caller id, type, linked web user, online state and call settings. The SIP password and PINs are never returned. GET /sip_users/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| sip_user_id | integer | yes | Placetel SIP user id (from placetel_list_sip_users). |
No output schema declared.
No examples provided.
placetel_initiate_call Initiate call ~135
WRITE: start a real phone call. Placetel rings the given SIP user's phone first and, once answered, dials the target number. This places an actual call and call charges apply. Do not use without the user's explicit request. POST /calls.
| Name | Type | Req | Description |
|---|---|---|---|
| from_name | string | – | Name shown for the call. |
| sipuid | string | yes | SIP user that is rung first, e.g. 7771234567@fpbx.de (the sipuid from placetel_list_sip_users). |
| target | string | yes | Number to call, e.g. +4922112345678. |
No output schema declared.
No examples provided.
placetel_list_call_center_agents List call center agents ~94
List call-center agents with name, status, extension, priority and last call time. GET /call_center_agents.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). Not every endpoint honours it; keep paging until a page is empty. |
No output schema declared.
No examples provided.
placetel_list_call_center_calls List call center calls ~149
Call-center calls of one day with queue, agent, from/to, answer status, start/end time and time spent in queue. date is required; narrow to queues with queue_ids. GET /call_center_calls.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Day to list, yyyy-mm-dd. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). Not every endpoint honours it; keep paging until a page is empty. |
| queue_ids | array | – | Only these queue ids (see placetel_list_call_center_queues). |
No output schema declared.
No examples provided.
placetel_list_call_center_queues List call center queues ~102
List call-center queues with name, ring time, loops and prompts. Use the ids to filter call-center calls. GET /call_center_queues.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). Not every endpoint honours it; keep paging until a page is empty. |
No output schema declared.
No examples provided.
placetel_list_call_detail_records List call detail records ~123
Call detail records (billing view) for one day: from, to, answering SIP user, length in seconds, cost amount and description. date is required. GET /call_detail_records.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Day to list, yyyy-mm-dd. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). Not every endpoint honours it; keep paging until a page is empty. |
No output schema declared.
No examples provided.
placetel_list_calls List incoming calls ~185
Incoming calls (accepted, missed, blocked, voicemail) on one day, today by default: caller number, called number, duration, matching contact, voicemail file URL and unread flag. For a different day pass date. GET /calls.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Day to list, yyyy-mm-dd (default: today). |
| from_number | string | – | Only calls from this caller number. |
| order | string | – | Sort order by time. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). Not every endpoint honours it; keep paging until a page is empty. |
| to_number | string | – | Only calls to this of your numbers. |
| type | string | – | Call outcome filter. |
No output schema declared.
No examples provided.
placetel_list_contacts List contacts ~316
List the shared phone-book contacts with names, company, phone/mobile/fax numbers, emails, tags and blocked flag. Filter by name, company, email, number or update time. search_number finds a contact by any of its numbers. GET /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| blocked | boolean | – | Only blocked (true) or only non-blocked (false) contacts. |
| company | string | – | Filter by company. |
| string | – | Filter by private email. | |
| email_work | string | – | Filter by work email. |
| first_name | string | – | Filter by first name. |
| last_name | string | – | Filter by last name. |
| mobile | string | – | Filter by private mobile. |
| mobile_work | string | – | Filter by work mobile. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). Not every endpoint honours it; keep paging until a page is empty. |
| phone | string | – | Filter by private phone. |
| phone_work | string | – | Filter by work phone. |
| search_number | string | – | Find the contact that owns this phone number (any of its number fields). |
| speeddial | integer | – | Filter by speed-dial code. |
| updated_since | string | – | Only contacts updated at or after this date/time. |
| updated_until | string | – | Only contacts updated at or before this date/time. |
No output schema declared.
No examples provided.
placetel_list_faxes List faxes ~150
In- and outbound faxes with from/to number, status, pages, duration, type and the file URL. Filter by direction or number. GET /faxes.
| Name | Type | Req | Description |
|---|---|---|---|
| from_number | string | – | Only faxes from this number. |
| order | string | – | Sort order. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). Not every endpoint honours it; keep paging until a page is empty. |
| to_number | string | – | Only faxes to this number. |
| type | string | – | Direction filter. |
No output schema declared.
No examples provided.
placetel_list_groups List groups ~124
List ring groups (ring_all, hunt, monitoring) with members. Filter by name, description or type. GET /groups.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Filter by description. |
| name | string | – | Filter by name. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). Not every endpoint honours it; keep paging until a page is empty. |
| type | string | – | Group type. |
No output schema declared.
No examples provided.
placetel_list_number_profiles List number profiles ~65
The routing profiles of a phone number (for example Standard, Holiday, Night) and which one is active. Needs a Placetel plan with number profiles. GET /numbers/{number_id}/profiles.
| Name | Type | Req | Description |
|---|---|---|---|
| number_id | integer | yes | Placetel number id. |
No output schema declared.
No examples provided.
placetel_list_numbers List phone numbers ~189
List the phone numbers of the account with number, E.164 form, name, description, site, activation state and the routing object id that answers them. GET /numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| activated | boolean | – | Only activated (true) or deactivated (false) numbers (Profi plans). |
| description | string | – | Filter by description. |
| name | string | – | Filter by name. |
| number | string | – | Filter by number. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). Not every endpoint honours it; keep paging until a page is empty. |
| prefix | string | – | Filter by area-code prefix. |
| site_id | integer | – | Only numbers of this site (see placetel_list_sites). |
No output schema declared.
No examples provided.
placetel_list_recordings List call recordings ~170
Call recordings with direction, from, to, duration, time and the file URL. Filter by direction, number or day. GET /recordings.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Only recordings of this day, yyyy-mm-dd. |
| direction | array | – | Directions to include, e.g. ["in","out"]. |
| from | string | – | Only recordings from this number. |
| order | string | – | Sort order by time. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). Not every endpoint honours it; keep paging until a page is empty. |
| to | string | – | Only recordings to this number. |
No output schema declared.
No examples provided.
placetel_list_routing_plans List routing plans ~99
List routing plans (time-based call distribution plans) with name, description, ring duration and object counts. GET /routing_plans.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). Not every endpoint honours it; keep paging until a page is empty. |
No output schema declared.
No examples provided.
placetel_list_routings List routings ~152
List routing objects (what happens to an incoming call: forward, group, routing plan, IVR, queue, voicemail, API) with their settings and time settings. Filter by update time. GET /routings.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). Not every endpoint honours it; keep paging until a page is empty. |
| updated_since | string | – | Only routings updated at or after this date/time. |
| updated_until | string | – | Only routings updated at or before this date/time. |
No output schema declared.
No examples provided.
placetel_list_sip_users List SIP users (extensions) ~159
List SIP users (phone extensions, softphones, fax and trunk lines) with extension number (did), caller id, type, online state and registrations. SIP passwords and PINs are never returned. GET /sip_users.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Filter by description. |
| did | integer | – | Filter by internal extension number. |
| name | string | – | Filter by name. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). Not every endpoint honours it; keep paging until a page is empty. |
| username | string | – | Filter by SIP username. |
No output schema declared.
No examples provided.
placetel_list_sites List sites ~84
List company sites (locations) with address and prefix. GET /sites.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). Not every endpoint honours it; keep paging until a page is empty. |
No output schema declared.
No examples provided.
placetel_list_users List users ~169
List the web users of the account (main account and sub-users) with name, email, login, type, permissions and numbers. Filter by name, email, login or type. GET /users.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Filter by email. | |
| first_name | string | – | Filter by first name. |
| last_name | string | – | Filter by last name. |
| login | string | – | Filter by login. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). Not every endpoint honours it; keep paging until a page is empty. |
| type | string | – | Only the main account or only sub-users. |
No output schema declared.
No examples provided.
placetel_send_sms Send SMS ~91
WRITE: send a real SMS to a phone number from the Placetel account. The recipient receives it immediately and SMS charges apply; it cannot be recalled. Do not use without the user's explicit request and exact text. POST /sms.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The exact message text (sent unchanged). |
| recipient | string | yes | Recipient number, e.g. +4915112345678. |
No output schema declared.
No examples provided.
placetel_update_contact Update contact ~244
WRITE: update the given fields of a contact (omitted fields stay; an empty string clears a text field). tags replaces the whole tag list; blocked=true blocks the caller. PUT /contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Private address. |
| address_work | string | – | Work address. |
| blocked | boolean | – | true = calls from this contact are blocked. |
| company | string | – | Company. |
| contact_id | integer | yes | Placetel contact id. |
| string | – | Private email address. | |
| email_work | string | – | Work email address. |
| fax | string | – | Private fax number. |
| fax_work | string | – | Work fax number. |
| first_name | string | – | First name. |
| last_name | string | – | Last name. |
| mobile | string | – | Private mobile number. |
| mobile_work | string | – | Work mobile number. |
| phone | string | – | Private phone number. |
| phone_work | string | – | Work phone number. |
| speeddial | string | – | Speed-dial code. |
| tags | array | – | Tags (replaces the existing tags on update; [] clears them). |
No output schema declared.
No examples provided.
How do I install the Placetel MCP by usefulapi server?
Placetel MCP by usefulapi is a hosted endpoint at https://placetel.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 · placetel.usefulapi.io
claude mcp add --transport http io-usefulapi-placetel 'https://placetel.usefulapi.io/mcp'
What is the Placetel MCP by usefulapi server?
Placetel MCP by usefulapi is listed in the public MCP registry as io.usefulapi/placetel. Read Placetel calls, recordings, numbers and routing; edit contacts, start calls, send SMS. This page covers its hosted endpoint (https://placetel.usefulapi.io/mcp).
Is the Placetel MCP by usefulapi server safe to use?
Placetel MCP by usefulapi scores 62 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 Placetel MCP by usefulapi server expose?
Placetel MCP by usefulapi exposes 28 tools: placetel_get_account, placetel_list_users, placetel_list_sip_users, placetel_get_sip_user, placetel_list_calls, and 23 more. Their descriptions and schemas cost roughly 3,535 tokens of context every time the server is loaded.
Does the Placetel MCP by usefulapi server require authentication?
Yes. Placetel 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 Placetel MCP by usefulapi server still maintained?
Placetel 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.