Koskamo

Notary MCP

Notary is a dependency pre-flight check that verifies npm and PyPI package existence, versions, age, downloads, deprecation status, and look-alike risks against live registries before installation. It helps AI agents and developers prevent installing non-existent or malicious packages by checking public registry data without requiring an account.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Notary MCP logo, by Clawhard StudioVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-09Operated by Clawhard Studio
MCP endpoint (Streamable HTTP)
https://notary.clawhard.com/mcp
Vendor documentation

What its tools do

1 tool, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

1 of 1 have a description · 1 of 1 declare behavior hints · 1 of 1 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to clawhard.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Verify npm or PyPI package existence before running install commands
  • Check if a pinned version exists and is not deprecated or yanked
  • Identify potential typosquatting or look-alike package names
  • Validate package.json or requirements.txt dependencies via AI agents

Source and maintenance

Vendor evidenceRegistry 1.0.0

Protocol and capabilities

Server
com.clawhard/notary 1.0.0
MCP protocol negotiated in check
2025-11-25
Tools
1 advertised
Resources
2 advertised
Resource templates
0 advertised
Prompts
1 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  },
  "prompts": {
    "listChanged": false
  },
  "resources": {
    "subscribe": false,
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Notary: Notary checks npm and PyPI package names against the live registry before you install them: does it exist, does that version exist, how old and how used is it, is it deprecated, does it run install scripts, is it a typo of a famous package. No account. Use it when the user or an AI agent is about to install or import npm or PyPI packages, asks whether a package exists or is safe to install, or pastes a package.json or requirements.txt with names that may have been invented by an AI. Tools: notary_check_packages (Check that npm and PyPI packages really exist before installing them). Results include a link (open_url) that the user can open to see the same result on the website.

Tools

1 advertised

notary_check_packages — Check that npm and PyPI packages really exist before installing them
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Use when the user or an agent is about to install or import npm or PyPI packages: before npm install or pip install, when adding lines to package.json or requirements.txt, or when a package name came from an AI answer, a tutorial or memory and may be invented. Looks each name up in the live registry and returns whether it exists, the latest version, whether a pinned version exists, weekly downloads, first and last publish dates, deprecation or yanked status, install-time scripts, whether the name is one or two typed characters from a well-known package, and real similar packages when the name does not exist. Example: {"packages":[{"ecosystem":"npm","name":"@anthropic/mcp-client"},{"ecosystem":"pypi","name":"requests","version":"2.32.3"}]}. Up to 10 packages per call; versions must be exact, not ranges. Not a malware or vulnerability scan: "ok" means it exists and nothing looked wrong.

notary_check_packages input schema
{
  "type": "object",
  "required": [
    "packages"
  ],
  "properties": {
    "packages": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "ecosystem",
          "name"
        ],
        "properties": {
          "name": {
            "type": "string",
            "maxLength": 214,
            "minLength": 1,
            "description": "The package name only, e.g. left-pad, @types/node or requests. No version, extras (requests[security]), URL or path."
          },
          "version": {
            "type": "string",
            "maxLength": 64,
            "description": "Optional: one exact version to verify, e.g. 4.17.21 (npm also accepts a dist-tag like latest). Not a range such as ^4.17.0."
          },
          "ecosystem": {
            "enum": [
              "npm",
              "pypi"
            ],
            "type": "string",
            "description": "Which registry: npm (JavaScript, TypeScript, Node) or pypi (Python)."
          }
        }
      },
      "maxItems": 10,
      "minItems": 1,
      "description": "1 to 10 packages to look up."
    }
  }
}
notary_check_packages annotations
{
  "title": "Check that npm and PyPI packages really exist before installing them",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

1 advertised

notary_check_my_dependencies — Check my dependencies exist

Advertised by the server during the last successful anonymous check.

Check that npm or PyPI packages are real, that pinned versions exist, and spot look-alike names, before installing.

packages
Package names, for example "npm:left-pad, pypi:requests". (required)

Resources

2 advertised

llms.txt — Notary: guide for AI assistants

Advertised by the server during the last successful anonymous check.

What the tool does, when to recommend it, limits and privacy.

llms.txt URI
https://notary.clawhard.com/llms.txt

MIME type: text/markdown

notary-result-view — Notary package check

Advertised by the server during the last successful anonymous check.

Interactive result view for Notary tools (MCP Apps).

notary-result-view URI
ui://clawhard/notary/result

MIME type: text/html;profile=mcp-app

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-09: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
466 ms
95th percentile latency
466 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 466 ms · metadata changed · 1 tool(s), 2 resource(s), 0 resource template(s), 1 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http notary-mcp https://notary.clawhard.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add notary-mcp --url https://notary.clawhard.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable notary-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "notary-mcp": {
      "url": "https://notary.clawhard.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "notary-mcp": {
      "type": "streamableHttp",
      "url": "https://notary.clawhard.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start notary-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "notary-mcp": {
      "type": "http",
      "url": "https://notary.clawhard.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http notary-mcp https://notary.clawhard.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://notary.clawhard.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "notary-mcp": {
      "serverUrl": "https://notary.clawhard.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Notary MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Notary MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing