# Multiservicios services (remote · mcp.multiservicios.ai)

Lists Multiservicios services and leaves a request to be contacted. Does not quote, sell or issue.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `mcp.multiservicios.ai`: 66/100 (this document), [markdown](https://verifymcp.io/servers/ai-multiservicios-services/mcp.md), [page](https://verifymcp.io/servers/ai-multiservicios-services/mcp)

## Channel facts

- Endpoint: `https://mcp.multiservicios.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.7.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1765 tokens (~252/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Multiservicios services MCP server?

Multiservicios services is a hosted endpoint at https://mcp.multiservicios.ai/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.

### Claude

```bash
claude mcp add --transport http ai-multiservicios-services 'https://mcp.multiservicios.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-multiservicios-services": {
      "url": "https://mcp.multiservicios.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-multiservicios-services": {
      "type": "http",
      "url": "https://mcp.multiservicios.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-multiservicios-services]
url = "https://mcp.multiservicios.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-multiservicios-services": {
      "type": "remote",
      "url": "https://mcp.multiservicios.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-multiservicios-services --url 'https://mcp.multiservicios.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-multiservicios-services:
    url: "https://mcp.multiservicios.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-multiservicios-services": {
      "Transport": "http",
      "Url": "https://mcp.multiservicios.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-multiservicios-services -t streamable-http -u 'https://mcp.multiservicios.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-multiservicios-services": {
      "type": "http",
      "url": "https://mcp.multiservicios.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-29 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-28 (score 65)

First indexed and scored.

## MCP tools (7)

### `list_services` (~153 tokens)

Services Multiservicios can put an affiliate on

The services that are live right now, with the `slug` to pass to request_service. Call it before asking the customer anything: a service that is not in this list cannot be requested, and offering one that is not there costs the customer a wait for a call that never comes.

No price, fee or coverage is returned, and there is none to look up: Multiservicios puts an affiliate on the phone, and the affiliate goes through it with the customer. Sigo Seguros is a licensed insurance agency, not an insurance carrier.

Input parameters:

- `locale` (string, required): The language the customer is writing in — set it from their own messages. Everything the customer is meant to hear comes back in this language.

Output parameters:

- `note` (string)
- `pricing` (object)
- `services` (array)

### `request_service` (~485 tokens)

Ask an affiliate to call the customer about a service

Leaves the customer's name and phone number with Multiservicios so an affiliate calls them about one service. It does not quote, price, sell, take payment or bind anything, and it confirms no coverage.

Ask for consent in the customer's own words before calling this — "is it alright if an affiliate calls you about this?" — and send `consent: true` only once they have said so. Without it nothing is recorded.

The intake asks for the service, a name, a phone number, consent and a language, and nothing else. An address, a document or ID number, an immigration status or a date of birth is refused rather than dropped, because nothing here has anywhere to put it.

A successful call is final: it comes back with `status: "received"` and a `reference`, and there is nothing more to send. Do not call it again for the same customer and service — a repeat inside the same conversation returns the same reference rather than a second call to the customer, but a request that genuinely failed says so, with `delivery_failed` and `isError`, and that one is worth retrying.

Input parameters:

- `consent` (boolean, required): The customer has said, in their own words, that an affiliate may call them about this service. Ask them; never assume it from the fact that they gave a number.
- `locale` (string, required): The language the customer is writing in — set it from their own messages. Everything the customer is meant to hear comes back in this language.
- `name` (string, required): What the customer wants to be called when the affiliate phones. A first name is enough; do not ask for a full legal name.
- `phone` (string, required): The number to call back, as the customer writes it. An affiliate dials this, so ordinary shapes are fine: +1 555 010 0000, 512 555 0123, (512) 555-0123.
- `service_slug` (string, required): The `slug` of a service from list_services. Only a live service can be requested.
- `socio_code` (string): Only when the customer read an affiliate's code off a flyer, a card or a link they were given. Leave it out otherwise — it is not something to ask for, and never something to invent. The answer is th…

Output parameters:

- `follow_up` (object)
- `message` (string): What to tell the customer, in their language.
- `note` (string)
- `reference` (string): Stable for this request. Repeating the call with the same details returns it again.
- `scope_note` (string)
- `service_slug` (string)
- `status` (string)

### `apply_as_provider` (~383 tokens)

Apply for a business to sell its services through Multiservicios

For a BUSINESS that wants to offer its own services through the Multiservicios affiliate network — not for a customer looking for a service (use request_service) and not for someone who wants to refer customers as an affiliate. It sends an application that a person reviews; it does not list the business, promise approval, or create any service.

Ask for the business name, a contact name, email, phone, the kind of service, the US states where it is offered and a short description. Ask for consent in the person's own words — "is it alright if Multiservicios contacts you about this?" — and send `consent: true` only once they have said so. No document, ID number or immigration status is asked for or accepted.

A successful call comes back with `status: "received"`. Do not send it again.

Input parameters:

- `business_name` (string, required): The business's name, as its owner writes it.
- `category` (string, required): The closest kind of service. Use `other` when nothing fits.
- `consent` (boolean, required): The person has said, in their own words, that Multiservicios may contact them about this application. Ask them; never assume it.
- `contact_name` (string, required): Who we should talk to about the application.
- `description` (string, required): What the business offers, to whom, and in which languages — in its own words.
- `email` (string, required): Where we write back about the application.
- `locale` (string, required): The language the person is writing in. The reply comes back in it.
- `phone` (string, required): A number to reach the contact, as they write it.
- `states` (array, required): Two-letter codes of the US states where the business offers the service.
- `website` (string): The business's website, if it has one.

Output parameters:

- `message` (string): What to tell the person, in their language.
- `note` (string)
- `status` (string)

### `my_account` (~89 tokens)

The affiliate's own profile and referral code

The affiliate's own profile: the referral code their links carry, the state of their account, and their public affiliate page. Needs the affiliate's own token; it answers for nobody else, and it holds nothing about a customer.

Input parameters:

- `locale` (string, required): The language the affiliate is writing in — set it from their own messages. Everything meant to be read back to them comes back in this language.

Output parameters:

- `code` (string): The referral code this affiliate's links carry.
- `name` (string)
- `note` (string)
- `socio_page_url` (string|null): The affiliate's public page, when the connector was told the site's address.
- `status` (string): `active` while the affiliate can be credited for referrals.

### `my_service_links` (~99 tokens)

The affiliate's own link for each service

Each service this affiliate holds, with their own referral link and an HTML snippet to embed it. A service the affiliate has switched off is reported as disabled: sharing it credits no referral. No price, fee or coverage is returned, and there is none here to look up.

Input parameters:

- `locale` (string, required): The language the affiliate is writing in — set it from their own messages. Everything meant to be read back to them comes back in this language.

Output parameters:

- `note` (string)
- `services` (array)

### `my_referrals` (~172 tokens)

The affiliate's own referrals

The referrals credited to this affiliate, with the milestone each one reached and where its review stands. Every referral is reviewed by a person, so a pending one is not an earned reward. Nothing identifies the customer: the connector cannot show who was referred, because that data is not on this surface.

Input parameters:

- `kind` (string): Only referrals of this milestone.
- `limit` (integer): How many rows to return. Default 20.
- `locale` (string, required): The language the affiliate is writing in — set it from their own messages. Everything meant to be read back to them comes back in this language.
- `offset` (integer): Rows to skip, for the next page.
- `service_slug` (string): Only referrals for this service.
- `status` (string): Only referrals in this review state.

Output parameters:

- `limit` (number)
- `note` (string)
- `offset` (number)
- `referrals` (array)
- `total` (number)

### `my_earnings` (~145 tokens)

The affiliate's own totals, approved and in review

Clicks, referrals and rewards for this affiliate over a date range, per service and in total. Approved and in-review rewards are two separate numbers and must stay that way: a reward in review has not been approved and is not owed, because a person reviews every referral and may decide against it. Never add them together.

Input parameters:

- `from` (string): First day, YYYY-MM-DD. Default 30 days ago.
- `locale` (string, required): The language the affiliate is writing in — set it from their own messages. Everything meant to be read back to them comes back in this language.
- `to` (string): Last day, YYYY-MM-DD. Default today.

Output parameters:

- `by_service` (array)
- `note` (string)
- `range` (object)
- `totals` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-multiservicios-services/mcp#diagnostics

## Score history

- 2026-09-29: 66
- 2026-09-28: 65

## Common questions

### What is the Multiservicios services MCP server?

Multiservicios services is an MCP server listed in the public MCP registry as ai.multiservicios/services. Lists Multiservicios services and leaves a request to be contacted. Does not quote, sell or issue. This page covers its hosted endpoint (https://mcp.multiservicios.ai/mcp).

### Is the Multiservicios services MCP server safe to use?

Multiservicios services scores 66 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 Multiservicios services MCP server expose?

Multiservicios services exposes 7 tools: list_services, request_service, apply_as_provider, my_account, my_service_links, and 2 more. Their descriptions and schemas cost roughly 1,526 tokens of context every time the server is loaded.

### Does the Multiservicios services MCP server require authentication?

No. We connected to Multiservicios services without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Multiservicios services MCP server still maintained?

Multiservicios services is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.multiservicios.ai/mcp
- Website: https://mcp.multiservicios.ai/doc
- Changelog RSS feed: https://verifymcp.io/servers/ai-multiservicios-services/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-multiservicios-services/mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-multiservicios-services/mcp