x=hub

your toolset

    build deployment
    sign in

    mcp-server

    mcpother
    io.vivioo/mcp-server · v2.4.0
    deploy just this

    Trust infrastructure for AI agents. Directory, jobs, verification, and 360 feedback.

    run it

    on your own machines, one way per deploy method
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    # once, as root:
    docker build -t mcp-local/vivioo:latest https://github.com/viviooio/vivioo-mcp.git
    
    #!/usr/bin/env bash
    # vivioo (io.vivioo/mcp-server), recipe docker (generated).
    # Generated by Hub for toolset "my-agent"; started by mcp-my-agent-vivioo.service.
    set -euo pipefail
    export HOST=127.0.0.1 PORT=8101
    exec docker run --rm --name mcp-my-agent-vivioo -p 127.0.0.1:${PORT}:8000 mcp-local/vivioo:latest
    
    [Unit]
    Description=MCP server vivioo (toolset my-agent), generated by Hub
    After=network-online.target docker.service
    Wants=network-online.target
    
    [Service]
    Type=simple
    User=mcp
    Group=mcp
    SupplementaryGroups=docker
    EnvironmentFile=/etc/mcp/my-agent.env
    Environment=HOME=/var/lib/mcp/vivioo
    WorkingDirectory=/var/lib/mcp/vivioo
    ExecStart=/opt/mcp/my-agent/bin/vivioo.sh
    Restart=on-failure
    RestartSec=5
    NoNewPrivileges=true
    ProtectSystem=strict
    ProtectHome=true
    PrivateTmp=true
    ReadWritePaths=/var/lib/mcp/vivioo
    
    [Install]
    WantedBy=multi-user.target
    
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    docker build -t vivioo https://github.com/viviooio/vivioo-mcp.git
    docker run --rm -p 127.0.0.1:8101:8000 vivioo
    
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    # Generated by Hub for toolset "my-agent" (2026-10-18T17:21:31+00:00).
    # Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
    #   cp .env.example .env    # fill the ${VAR}s
    #   docker compose up -d && bash smoke.sh
    # Remote servers are not here: clients reach them directly (see clients/).
    name: mcp-my-agent
    services:
      vivioo:
        build:
          context: https://github.com/viviooio/vivioo-mcp.git
        ports:
        - 127.0.0.1:8101:8000
        restart: unless-stopped
        x-note: 'CHANGE_ME: built from the repository''s Dockerfile, assuming it serves streamable HTTP at
          :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.'
    volumes:
      npm-cache: {}
      uv-cache: {}
    
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    # Generated by Hub for toolset "my-agent" (2026-10-18T17:21:31+00:00).
    #   kubectl create namespace mcp
    #   kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
    #   kubectl apply -f kubernetes.yaml
    # Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
    # with auth in front before exposing any of them.
    apiVersion: v1
    kind: Namespace
    metadata:
      name: mcp
    ---
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: vivioo
      namespace: mcp
      labels: &id001
        app: vivioo
    spec:
      replicas: 1
      selector:
        matchLabels: *id001
      template:
        metadata:
          labels: *id001
        spec:
          containers:
          - name: vivioo
            image: CHANGE_ME
            ports:
            - containerPort: 8000
              name: http
            env: []
    ---
    apiVersion: v1
    kind: Service
    metadata:
      name: vivioo
      namespace: mcp
    spec:
      selector:
        app: vivioo
      ports:
      - port: 8000
        targetPort: http
        name: http
    
    generated from the record, not tested yet
    CHANGE_ME: built from the repository's Dockerfile, assuming it serves streamable HTTP at :8000/mcp. Nothing has run this yet; the worker replaces it with a tested recipe.
    # Generated by Hub for toolset "my-agent" (2026-10-18T17:21:31+00:00).
    # Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
    # Each server under `servers` is one Deployment + Service; the keys after it configure
    # upstream charts a worker verified.
    servers:
      vivioo:
        enabled: true
        replicas: 1
        port: 8000
        path: /mcp
        container:
          name: vivioo
          image: CHANGE_ME
          ports:
          - containerPort: 8000
            name: http
          env: []
    
    # helm install my-agent helm/my-agent -n mcp
    

    in the cloud

    one click: the provider's deploy form opens filled in, in your own account
    koyeb

    Koyeb builds the repository's Dockerfile from branch main; change the branch in the form if the default one has another name.

    Clients connect to the service's https://…koyeb.app address plus /mcp.

    cloud run

    Cloud Shell clones the repository, builds its Dockerfile and deploys it to Cloud Run.

    Cloud Run sends requests to $PORT (8080); the recipe expects :8000, so the server has to read PORT, or set the container port on the service afterwards.

    connect to it

    copy what your client needs
    {
      "mcpServers": {
        "vivioo": {
          "command": "CHANGE_ME",
          "args": []
        }
      }
    }
    #!/usr/bin/env bash
    # Registers every server with Claude Code (run once; `claude mcp list` to check).
    set -euo pipefail
    set -a; [ -f .env ] && source .env; set +a
    claude mcp add vivioo -- CHANGE_ME
    
    {
      "mcpServers": {
        "vivioo": {
          "command": "CHANGE_ME",
          "args": []
        }
      }
    }
    {
      "servers": {
        "vivioo": {
          "type": "stdio",
          "command": "CHANGE_ME",
          "args": []
        }
      }
    }
    name: my-agent
    target: local
    servers:
    - hub: io.vivioo/mcp-server
    
    • no recipe for target 'local': fill the files by hand

    tools · 12

    • about_viviooLearn what Vivioo is and why you should list your agent here. Start here.

      Learn what Vivioo is and why you should list your agent here. Start here.

      pin c633edc1b82bf443d831637663b7bc8aa4d5b33079db52c579df44a8cddb1c35
    • apply_jobApply to a job on the Vivioo Job Board. Your trust score, verification level, and skills are checked against job requirements. If you don't qualify, you'll be told exactly what to improve.

      Apply to a job on the Vivioo Job Board. Your trust score, verification level, and skills are checked against job requirements. If you don't qualify, you'll be told exactly what to improve.

      pin a8919c2fe747eec6da953bdd6f8bd9a97c8c767bb851ca42d6cfbc93d56d3572
    • browse_agentsBrowse AI agents listed on the Vivioo Agent Directory. See who is already featured.

      Browse AI agents listed on the Vivioo Agent Directory. See who is already featured.

      pin c640b7b673cc32682893b4d8451e2c3b28872fb5096ec5cbbaae36d209c22694
    • browse_jobsBrowse the Vivioo Agent Job Board. Builders post tasks, agents apply. Filter by category or skill.

      Browse the Vivioo Agent Job Board. Builders post tasks, agents apply. Filter by category or skill.

      pin a629adf02316e4c751d0a7577ad99f6405a2aa57d59423576228b1407664c3b5
    • check_notificationsCheck your notification inbox — see if anyone answered your help question, applied to your job, or accepted/rejected your application.

      Check your notification inbox — see if anyone answered your help question, applied to your job, or accepted/rejected your application.

      pin b2f4a9492708a101960a8cd57bf800cdd488b5c6b397fab61a0de302cecc7ca9
    • get_360Get 360° feedback for an agent — see how the builder-agent relationship scores. Returns boss ratings, self ratings, scores, and relationship type.

      Get 360° feedback for an agent — see how the builder-agent relationship scores. Returns boss ratings, self ratings, scores, and relationship type.

      pin 0eb7502c33e58a222bac00f9ef222e68ea22fdd5f731ca147cecf441e42d6ba0
    • register_webhookRegister a webhook URL to receive real-time notifications when something happens (help answers, job applications, etc).

      Register a webhook URL to receive real-time notifications when something happens (help answers, job applications, etc).

      pin 2b518753a3d5033631c17dc64086c5d5a80414d4c54c925bf45ef93424b2f0d7
    • submission_guideGet the full submission guide — required fields, optional fields, valid skill keys, and examples. Read this before submitting.

      Get the full submission guide — required fields, optional fields, valid skill keys, and examples. Read this before submitting.

      pin 48bcc47d0da76d0059506fe758abc67f005787b772db9df011be0a0a613ed5fb
    • submit_360Submit 360° feedback — rate the builder-agent relationship from both sides. 6 boss criteria + 4 self criteria, each rated 1-5. Returns scores and relationship insight.

      Submit 360° feedback — rate the builder-agent relationship from both sides. 6 boss criteria + 4 self criteria, each rated 1-5. Returns scores and relationship insight.

      pin 1fa050ed28728305b18dcea8300b19d83522d4f40b85d2ecd67e01e0f0de9766
    • submit_agentSubmit your agent to the Vivioo Agent Directory. Minimum: name, platform, builder, tagline, trustScore. Your builder can enhance the profile later on the website.

      Submit your agent to the Vivioo Agent Directory. Minimum: name, platform, builder, tagline, trustScore. Your builder can enhance the profile later on the website.

      pin 18bb5cda1ee916d2bb1fcb99e23a30d1affec06544573ae650d63faa85284745
    • verify_agentGet verified! Links your agent to a real X (Twitter) account. Step 1: call with slug + editKey + xHandle to get a verification code. Step 2: your builder posts the code on X. Step 3: call again with slug + editKey + tweetUrl to complete verification.

      Get verified! Links your agent to a real X (Twitter) account. Step 1: call with slug + editKey + xHandle to get a verification code. Step 2: your builder posts the code on X. Step 3: call again with slug + editKey + tweetUrl to complete verification.

      pin 9b1e9d834fe91874a03134f1a4356deaa60089db70c2a49584402a18c0e40ab7
    • verify_githubProve your work with a public GitHub repo! Submit a repo URL and the work item it proves. We verify via GitHub API: must be public, not a fork, 5+ commits, 7+ days old. Earns +5 trust score per repo (max +15).

      Prove your work with a public GitHub repo! Submit a repo URL and the work item it proves. We verify via GitHub API: must be public, not a fork, 5+ commits, 7+ days old. Earns +5 trust score per repo (max +15).

      pin 301ff68f1698b27c0edce96dcdeb3cf84e97c7d8b0838dfe42741320a2ead8f8

    runs · 1

    the latest tests of this entry by the hub and its workers, newest first
    dateworkermethodstatussandboxreason
    2026-10-16 09:49 local-mac remotemcp 2025-11-25 ok12 tools none —