Yesno Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.4Updated Oct 29, 2026

Random yes or no answers from the Yes No API. No key required.

VerifiedSTDIODesktop only

Overview

AI-generated overview

A local MCP server that gives an assistant random yes-or-no answers from the Yes No API, with no API key required.

What you can do
  • Fetch a random yes or no answer from the Yes No API on request.
  • Use the result as a playful tie-breaker or decision prompt inside a conversation.
  • No other tools are documented in the manifest, description or README.
When to use it
Useful when you want a lightweight, whimsical way to get a random yes/no verdict during a chat, for example for fun decisions or brainstorming. It is not suited to decisions that need real reasoning or data.
Requirements
Runs as a local process over stdio, installed from the npm package yesno-mcp, so Node.js and npm are needed. No API key, environment variables or headers are declared. Network access is implied by calling an external API.
Before you install
Answers are random and carry no reasoning, so do not rely on them for consequential decisions. Requests go to a third-party public API, so the fact that a query was made leaves your machine.

Installation

In SourceWeft

  1. Open Yesno Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

2
  1. v1.0.4LatestOct 29, 2026
  2. v1.0.0Sep 22, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.