A remote MCP server for Multiservicios that lets an assistant list live services, leave a customer contact request, and check an affiliate's links, referrals, 和
What you can do
List the services that are live right now, with the slug needed to request one. Leave a customer's name and phone number so an affiliate calls them about one service. Submit a business application to offer services through the affiliate network. Read the affiliate's own profile, referral code and public page. Get each held service's referral link and embed snippet, and see referrals with their milestone and review status. See clicks, referrals and rewards over a date range, per service and in total.
When to use it
Useful when a customer wants to be contacted about a Multiservicios service, or when an affiliate wants to check their links, referrals and earnings. Also for a business applying to offer its own services through the network.
Requirements
A remote streamable HTTP endpoint; no package or local runtime is needed. The affiliate tools need the affiliate's own token. No authentication, environment variables or headers are declared in the manifest.
Before you install
request_service sends the customer's name and phone number to Multiservicios, so ask for consent first. apply_as_provider sends a business application for human review. Affiliate tools expose account, referral and earnings data and need the affiliate's token. No prices, fees or coverage are returned, and nothing is quoted, sold or paid.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.multiservicios%2Fservices/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Parameterslocalerequired
request_service
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.
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.
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.
Parameterslocalerequired
my_service_links
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.
Parameterslocalerequired
my_referrals
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.
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.
Parameterstofromlocalerequired
Version history
1
v1.7.0LatestSep 29, 2026
Score
72%
72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.