Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Multiservicios services

REMOTE · MCP.MULTISERVICIOS.AI · SCANNED SEP 29

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

66 Trust /100
Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • 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. 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 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

remote · mcp.multiservicios.ai

# add to Claude Code
claude mcp add --transport http ai-multiservicios-services 'https://mcp.multiservicios.ai/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-multiservicios-services": {
      "url": "https://mcp.multiservicios.ai/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-multiservicios-services": {
      "type": "http",
      "url": "https://mcp.multiservicios.ai/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-multiservicios-services --url 'https://mcp.multiservicios.ai/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-multiservicios-services:
    url: "https://mcp.multiservicios.ai/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-multiservicios-services": {
      "Transport": "http",
      "Url": "https://mcp.multiservicios.ai/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ai-multiservicios-services -t streamable-http -u 'https://mcp.multiservicios.ai/mcp'
// mcp.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 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.

  • 29 Sept 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 28 Sept 26 65

    First indexed and scored.

Diagnostics

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 29 Sept 2026 · Probed https://mcp.multiservicios.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=multiservicios.ai CN=WE1,O=Google Trust Services,C=US 1 Sept 2026 30 Nov 2026 ECDSA 256 ECDSA-SHA256 2cb22192fe3f17d70edbaaf4af72c661
SANs: multiservicios.ai, *.multiservicios.ai
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 mcp.multiservicios.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
multiservicios.ai. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.multiservicios.ai/mcp Verified 200
http (plaintext) http://mcp.multiservicios.ai/mcp Inconclusive 406
MCP tools · 7 exposed · ~1,526 tokens

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 →

Tool Tokens
apply_as_provider ~383

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.

NameTypeReqDescription
business_namestringyesThe business's name, as its owner writes it.
categorystringyesThe closest kind of service. Use `other` when nothing fits.
consentbooleanyesThe person has said, in their own words, that Multiservicios may contact them about this application. Ask them; never assume it.
contact_namestringyesWho we should talk to about the application.
descriptionstringyesWhat the business offers, to whom, and in which languages — in its own words.
emailstringyesWhere we write back about the application.
localestringyesThe language the person is writing in. The reply comes back in it.
phonestringyesA number to reach the contact, as they write it.
statesarrayyesTwo-letter codes of the US states where the business offers the service.
websitestring–The business's website, if it has one.
NameTypeReqDescription
messagestringyesWhat to tell the person, in their language.
notestringyes–
statusstringyes–

No examples provided.

list_services ~153

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.

NameTypeReqDescription
localestringyesThe language the customer is writing in — set it from their own messages. Everything the customer is meant to hear comes back in this language.
NameTypeReqDescription
notestringyes–
pricingobjectyes–
servicesarrayyes–

No examples provided.

my_account ~89

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.

NameTypeReqDescription
localestringyesThe 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.
NameTypeReqDescription
codestringyesThe referral code this affiliate's links carry.
namestringyes–
notestringyes–
socio_page_urlstring|nullyesThe affiliate's public page, when the connector was told the site's address.
statusstringyes`active` while the affiliate can be credited for referrals.

No examples provided.

my_earnings ~145

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.

NameTypeReqDescription
fromstring–First day, YYYY-MM-DD. Default 30 days ago.
localestringyesThe 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.
tostring–Last day, YYYY-MM-DD. Default today.
NameTypeReqDescription
by_servicearrayyes–
notestringyes–
rangeobjectyes–
totalsobjectyes–

No examples provided.

my_referrals ~172

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.

NameTypeReqDescription
kindstring–Only referrals of this milestone.
limitinteger–How many rows to return. Default 20.
localestringyesThe 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.
offsetinteger–Rows to skip, for the next page.
service_slugstring–Only referrals for this service.
statusstring–Only referrals in this review state.
NameTypeReqDescription
limitnumberyes–
notestringyes–
offsetnumberyes–
referralsarrayyes–
totalnumberyes–

No examples provided.

my_service_links ~99

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.

NameTypeReqDescription
localestringyesThe 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.
NameTypeReqDescription
notestringyes–
servicesarrayyes–

No examples provided.

request_service ~485

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.

NameTypeReqDescription
consentbooleanyesThe 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.
localestringyesThe language the customer is writing in — set it from their own messages. Everything the customer is meant to hear comes back in this language.
namestringyesWhat the customer wants to be called when the affiliate phones. A first name is enough; do not ask for a full legal name.
phonestringyesThe 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_slugstringyesThe `slug` of a service from list_services. Only a live service can be requested.
socio_codestring–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…
NameTypeReqDescription
follow_upobjectyes–
messagestringyesWhat to tell the customer, in their language.
notestringyes–
referencestringyesStable for this request. Repeating the call with the same details returns it again.
scope_notestringyes–
service_slugstringyes–
statusstringyes–

No examples provided.

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.