MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Other

Multiservicios services

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

Checks passed
12 / 22

2 failed · 8 not measured

Median response
521 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
7

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
222

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 521 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name multiservicios.

  • Pass
    Lists tools

    tools/list returned 7 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 521 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 521 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    28 of 28 parameters have a description (100%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Fail
    Website matches publisher

    The website host does not match the reverse-domain namespace.

  • Fail
    Source repo linked

    No repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-09-28T15:19:44.125948Z, within 180 days.

  • Not measured
    Open-source licence

    No GitHub repository to ask about a licence.

Start using Multiservicios services

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

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

Capabilities

Tools 7

apply_as_provider

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.

Discovered
list_services

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.

Discovered
my_account

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.

Discovered
my_earnings

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.

Discovered
my_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.

Discovered
my_service_links

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.

Discovered
request_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.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected521 ms7