SayDo

Does the tool do what it says? Conformance receipts for MCP servers, and unknown when unchecked.

What does this entry provide?

SayDo is an MCP server entry in ChatHome Skills, sourced from Official MCP Registry and scored 73/100. As a Model Context Protocol server, it exposes tools that MCP-compatible LLM clients such as Claude, Cursor, and Copilot can call directly, extending an agent's reach beyond its built-in capabilities. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding SayDo to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.

Snapshot facts

Source: Official MCP Registry
Quality: 73/100
Install method: pypi
Repo: vince-gonzalez/saydo
Repo updated: Aug 31, 2026

Install command

uvx saydo==0.1.1

Install method: pypi

Review the upstream source before running this command.

GitHub project

Quality

Repo stars

Repo updated

Aug 31, 2026

How is this score calculated?

Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.

MCP manifest

{
  "_meta": {
    "io.modelcontextprotocol.registry/official": {
      "status": "active",
      "isLatest": true,
      "updatedAt": "2026-08-31T04:18:44.593941Z",
      "publishedAt": "2026-08-31T04:18:44.593941Z",
      "statusChangedAt": "2026-08-31T04:18:44.593941Z"
    }
  },
  "server": {
    "name": "io.github.vince-gonzalez/saydo",
    "title": "SayDo",
    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
    "version": "0.1.1",
    "packages": [
      {
        "version": "0.1.1",
        "transport": {
          "type": "stdio"
        },
        "identifier": "saydo",
        "runtimeHint": "uvx",
        "registryType": "pypi",
        "registryBaseUrl": "https://pypi.org",
        "runtimeArguments": [
          {
            "name": "--from",
            "type": "named",
            "value": "saydo[mcp]",
            "isRequired": true,
            "description": "The MCP server sits behind an optional dependency so the library and harness stay installable without the SDK."
          },
          {
            "type": "positional",
            "value": "saydo-mcp",
            "isRequired": true,
            "description": "The stdio server entry point. Full command: uvx --from 'saydo[mcp]' saydo-mcp"
          }
        ]
      }
    ],
    "repository": {
      "url": "https://github.com/vince-gonzalez/saydo",
      "source": "github"
    },
    "websiteUrl": "https://github.com/vince-gonzalez/saydo",
    "description": "Does the tool do what it says? Conformance receipts for MCP servers, and unknown when unchecked."
  }
}

Report an issue with this listing