Vivere

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

검사 2/3 통과 · 내가 묻는 내용은 제작자 서버(vivere.dev)를 거쳐요 · ✓ 명령 확인 2026년 11월 13일

claude mcp add --transport http --scope user monitors https://vivere.dev/mcp --header 'Authorization: Bearer your-value'

{
  "mcpServers": {
    "monitors": {
      "url": "https://vivere.dev/mcp",
      "headers": {
        "Authorization": "Bearer your-value"
      }
    }
  }
}

{
  "servers": {
    "monitors": {
      "type": "http",
      "url": "https://vivere.dev/mcp",
      "headers": {
        "Authorization": "Bearer your-value"
      }
    }
  }
}

어떤 앱에서 쓸 수 있나요

이 서버의 연결 방식과 각 앱의 공식 문서를 바탕으로 했어요. 2026년 11월 10일 확인.

인터넷으로 연결하는 앱

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

모든 앱과 장단점 →

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 9일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

• list_pages

  List the pages this account can see: its own, then pages other accounts share with it, each with the access it has there (owner, editor or viewer) and how many monitors are on it and down.

• list_monitors

  List the monitors on every page this account can see, or on one page, with status, page and access. Monitors on a page shared to view have no id; address them by page_id and slug.

• get_monitor

  Get one monitor by id, including its ping URL for heartbeat monitors, or by page_id and slug, which also works on a page shared to view.

• create_monitor

  Create a heartbeat monitor (default) or an HTTP check on the account's first page or on page_id, which may be a page shared with this account as editor. Returns the monitor and, for heartbeats, the ping URL to call after each run.

• check_in

  Report on a heartbeat monitor: 'success' after a completed run (resets the deadline), 'start' when a run begins, 'fail' when it failed. Include a short message; it is kept as the run log.

• pause_monitor

  Pause a monitor so it stops alerting until resumed or pinged again.

• resume_monitor

  Resume a paused monitor.

• get_account

  Which account this key belongs to, its plan's limits and what it uses of them, and what this key may do: its permission on each resource (none, read or write) and the pages it is limited to, if any.

• update_monitor

  Change a monitor. Only the fields given change; its kind cannot. Setting cron switches a heartbeat to a cron schedule and setting period switches it back. Only the page's owner can move it, with page_id, to another of their own pages.

• delete_monitor

  Delete a monitor and all its history. This cannot be undone; pause_monitor stops alerts without losing anything.

• list_runs

  A heartbeat monitor's newest runs with their outcome, duration, exit code and any model, tokens and cost they reported, plus what its runs cost over 30 days.

• get_run

  One run with the output it sent (the log), where it came from and what it cost.

• list_monitor_events

  One monitor's status changes (up, down, late, paused), newest first.

• list_events

  Status changes across the account's own monitors, newest first.

• get_page

  One page: its public address, monitors and, on your own pages, who it is shared with and as what.

• create_page

  Add a page to group monitors under, within the plan's pages. Its slug is its public address, made from the title when not given.

• update_page

  Rename one of your pages or change its slug, which moves its public address.

• delete_page

  Delete one of your pages. Only an empty page that is not your first can go.

• make_page_private

  Turn off Public on every monitor on one of your pages, which takes its public status page down.

• share_page

  Share one of your pages with the account of a person who has a Vivere login (email) or with one of your teams (team_id), as viewer or editor, or change the role they have. Needs a paid plan, a free seat for anybody new, and the Team plan for teams.

• unshare_page

  Stop sharing one of your pages with an account (account_id, from get_page) or a team (team_id). Their alert channels come off its monitors.

• list_teams

  Your teams, with how many members and pages each has.

• get_team

  One team: its members and the pages shared with it.

• create_team

  Make a team, on the Team plan.

• rename_team

  Rename a team.

• delete_team

  Delete a team. Its members lose the pages it gave them.

• add_team_member

  Add the account of a person with a Vivere login to a team. Joining a team that has pages takes a seat.

• remove_team_member

  Take an account out of a team.

• list_channels

  Your alert channels. Secret settings are never shown; secrets_set names the ones that have a value.

• create_channel

  Add an alert channel. Settings by kind: email {to}; webhook {url, secret}; slack {url}; discord {url}; telegram {token, chat_id}; ntfy {url, token}. Slack, Discord, Telegram and ntfy need a paid plan.

• update_channel

  Rename a channel or change its settings. Settings left out keep their value.

• delete_channel

  Delete an alert channel. Monitors stop sending alerts to it.

• test_channel

  Send a test alert to a channel.

• list_pixels

  Your tracking pixels, with the tag to paste and how often each has loaded.

• get_pixel

  One pixel and its newest loads: when, from which page, browser, language and platform.

• create_pixel

  Make a tracking pixel, within the plan's pixels. Returns the tag to paste into a page or an email.

• delete_pixel

  Delete a pixel and every load it recorded.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 14일 점검

• ! 주의

  제작자와 저장소 일치

  레지스트리에 소스 저장소가 없어서, 게시자(vivere.dev)와 코드를 맞춰 볼 수 없어요

• … 아직 점검 안 함

  계속 관리되고 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• … 아직 점검 안 함

  라이선스 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• ✓ 통과

  엔드포인트 응답

  1142ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✓ 통과

  도구 설명에 숨겨진 지시 없음

  도구 설명 37개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

사용자 리뷰

아직 리뷰가 없어요

Google로 로그인하고 리뷰 쓰기

기타 카테고리의 다른 서버와 비교i

• 이 카테고리의 다른 서버 19732개 중 0%보다 스타가 많아요
• 이 카테고리의 다른 서버 19732개 중 41%보다 최근에 레지스트리에 공개됐어요
• 기본 점검 결과가 이 카테고리의 다른 서버 19732개 중 45%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

같은 카테고리의 다른 것

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.

제작자: koala73·널리 사용됨·★ 9.1만·어제 업데이트

클라우드에서 실행✓ 서비스 회사 · worldmonitor.app

연결 방법

Claude Flow

AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.

제작자: ruvnet·널리 사용됨·↓ 1.4만/주·★ 8.2만·14개월 전 업데이트

내 컴퓨터에서 실행

설치

Windmill

Run Windmill scripts and flows and manage jobs, schedules, resources and variables.

제작자: windmill-labs·널리 사용됨·★ 1.9만·그저께 업데이트

클라우드에서 실행

연결 방법

제작자의 README

저장소에서 README를 찾지 못했어요